Release Procedure without Classification – only for PR

Steps to set up a release procedure without classification in Customizing – only possible for PR

OME6 Set Up Procedure Without Classification

path: SPRO – IMG – MM – Purchasing – PR – Release Procedure – Set Up Procedure Without Classification

1. Set up release codes

Release code: The release code is a two-character ID used by an individual or group of individuals responsible for processing a document to release (approve) an item of a PR, a complete PR, or a complete external purchasing doc, like PO,  or cancel an already effected release (that is, revoke an approval).

Who may use which release codes is controlled via authorizations. If a link to SAP Business Workflow has been defined for the release code, the person can release (approve) or refuse to effect release (withhold approval) thus rejecting the item or document.

2. Set up release indicators

Like R for Released

Note: You can protect a PR generated in a planning run against changes caused by a new planning run with a fixing indicator.

You can use a field selection key to prevent certain fields being changed during later processing.

Otherwise you can use the Changeability indicator to specify the consequence of changing the document after the start of the release procedure.

For value changes you can define a percentage that will be tolerated.

And B for Blocked

3.  Assign release indicators

Example: You create a release strategy S1 consisting of two release codes 10 and 20.

If release has been effected with 10, the requisition has been given the “all clear” for the issue of RFQs. If release has been effected with 10 and 20, the requisition has been given the “all clear” for issue of RFQs and POs.

Release with 10 is a prerequisite for release with 20 (defined in next step).

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

Now enter the following as assignment:

Note: you can use a maximum of eight (8) release codes in a release strategy.

4. Release points: 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: Release with 10 is a prerequisite for release with 20.

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.

i.e. Assign release strategy to a combination of Account Assignment Category, Material Group, Plant, Value of PR, and Currency.