PR-Release Procedure

Setting up simple Release Procedure for Purchase Requisitions

Release Procedures (approval) can be used for Purchase Requisitions (PR), Purchase Orders (PO), RFQ’s, Outline Agreements and Service Entry Sheets. The principle is exactly the same for all. If you can master one, you will know them all.

Lets set up release procedures for PR for the following example:

Our company have got 2 plants: Plant 3100 (London) and plant 3600 (New York).

  • For New York (plant 3100), if PR item value is between 0 – 1000 dollars, then PR needs to be released by one person (person B)
  • For New York (plant 3100), if PR item value is bigger than 1000 dollars, then PR needs to be released by two people (first by person B, then person C)
  • For London (plant 3600), if PR item value is bigger than 1000 dollars, then PR needs to be released by two people (first by person A, then person C).

Name:  relpro_diagram.gif Views: 14125 Size:  17.8 KB

Key terminology:

  • 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)

Here is a summary of the steps to follow to set up our example:

  • Create Characteristics & link to comm. structre (CEBAN for PR)
  • Create Class & link to characteristic
  • Create Release Groups & link to class
  • Create Release Codes
  • Release Indicator
  • Set up strategies
    – Strategies & Codes
    – Prerequeirements
    – Status
    – Assign values for strategies
  • Set overall / item for doc type (PR only)
  • Create and allocate autorisation profiles


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.

Name:  se12_1.gif Views: 13910 Size:  8.0 KB

Name:  se12_2.gif Views: 13775 Size:  21.6 KB
Name:  se12_3.gif Views: 13688 Size:  5.9 KB

So the two fields that will be used is:

Field CEBAN-WERKS for Plant
Field CEBAN-GSWRT for Item Value

We need to create a characteristic for every field. tcode ct04
Any characteristic name can be used. Keep something descriptive to avoid confusion.

For Item Value — lets create characteristic Z_GSWRT
Name:  ct04_1.gif Views: 13705 Size:  9.9 KB

First go to Additional Data tab and enter the table/field (and Enter)
Name:  ct04_2.gif Views: 13713 Size:  12.7 KB

Enter currency to be used in the Basic data tab.
Also select multiple values and Intervals allowed

The Intervals allowed will allow us to assign a range of values, example: If PR value is 0 – 1000 USD …..

Name:  ct04_3.gif Views: 13648 Size:  17.7 KB

Save the characteristic

For Plant — characteristic Z_WERKS
Again, the table/field name in Additional Data to enter table/field

Name:  ct04_4.gif Views: 13652 Size:  14.8 KB

Again set multiple values and save the characteristic
The multiple values is to assign more than one plant to strategy, example: If PR for plant 3100 and plant 3600 is …

Create Class & link to characteristic

Create a class (simply to group the characteristics). Again any name can be used. Tcode CL01 — Create Class. The Class Type must be 032.

Name:  cl01.gif Views: 13554 Size:  9.3 KB

Configure Release Procedures

Above actions was all master data. We now need to do some configuration. Menu: IMG > Materials Management > Purchasing > Purchase Requisition > Release Procedure > Procedure with classification > Set up procedure — (tcode OMGQ in older SAP versions)

Name:  omgq.gif Views: 13515 Size:  5.8 KB

Create Release Groups & link to class

We have two groups to create AA and AB. We need to indicate the class we are working with, in out case Z_PR.

Name:  rel_group.gif Views: 13500 Size:  8.1 KB

Create Release Codes

Create all the release code / group combinations. This is all the dots in diagram above. So we have 4.

Name:  rel_codes.gif Views: 13469 Size:  7.5 KB

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.

Name:  rel_indicator.gif Views: 13418 Size:  9.7 KB

We will be using two of these — X (Block) and 2 (Released)

Name:  indicator_x.gif Views: 13413 Size:  8.9 KB

Name:  indicator_2.gif Views: 13381 Size:  9.0 KB

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)

Name:  rel_strat.gif Views: 13357 Size:  7.3 KB

Here are the settings for AA / S2

Name:  ab_s2.gif Views: 13333 Size:  8.6 KB

Set up strategies – Prerequisites

For every strategy, we need to define a release prerequisites. This indicate if one code need to take place before the other. In this case, level 2 (L2) can only take place if level 1 (L1) has been released.

Name:  strat_prereq.gif Views: 13295 Size:  3.2 KB

Set up strategies – Status

This is also done for every strategy. The screen is dependant on what groups were linked to the strategy as well as prerequisites that was set up. In this example:

– if nobody release it then PR is block.
– if L1 release the PR, the PR is still blocked
– if L1 and L2 release the PR, the PR can be converted to RFQ/PO

Out of interest, the reason why there is not a L2 only option is because of the setting in the prerequisites.

Name:  strat_status.gif Views: 13304 Size:  4.9 KB

Set up strategies – Values for strategies

The values linked to strategies are master data (not configuration) and can be set in two places. Either within the configuration itself — selecting the classification button

Name:  classi.gif Views: 13247 Size:  3.7 KB

Name:  classi_values.gif Views: 13279 Size:  6.4 KB

Or, in classification, example CL24N

Name:  cl24n_1.gif Views: 13284 Size:  8.7 KB
Name:  cl24n_2.gif Views: 13206 Size:  5.8 KB

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

Name:  itemwise1.gif Views: 13203 Size:  4.4 KB

On the document type configuration for PR
Config menu: Materials Management > Purchasing > PR > Define document types

Name:  itemwise2.gif Views: 13195 Size:  6.2 KB

Create and allocate authorisation profiles

In our example we will have three people releasing, so three profiles will need to be created. Authorisation profiles can be created using tcode PFCG.

Usage of PFCG are not being discussed here, but see below for relevant screen where the profile was created.

Name:  pfcg.gif Views: 13254 Size:  33.8 KB


Create a Purchase Requisition

Lets create a PR, and see if the release procedure kicks in. In our case we will create it for plant 3600 and any value. So we will expect Strategy AB / S2 to kick in.

Create PR — me51n
Name:  pr_rel_tab.gif Views: 13136 Size:  9.1 KB

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).


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

Name:  me55_1.gif Views: 13109 Size:  6.3 KB

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.

Name:  me55_2.gif Views: 13149 Size:  13.4 KB

This is the absolute basics of setting up Release Procedures for Purchase Requisitions. For more posts on Release Procedures, see index of posts.

Categories: Purchasing | Tags: | 1 Comment

Post navigation

One thought on “PR-Release Procedure

  1. Manish


    Can we have more than 8 Release code( Approval Levels ) beacuse, I have got requirement of stretching the 8 levels till 12. But nowhere I could find annthig useful.

    Please help , its an urgent issue.

    Manish Mridul

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Create a free website or blog at

%d bloggers like this: