SAP Material Management
Purchase Requisition
Release Strategy SETUP
Item level Release Strategy
IMG Menu path for PR Release Strategy with Classification
1
Release Group
Release Group is Enterprise Strucutre Independent
Not selected means Release Strategy activated at the PR item level.
Selected means Overall Release, where Release Strategy is activated at Header PR level
FRG_EBAN and GFRG_EBAN are example SAP delivered Class for Release Strategy
New Release Strategy is only desirable when a new CLASS is required due to additional classifications characteristics for a new Plant (otherwise, it a New Plant can share the same Release Group)
2
Class
Release Strategy uses Class type 032
These Characteristics are called Reference Characteristics as there are linked to fields in the PR table.
Eg: Double click FRG_EBAN_WERKS
CEBAN is the Communication Table for PR Release Strategy
WERKS is the Plant field
You can check in SE11 for the PR fields you can use via the CEBAN table
I show you an example how to create a Reference Characteristics POINTING to the PLANT field
NO NEED to enter any DATA here
CLICK to goto Addiontal Data TAB
CEBAN is the Communication Table for PR Release Strategy
WERKS is the Plant field
Format data from SE11 data dictionary for WERKS field copied
From WERKS (SE11) data dictionary. Not need to change anything
SAVE
Next I show you how to create a New Class
Description
Next, Goto Characteristics TAB
Enter Characteristics Z_PLANT and press enter to confirm
Existing Characteristics can be used for many classes (for the same class type)
Technically speaking, SAP Documentation says DO NOT do this, see Documentation below !
If we follow SAP Standards, once project go life with Release Groups and CLASS, you will not be creating new CLASS !!! ….->>>>
Note: In most SAP versions, you are not even allowed to SAVE it. BUT even if you can SAVE it, do avoid the RISK !
3
Release Codes
Release Codes are 2 alphanumeric and dependent on Release Groups (wtih or without workflow)
When a Plant added with new Personnel, it is likely to have to Maintain a NEW Release Code (due to Role Authorization for PR Approval)
Enter like this, then press enter to confirm and SAVE
You can SAVE this into a Seperate Transport Sequentially just for PR Release Strategy
4
Release Indicstors
Release Indicators/ID are Release Code Independent and after project Go-Life, unlikely there is a need to review to add (when purchasing policies are the same), It is a single alphanumeric Key
Release ID is also assign to Field Selection (to hide/display etc fields in the PR once the status is reached)
5
Release Strategy
Consider this, when phase 1 consultants design a Release Strategy for each Plant (due to whatever reason), then in other phases in the future when adding a new Plant, it maybe desirable to follow similar route and therefore create a New Release Strategy for the New Plant !
However, you must also consider if introduction of new Release Codes, new Release ID/indicator, and Approval Values are all possible reasons why a New Release Strategy is desirable !
In this example, we shall create a Release Strategy with 3 Release Codes and approprite Release Pre-requisites for a New Plant with Approval value of >$10,000
We use Release Group with Item level Strategy activation
SAP provide max of 8 Release code per Strategy, we shall use 3 in this example
Define Release Prerequsites
This indicator means Z1 must approve before Z2
This indicator means Z2 must approve before Z1
Beware of how you select the indicators, see the explanations.
Obviously the above selection has no meaning. System does not allow you you click CONTINUE ...
Note, I have added one more selection:
First, Z1 must approve before Z2
Next, Z1 must approve before Z9
But Z9 can approve before Z2 approves the PR
Likes wise Z2 can approve the PR as long as Z1 has approve the PR (Z2 does not have to wait for Z9 to approve the PR as there are no pre-requisites setup for it)
Final indicator I have choses, now the Strategy will sound like this:
Z1 must approve before Z2 and Z9 can approve
Z2 must approve before Z9 can approve
Z9 can only approve if both Z1 and Z2 approves
Next, we can set the Release Status (beware, the layout combinations will depend on the Release Pre-quisite)
I will show you a few examples.
Line 1, when no one approve, PR at “S” status
Line 2, Z1 expected to approve, PR still at “S” status
NOTE line 3 an line 4,
After Z1 approve the PR,
either Z9 or Z2 can approve But PR still at “S” status when only either Z9 or Z2 approves the PR
When All 3 approves the PR, now PR can convert to PO
Line 1, when no one approve, PR at “S” status
Line 2, Z9 must first approve before Z1 and Z2
Z2 can only approve the PR when Z9 has approve it
Z1 can only approve the PR after both Z2 and Z9 approved the PR
No release pre-requisite, note Line 2, 3, 5 shows all 3 release code can release independently, note line 4, 6, 7 shows what if any 2 release code release then what will be the release indicator !
Line 1, when no one approve, PR at “S” status
Line 2 shows that Z1 must release first before any other release code can release
Line 3 shows that after Z1 release the PR, the next to release the PR is Z2 !!!
Z9 is the last person to release after both Z1 and Z2 have release the PR
Next is to design the Classification Values
To enter multiple values, click FR on the field
Select Multiple values and click CONTINUE
Note you can only see desriptions and not the key after press Enter.
Perform a Simulation
You must SAVE first before begin SIMULATION
Start Simulation
Double-click here to Release by Z1
Z2 can release
Note Z1 release affected
Z3 will have to wait
Double-click here to Release by Z2
Note Z2 release affected
Z3 can now release
Note,
Release Strategy Z9 Activated
Double-click here to Release by Z3
Note Z3 release affected
Final Release Status
We will use this material with some of the matching characteristics values (the rest of the fields values are in the PR)
PR will use Material master Price
1
1
2
2
3
3
4
4
5
5
6
6
7
7
When fields values in the PR matches the Release Strategy Characteristics Values… the
Release Strategy will be ACTIVATED