Releasing Procedure for PO

[Former Member]

Dear all,

I created Releasing Procedure for PO, when creating PO, the Release procedure not diplay in PO, what i done a mistake, can you help me.

Thanks

[Former Member]

Hi,

Release Procedure for Purchase Orders

Appended below are activity required to be done step by step for configuring the release procedure for purchase orders (POs) and its link to workflow.

[edit]

Requirements

u2022 In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).

u2022 You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure (Authorization Management -> Create Authorization Profiles and Assign to Users).

[edit]

Activities

Here you define the following:

u2022 Edit Characteristic

u2022 Edit Class

u2022 Release group

u2022 Release codes

u2022 Release indicator

u2022 Release strategy

u2022 Workflow

[edit]

Edit Characteristic

In this step, you create characteristics for a release procedure for purchase orders (POs).

Classification characteristics are the criteria for a release condition.

If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchasing document (e.g. purchase order or RFQ).

[edit]

Edit Class

In this step, you create classes for a release procedure for purchase orders (POs).

You use a class to group together characteristics that are to constitute a release condition for a release strategy. In the step "Define Release Procedure for Purchase Orders" you assign this class to the release strategy.

[edit]

Release group

Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure.

[edit]

Release codes

Here you create the release codes you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field

The Workflow indicator is also used to control role resolution:

u2022 "1 - Role Resolution with Group, Code and Plant (T16FW)"

o Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).

u2022 "9 - Role Resolution via User Exit"

o Here you use the customer exit M06E0005 to define a role resolution of your own.

[edit]

Release indicators

A release indicator shows the release status of a PO.

Via the following settings, you can define the release indicators you need for your release procedure

u2022 The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.

u2022 The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).

u2022 By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.

[edit]

Attention

The following release indicators are necessary for every release procedure:

u2022 Release indicator for initial status

o If the PO is subject to a release strategy, it must normally be released before it can be transmitted to the vendor. Therefore, when a PO is created, it is assigned a release indicator that blocks it from being outputted in message form.

o The Released indicator must not be selected for this indicator.

u2022 Release indicator for released status

o This indicator is assigned to the PO when it is released.

o The Released indicator must be selected for this indicator.

[edit]

Release strategies

Create a release strategy for your release group and assign your release codes accordingly.

u2022 Release prerequisites

o With the release prerequisites, you specify the order in which the individual release points (individuals or departments) represented by the release codes may release the document.

u2022 Release statuses

o Here you specify the status a PO has after certain release points have effected release. Specify which release indicator/status a PO is to have after having been released via a certain release code.

u2022 Classification

o In classification, you maintain the values assigned to the characteristics. Via the characteristics and their values, you specify the POs to which your release strategy is assigned. Maintain values (individual values or intervals) for your characteristics.

u2022 Release simulation

o The release simulation function enables you to check which status a PO will achieve with your release strategy if release is effected by a certain release point. Choose "Simulate release" and release the document with the desired release code by double-clicking. The system shows you which status the PO now has as a result of this release.

u2022 Workflow

o Assign a processor ID to your workflow-relevant release codes. The processor (member of staff responsible for processing the document) will then receive a work item when he or she is required to effect release.

You can assign a processor ID either directly or indirectly:

u2022 Direct processor assignment:

o Enter a user name.

u2022 Indirect processor assignment:

o Enter a job, for example, or a position. At runtime, the system will then determine the member(s) of staff responsible for processing the document.

Good luck

anthyodaya.

[Former Member]

Hi,

if u r maintaining chacteristic value by price(amount value ) plant , value,pur. group

check once again. check the amount value and plants ext.

can u find this more info :-

for configuring the PO rel stratgy, the following are the steps to follow.

SPRO>MM>Purchasing>Purc.order>rel .procedure-->with classification.

1. create characterstic(CT04)

2. Create class(CL02)

3. Define rel stargy(rel.grp.,rel.code,stratgy)

4.in the staregy last step (in work flow) giv the agent id number for the rel.group and code

5. in CL24N check all the parameters related to the strategy.

6. and in the workflow assignment i.e. t.code:PPOM_old(and PPOM is new t.code) select the respective organizational unit and in that the number of users were assigned to the agent Id.

Regards,

Anthyodaya.

[Former Member]

Dear All,

i am tried to release PO, but in PO no Release Procedure, i don't what i have done a mistake.

Steps:

1. Edit Charactertics- Company Code, Plant, Pur Org & Total Net order value, these are characteristic created.

2. Created a Class for Charactertics.

3. Then created Release Strategies.

4. Created PO

5. Release PO- Using Tcode ME28.

6. Then Display the PO.

Result: No Po Release Procedure displayed in PO.

plz help me how to create Release strategy steps by steps.

It will help for me.

Thanks

[Former Member]

You need to maintain classification view for your strategy to work. Go under release strategies tab, there you will see CLASSIFICATION, double click on it, and maintain your Company Code, Plant, Pur Org & Total Net order value there and once classification is maintained, you will see your release strategies working.

If your spro is non customizable, you cannot write directly to classification. In that case you go through TCode CL20N and maintain your classifications there.

Edited by: Afshad Irani on Apr 13, 2010 5:45 PM

[Former Member]

After Creating the PO, Click on Check, then look for Release strategy tab. If it is not present, you should check one again check the settings for the characteristics defined for your strategy

[Former Member]

1. Create Characteristic : with transaction code CT04

Under Basic Data View : give the data type, Number of Character and Decimal Place

Under

Additional Tab give Table and field name for which you are trying

Under restriction tab give class type as 32.

2. Create Class under CL02 transaction code ( You can go through Menu path)

Under Basic Data tab give description and check the status as Released.

Under characteristic tab assign Character created.

3. Under Release Procedure

A. Define Release group and assign the class

B Define release code and assign to Created release group

C. Check Release Indicator is their or not.

D. Under Release Strategy

I) Assign the Strategy to group

II)Give the release code as required.

II)Set Prerequisites

II)Check release strategy

IV) Under classification view Assign the value to Characteristics ( or go to transaction code Cl20N and do assign)

V) Do release simulation and save

Try again for transaction with necessary " Characteristic Value"

You will get.

If you are not getting.

Delete all config. save and come out of the system and try the steps you will get. ( Infact this sentence is not required you can resolve)

• Check Version Management if active.?

• Check table entry T16FS for all data is existing or not.

Edited by: sudhansu satapathy on Apr 13, 2010 8:52 AM

[Former Member]

Dear Friend,

Please check in Tcode CL20N for your release group and strategy, chacteristic value ( plant , value,pur. group etc..) entry .

Rgds,

Kareena

[Former Member]

Hi,

Once you save your PO than only u can see the release tab at the header level. check it out.