cancel
Showing results for 
Search instead for 
Did you mean: 

PR Workflow for release strategy

Former Member
0 Kudos

Hi,

Could you please let me know the steps how to configure the workflow for the PR release strategy for both item level as well as header level.

Thanks in advance

Shp

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

In SPRO - In the Work flow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The work flow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the work flow if you want him/her to have the authority to release purchasing docs in more than one Plant.

How to configure?

Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).

For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

If you wish to work with procedure 1, define the following:

Release codes

Release indicators

Assignment of release indicators

Release prerequisites

Determination of release strategy

1. Release codes

Create the release codes.

2. Release indicators

Define release indicators and branch to the detail screen. Here you define whether fixed purchase requisitions may be changed by Materials Planning, for example, and whether an RFQ or a purchase order may be created from the requisition.

You can also determine the field selection here.

In the area "Changes after the start of the release procedure", you specify whether a requisition may be changed after the release procedure has begun. You specify whether the strategy has to be redetermined after changes, or whether the release procedure has to start all over again from the beginning.

This parameter bears a relation to the parameter "Value change". For example, previous releases are not cancelled if the value of the requisition item after the change does not exceed plus 10% of its original value.

Attention:

Be sure to create a release indicator (e.g. B for "blocked") that serves as the starting point for subsequent indicators. Do not set the indicators for release for the issue of RFQs and PO on the detail screen for this indicator.

Also create a release indicator characterizing the released status. Set the indicators for release for the issue of RFQs and PO on the detail screen.

3. Assignment of release indicators

Assign a release indicator in dependence on the status of the release.

Example:

You create a release strategy S1 consisting of two release codes 01 and 02. Release with 01 is a prerequisite for release with 02. If release has been effected with 01, the requisition has been given the "all clear" for the issue of RFQs.

You have created the release indicators B (blocked), 1 (cleared for issue of RFQs) and 2 (cleared for RFQs and PO).

Now enter the following as assignment:

Strategy C1 C2 C3 ...

S1 B (blocked)

S1 X 1 (RFQ)

S1 X X 2 (RFQ/PO)

4. Release prerequisites

Define which release codes are involved in a release strategy. Specify whether a code is set for a release status following release, and whether one release status is a prerequisite for another (+).

Example:

Strategy Code C1 C2 C3 ...

S1 01 X

S1 02 + X

5. Determination of the release strategy

Determine the conditions under which each release strategy is assigned. The criteria are account assignment category, material group, plant, and value of the requisition item.

Former Member
0 Kudos

Hi,

Thanks for the detailed explanation & prompt reply. However my issue is with workflow configuration(Workflow management) without maintainig the userid & release grp/relesae code in PR release strategy.

Could yopu please suggest on this.

Thanks

Shp