Beruflich Dokumente
Kultur Dokumente
Release Codes - The different levels that the approval will go through.
Release Groups - Grouping of strategies.
Release Strategy - Unique, set of condition, sequence and levels of releases. Every
line in diagram is a Strategy (so we have 3).
Release Indicator / Status - The status of PR as it moves through the strategy.
Example 'Block' (can't create PO yet) or 'Final Release' (can create PO from PR)
--------------- DETAILS OF SETTING IT UP --------------Create Characteristics & link to communication structure (CEBAN for PR)
Here we define which fields are used to determine the strategy that will kick in. In our case
we used 'Plant' and 'Item value'. Not all fields in the PR can be used. For a full list of fields
that can be used to determine the release startegy, see tcode se12 table CEBAN.
First go to Additional Data tab and enter the table/field (and Enter)
Later on, authorisation profiles will be linked to these code / group combinations.
Release Indicator
First we create the different statusses that the PR can be in throughout it lifecycle. Later on
(below), we will be linking using these statusses. Here is the standard SAP indicators, wou
probably wouldn't need to add any.
Under the Details section, you can indicate which documents can be created from this PR.
For Indicator 2, one can create PO's and RFQ's.
With Field Selection you can define which fields can be changed. This is the same indicator
that gets used with document type configuration to make some fields read only, mandatory,
hidden.
Set up strategies - Strategy & Codes
Every line in our diagram above is a strategy. So We have three
Lets call them:
Group AA / Startegy S1 -- Code L1 (for plant 0001)
Group AA / Startegy S2 -- Code L1 & L2 (for plant 0001)
Group AA / Startegy S2 -- Code L1 & L2 (for plant 0002)
take place before the other. In this case, level 2 (L2) can only take place if level 1 (L1) has
been released.
Both methods work, the advantage of CL24N is that all the strategies can be viewed easier.
Set overall / item for doc type (PR only)
For Puchase Requisitions, there is an option to release either on item level or on document
level. For PO / RFQ / Contracts, one can only release on header level. Back to the PR, it is
highly recommended to use item release. This can be done in two places.
Firstly where the groups were created
Create PR -- me51n
If no 'Release strategy' tab, then it didn't work. In this case all is fine. The user can see the
Release Group (AB), Strategy (S2) and release indicator (X).
(SAVE)
Release a Purchase Requisition
Releasing can be done per PR or collective. Lets' use the collective release. SAP Menu:
Logistics > Material Management > Purchasing > Purchasing Requisition > Release >
Collective Release -- ME55
Select all the items to be released and then hit Save. You will see the status of the item
change to the next Release Indicator.
This is the absolute basics of setting up Release Procedures for Purchase Requisitions. For
more posts on Release Procedures, see index of posts.
SAP version used for this post: SAP ECC (ERP Central Component) 5.0