Professional Documents
Culture Documents
Release Strategy PO
Release Strategy PO
RELEASE PROCEDURE
Release Procedure is an Approval Process for all the Purchasing Documents like Purchase
Order (PO), Purchase Requisition (PR), etc.
The manner in which this procedure is configured is called as Release Strategy.
Release strategy can be with Classification and Without Classification.
Release Strategy without classification will have Account assignment category, Plant,
Material Group & Total value as characteristics whereas with classification you can
define your own characteristics.
Purchase Requisition is released at Header level (overall release) & Item level (item by
item) whereas Purchasing Documents like PR, PO, Contract.etc are released at header
level only (overall release).
In Release Procedure for PO, we use Table CEKKO & for PR we use Table CEBAN.
CEBAN CEKKO
WERKS Plant WERKS Plant
EKORG Purchasing Organization Purchasing
EKORG
EKGRP Purchasing Group Organization
BSART Document Type EKGRP Purchasing Group
GFWRT Header Level Net Value BSART Document Type
GSWRT Item Level Net Value GNETW Net Value
1
Niket Moharle
In this step we will create characteristics of each attribute for selection criterion.
For example, we will create Plant, Purchasing Organization & Net Value as a
characteristic.
a) Plant
Here, we have created one characteristic as PO_PLANTTS & for this we have selected
table name as CEKKO & field value as WERKS (plant).
Select the characteristics value for which release will be applicable. Here in this case
plant TX10 is the Characteristics value.
2
Niket Moharle
b) Purchasing Org.
3
Niket Moharle
Here, we have created one characteristic as a PO_PURCHORGTS & for this we have
selected table name as CEKKO & field value as EKORG (Purchasing Org).
Select the characteristics value for which release will be applicable. Here in this case
Purchasing Org. 3500 is the Characteristics value.
4
Niket Moharle
Here, we have created one characteristic as a PO_VALUETS1 & for this we have selected
table name as CEKKO & field value as GNETW (Net Value).
Enter the Currency & select Interval values allowed.
Select the characteristics value for which release will be applicable. Here in this case, we
select multiple values as <2,00,000 INR & >=2,00,000 INR. It means the Net Value below
2 lakhs will have on release & Greater than equal to 2 lakhs it will have another Release.
5
Niket Moharle
In this step we will create one Class & assign all the newly created Characteristics to it.
Always select Class type “032” for Release strategy.
6
Niket Moharle
In this step, we define Release Strategy & has various sub steps.
a) Release Group
b) Release Codes
c) Release Indicator
d) Release Strategies
e) Workflow
7
Niket Moharle
a. Release Groups: -
b. Release Codes: -
In this step, we will define release codes for our release groups. Maximum 8
release codes can be defined.
Here, we define two release codes each for our both release groups.
8
Niket Moharle
c. Release Indicators: -
d. Release Strategies: -
In this Step, we will define a new release strategy with respect to our release
groups & release codes.
9
Niket Moharle
In Release Prerequisites, we will decide the sequence of the release i.e. (Release
Codes)
In Release Status, we will decide the status of release w.r.t. Release Codes.
In Classification, we maintain the value of characteristics for which release
strategy should be applicable.
In Release Simulation, we just simulate the release i.e. activate the release.
10
Niket Moharle
Similarly, we define one more Release Strategy S9 for Release group TQ with
characteristics Plant TX10, Purchasing Org. 3500 & Net Value >= 2,00,000 INR.
11
Niket Moharle
CASE A: -
In this step, create one PO to check whether the system triggers the correct release strategies.
12
Niket Moharle
Here, one PO of 1000 Kg is created with net price as 150 per Kg for Plant TX10.
PO Doc Type TS created under the number 5500001020
Now if we try to post GR, system will show a message that Purchase order not yet
Released.
13
Niket Moharle
As we enter the PO no., we see that Strategy S8 with Release Codes X1 & X2 gets
triggered by the system.
Plant- TX10, Purchasing Org. 3500 & Net Value <2,00,000 INR.
14
Niket Moharle
Again, for the Same PO, we change the Quantity as 2000 kg with net price unchanged for
Plant TX10 & Save the PO.
15
Niket Moharle
As we enter the PO no., we see that Strategy S9 with Release Codes Q1 & Q2 gets
triggered by the system.
Plant- TX10, Purchasing Org. 3500 & Net Value >=2,00,000 INR.
16
Niket Moharle
Strategy S8 will be trigger for Purchasing Org. 3500, Plant TX10 & if the Total Net Value is
less than 2 lakhs.
Strategy S9 will be trigger for Purchasing Org. 3500, Plant TX10 & if the Total Net Value is
equal to & greater than 2 lakhs.
Also, if there is any Value change then also system will trigger the release strategy.
17