Setting Up Purchase Order Release Strategy _ SAP Blogs

3/30/2018

PPrroodduuccttss

Setting up Purchase Order Release Strategy | SAP Blogs

IInndduussttrriies

SSuuppppoorrtt

TTrraaiinniinng g

CCoom mm muunniitty

DDeevveellooppeerr

PPaarrttnneerr

About About

 Home / Community / Blogs

Actions

Setting up Purchase Order Release Strategy September 18, 2013

|

80,017 Views |

Amit Tunara Tunara more by this author

Retailil Reta @sap @sa p retail | pur chase chase release | retail | sap sap mm mm

share 0

share 1

tweet

share 0

like 4

Follow

Purpose of the Release Strategy The procurement department of a company consists of many buyers who are responsible for buying goods from the market. There is a https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

1/44

3/30/2018


hierarchy of people order

and

like the operator operator or the buyer who creates creates the

purchasing

managers

to

supervise

and

control

the

procurement process. Since purchase order is a legal document and it goes outside the company to the vendor, it is very much important to control the process to avoid any errors or unauthorized transaction. When the Purchase order is processed further for goods receipt and invoice verifications, there will be accounting entries generate and it creates Accounts Payable entries (AP).

Because of this reason and legal implications of Purchase orders, it is very much required to control the procurement process by introducing approvals. For the same, SAP has provided a concept of release strategy. strategy.

In release strategy, there there are different released released

codes which are used for designated users. The release code is a two character ID allowing a person to release (clear, or approve) a purchase requisition or an external purchasing document. The release codes are basically controlled via a system of authorizations (authorization object M_EINK_FRG). The user with specific release code assigned can perform a respective release in a purchase order. For example, the user who creates the purchase order is assigned the lowest level release code. When the purchase order is saved or checked, system will trigger the Release Strategy for that document depending on the defined criteria. In the purchase order which is required to be released by a higher level user, there will be a Release Strategy tab on header of the PO document. In this tab, system shows all the levels of release codes who are involved in approving the purchase order. Following practical example will demonstrate the purpose of release strategy and its implementation in SAP. A company where there is following approval mechanism used in procurement department needs to have a release strategy in SAP. If the value of Purchase order is less than 500.00 USD, it can be approved by a Purchase Manager and then can be processed further. When the Purchase order value exceeds 10000.00 USD, in addition to the purchase manager, it requires an additional approval of Head of Department. Department. If the value of PO is more than 50000.00 USD, then it needs an approval of Vice President once it is approved by the Manager and then by HoD. https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

2/44

3/30/2018


hierarchy of people order

and

like the operator operator or the buyer who creates creates the

purchasing

managers

to

supervise

and

control

the

procurement process. Since purchase order is a legal document and it goes outside the company to the vendor, it is very much important to control the process to avoid any errors or unauthorized transaction. When the Purchase order is processed further for goods receipt and invoice verifications, there will be accounting entries generate and it creates Accounts Payable entries (AP).

Because of this reason and legal implications of Purchase orders, it is very much required to control the procurement process by introducing approvals. For the same, SAP has provided a concept of release strategy. strategy.

In release strategy, there there are different released released

codes which are used for designated users. The release code is a two character ID allowing a person to release (clear, or approve) a purchase requisition or an external purchasing document. The release codes are basically controlled via a system of authorizations (authorization object M_EINK_FRG). The user with specific release code assigned can perform a respective release in a purchase order. For example, the user who creates the purchase order is assigned the lowest level release code. When the purchase order is saved or checked, system will trigger the Release Strategy for that document depending on the defined criteria. In the purchase order which is required to be released by a higher level user, there will be a Release Strategy tab on header of the PO document. In this tab, system shows all the levels of release codes who are involved in approving the purchase order. Following practical example will demonstrate the purpose of release strategy and its implementation in SAP. A company where there is following approval mechanism used in procurement department needs to have a release strategy in SAP. If the value of Purchase order is less than 500.00 USD, it can be approved by a Purchase Manager and then can be processed further. When the Purchase order value exceeds 10000.00 USD, in addition to the purchase manager, it requires an additional approval of Head of Department. Department. If the value of PO is more than 50000.00 USD, then it needs an approval of Vice President once it is approved by the Manager and then by HoD. https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

2/44

3/30/2018


To achieve this, there will be four release codes created in the system. Code 10: For Initial Status when the PO is created Code 20: For Purchase Manager Code 30: For Head of Department Code 40: Vice President Now with this requirement, following release code will be attached to each document depending on the value of the PO. A Purchase order of value 345.00 USD will have only two release codes 10 & 20. First it needs to be released by user who is assigned release code 10 and then further release is required by the Purchase manager who has release code 20. A Purchase order of value 12500.00 USD will have 10, 20 and 30 release codes. First release will be user with release code 10; second release will be by user with release code 20 and then final release by HoD who has release code 30. Similarly a purchase order of 75500.00 USD, it requires 4 level of release.

Preparation of required objects for Release Strategy in SAP Before we start configuring release strategy in SAP, we need to define the combination of parameters to trigger the release. This triggering criterion can be a combination of Document type and Purchasing organization along with value depending on which the number of release codes are assigned when the document is created. In SAP we have a run time structure with name CEKKO (Communication Release Strategy Determination Purch. Document) which provides all the possible list of fields using which a release strategy can be configured. To view all this fields of the structure you can use transaction code SE12. In SE12 screen, in the database field provide the structure name CEKKO and click on Display button.

https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

3/44

3/30/2018


Conguration of Release Strategy for Purchase Order Creating Characteristics of each attribute of Selection criterion Let us assume that we want to configure the release strategy based on the combination of three fields. These fields are Document Type (CEKKOBSART), Purchasing Organization (CEKKO- EKORG) and Purchase order total value (CEKKO- GNETW). We need to create individual characteristic for each of this field and then group them into a release class. Please follow the steps given below to create characteristics. SPRO Menu Path: SPRO: Material Management -> Purchasing -> Purchase

Order -> Release Procedure for Purchase Orders -> Edit Characteristic

Transaction code: CT04

Provide the characteristic name and click on Create button to create the characteristic.

Give

appropriate

and

meaningful

name

for

each

characteristic so that they become easy to identify in further process.


4/44

3/30/2018


In Basic Data of characteristic screen, provide appropriate description. If you want to configure the release strategy for single document type, you need to select Single Values in Value Assignment block and if it is required for multiple document type then select Multiple Values radio button.

Now, the fields are to be referred from CEKKO structure, we need to provide the reference to this structure and corresponding field. Since this characteristic is created for document type, please specify the structure and field name given in the below screen.

As soon as you enter the structure name and field name, system will generate a warning message “ Format data taken from Data Dictionary (press


5/44

3/30/2018

enter)”.


This warning message indicates that the data type of the

characteristic will be taken from the data dictionary of this structure in SAP.

Now navigate to Values tab and provide the document types which are required in this release strategy. For this example, we are taking document type NB which is Standard PO. Please see below screen shot.

Please note that in the characteristic values tab, these values are not available as a F4 selection. So they must be typed correctly and it should match exactly with the document types used. We need to make sure that these characteristics are used only in class which is made up for Purchase order release. For this purpose we need to provide the restriction in characteristic. Provide class type 032 in the restriction tab to achieve this.

If the system is used in multiple languages and if it is required to maintained the characteristic description in multiple languages, then the same can be done from the description tab. Please navigate to Description tab and for each language and save your characteristic.


6/44

3/30/2018


Finally Save the characteristic. Using the same method creates another characteristic BP_PURORG for Purchasing Organization. For third characteristic which is Purchase order Net value, we need follow the same steps except the below points:

When you mentioned the Structure name CEKKO and field GNETW for purchase order net value, system will ask for the currency since this field is related to numbers and net value of purchase order. Please mention USD as a currency for the characteristic. If you have multiple criteria for different range of values, the same has to be provided in Values tab with a Multiple Value radio button tick in Basic data. Since there will be intervals in the purchase order values, you have to configure the characteristic to allow the values in intervals. For the same please tick the check box “Interval Vals allowed” in Value assignment block in Basic data tab.


7/44

3/30/2018


For this characteristic, the values are to be defined in intervals as given in below screen.

So this way we have created the following characteristics for our release strategy.

BP_DOCTYPE for Document Type NB BP_PURORG for Purchasing Organization BP01 BP_NETVAL for Net Value below 100.00 USD and above 100.00 USD


8/44

3/30/2018


Creating Class for Purchase order Release Once we have all the characteristics ready with us, we need to group them into a class. Please see the below procedure to create the class.

SPRO Menu Path: SPRO: Material Management -> Purchasing -> Purchase

Order -> Release Procedure for Purchase Orders -> Edit Class Transaction code: CL02.

In main screen of CL02 transaction, provide appropriate Class Name and click on Create button. Make sure that the class type must be 032.

In main screen of CL02 transaction, provide appropriate Class Name and click on Create button. Make sure that the class type must be 032. In the detailed screen, provide appropriate description. In Same classification block please select Do not Check radio button.


9/44

3/30/2018


Now the next step is to assign the earlier characteristics to this class. Please note that those characteristics are restricted to be used only in class type 032 which type this class is to be created.

Finally save the class. This concludes the first step for setting up the release strategy.

Dene Release Strategy for Purchase Order After the class is ready, the next is to configure the elements required in release strategy. Following elements are required. Release Groups Release Codes Release Indicator Release Strategies Workflow

Congure Release Groups Use following SPRO path for configuring these elements of release strategy.

SPRO: Materials Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders.

When you click on this option, system will give sub options to proceed further. Please select Release Group. Keep the cursor on Release Group and click on Choose button. https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

10/44

3/30/2018


Click on New Entry button to create new Release Group. In new record, give appropriate Release Group name as BP, in Class field give our Class name which we have created in above step. Click on Save button to save your entry.

Congure Release Codes Use following SPRO path for configuring these elements of release strategy. SPRO: Materials Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders.

When you click on this option, system will give sub options to proceed further. Please select Release Codes. Keep the cursor on Release Codes and click on Choose button. https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

11/44

3/30/2018


Click on New Entries to create the Release codes for our release strategy. Number of release codes depends on number of approval levels. Here only two release codes are created which are 10 and 20 for Buyer and Manager respectively. Please note that these release codes are to be created under the same release group which we have configured in previous tab. Click on Save to save your entries.

Congure Release Indicator Use following SPRO path for configuring these elements of release strategy. SPRO: Materials Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders.

When you click on this option, system will give sub options to proceed further. Please select Release Indicator. Keep the cursor on Release Indicator and click on Choose button.

This screen indicates release id for initial and released status. Release ID 0 indicates Blocked status and with release ID 1 it is Released status. The field Changeable contains the parameter which will define how the system reacts if a purchasing document is changed after the start of the release procedure. Means once the order is released, we can still change the values in purchase order which will trigger a new release status. If the field is allowed to change, we can define the % of change allowed.

Congure Release Strategies Use following SPRO path for configuring these elements of release strategy.


12/44

3/30/2018


SPRO: Materials Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders. When you click on this option, system will give sub options to proceed further. Please select Release Strategies. Keep the cursor on Release Strategies and click on Choose button.

Click on New Entries button and give your release group. After giving the release group, provide appropriate Release strategy and description.

Now suppose you want to keep only one level of approval for all PO below 100.00 USD and 2 level of approvals for PO greater than or equal to 100. To achieve this we need to have two release strategies. First release strategy will have only 1 release code and only value less than 100.00 USD is to be selected from characteristic BP_NETVAL. For the Purchase order having value greater than or equal to 100.00 USD, we will create another release strategy which will have both the release codes as we need two level approvals in this case. The following steps are demonstration of second release strategy (with 2 approvals). The same steps needs to be followed for another strategy. In the given space give all your Release codes.


13/44

3/30/2018


Now click on Release prerequisites button. In prerequisites screen, select prerequisites for each release code. In the given screen shot, we are saying there is not prerequisite for release code 10 and for release code 20 it is required that release id 10 has to be there. Once done, click on Continue button to save the settings.

The next step is Release statuses. Click on Release Statuses button. Here we are attaching the release ids for each operational step. From the below screen it is clear that when the document is created when both the release status are at initial condition.

When the first level of release is done means when it is released by a user having release code 10, the overall status is still Blocked. When the document is released by a higher level user having release code 20, the https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

14/44

3/30/2018


documents overall status will be Released. Once it is done click on Continue button.

Next step is to select the classification values for the selected characteristics in release class. Click on Classification button to proceed.

Here it is required to select all the values from all the characteristics. If you have multiple values in characteristic, you have to select the values which you want to involve in the release strategy. Select a characteristic row and click on Choose button bottom.

Please note it is also possible to directly mention the values here provided Additional Values option is enabled in your characteristic.

Congure Workow

Use following SPRO path for configuring workflow for the above configured release strategy. SPRO: Materials Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders.


15/44

3/30/2018


When you click on this option, system will give sub options to proceed further. Please select Workflow. Keep the cursor on Workflow and click on Choose button.

Click on New Entries button to create records for involved users. Specify the Release group, appropriate release code and User ID in Agent ID column. Please make sure the user ids are specified with Agent type US which indicates that mentioned agent name is a User id of SAP. You have to create each line for each users who are involved in this process and should be attached to an appropriate release code. This is the end of release strategy configuration. With this configuration, we are set to create a purchase order to test our release strategy. Please note that if the purchase order is not released, buyers will not be able to print the Purchase Order. Also in Goods Receipts will be shown with Message no. ME 390 – Purchasing document XXXXXXX not yet released Purchase Order with Release Strategy has tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order. The person with the release authorization has to use ME28 to release the Purchase Order.

—–End of Document ——

Alert Moderator


16/44

3/30/2018


79 Comments

Jürgen L October 14, 2013 at 6:40 pm

which meaning shall this value of <100.00 and >= 100.00 in your strategy have? it just says that any value lower than a hundred and any value greater equal 100 will control that this strategy is valid. You already explain “ For the same we need to have two release strategies.” Why do you show it then as example? This is just misleading the freshers

Amit Tunara

Post author

October 15, 2013 at 2:26 am

Hi,

Thanks for your comment. I have also mentioned the reason for two strategies. Not because of difference in value but I want to attach 2 release code for the PO greater then 100.00.

I have corrected the document with more easy explanation.

Thanks for highlighting this and helping to enhance the usability of the document.

Regards, Amit


17/44

3/30/2018


yagnesh acharya October 17, 2013 at 8:20 am

Dear Amit ,

Good document which explain in details about the release strategy for the Procurement Process.

Mohsin Abbasi October 24, 2013 at 5:01 am

Hi Amit, It’s a nice document, that explain each and every step of Release strategy configuration. You have done in such a nice manner.

Best Regards Mohsin abbasi

Amit Tunara

Post author

October 24, 2013 at 7:19 am

Hi Mohsin,

Thanks for your words.

Regards, Amit


18/44

3/30/2018


Pradeep Mani November 5, 2013 at 12:31 pm

Good work Amit.

Xinhua Fan January 9, 2014 at 8:37 am

hi Amit

I have a problem about the release strategy In our SAP, sometime the PO will have not any release strategy if the PO amount is out of all strategies, and means this PO won’t to be got the approval,

How to fix this and is there any settings we missed, thanks.

Amit Tunara

Post author

January 9, 2014 at 9:34 am

Hi,

Please make sure that your characteristic BP_NETVAL (used above) have the value of all larger value beyond a certain number. Here I have taken last value as >= 100 means all values beyond 100 will be considered for release strategy.

So check in your characteristics for Values.

Regards, Amit


19/44

3/30/2018


Xinhua Fan January 9, 2014 at 4:02 pm

Hi Amit

Thanks for your reply, I’ll test in our QA system, thanks again.

Sowmyesh Maniyar February 10, 2014 at 3:34 pm

Dear Amit,

I am new to this thread & SCN forum & I read this document completely, This is very very well explained and has covered all the aspects required for the configuration. Could you please upload the same kind of document for RFQ & Service Entry Sheet as well.? It’ll indeed be a great help. Please do reply back.

Regards,

Sowmyesh Maniyar

Timo Rietveld June 25, 2014 at 11:34 am

Hi Amit, In our organization we have 176 different release strategies. Still it happens we create PO’s that do not match any of the release strategies. I would like to build some kind of a final release strategy, just for the exeptions that were not foreseen. How can I achieve this? (In a some other ERP system I know I could build a release strategy that is always applicable and I


20/44

3/30/2018


could give it the lowest priority. But I missed the priority thing in SAP.) Thanks! Timo

Dhwni Patel February 27, 2014 at 3:44 am

Hi Amit,

This is a wonderful document which gives all the minute details required to understand the release procedure. Inspite of not being from MM background i could understand this concept very well and i appreciate the efforts taken by you to write this document

Keep up the good work

Regards, Dhwni Patel

Amit Tunara

Post author

February 27, 2014 at 3:51 am

Hi Dhwni,

Thanks for your word.

Regards, Amit


21/44

3/30/2018


Sridhar Jayavarapu February 27, 2014 at 5:38 am

Dear Amit,

Good document well explained !!

Thanks

Amit Tunara

Post author

February 27, 2014 at 5:43 am

Hi Sridhar,

Thanks for your comment.

Regards, Amit

Krishna Kishor Kammaje March 22, 2014 at 10:27 pm

Well written, thank you.

As I understand, since we are going to have two release strategies, In the Classification screen, one will have ‘>=100.00 USD’ and the other will have ‘<100.00 USD’ isn’t it?

Also, what happens if more that one release strategies match the PO?

Thanks Krishna https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

22/44

3/30/2018


Amit Tunara

Post author

March 23, 2014 at 2:13 am

Hi Krishna,

If there are multiple strategies matching the PO, then I would say there is some thing wrong in strategy building. It should not happen in actual practical scenario.

Regards, Amit

Sinead Ryan March 27, 2014 at 9:26 pm

Hi Amit, I really like your document and I have a question for you. Historically (6 years +) some release codes were used on our SAP system. Following changes to the system 6 years ago these release codes were no longer used in any valid release strategies. I need to create some new release strategies and codes now to reflect changes in the organisation structure. Can I re-use some of the old release codes rather than setting up new ones?

Regards, Sinead

Jürgen L March 27, 2014 at 9:45 pm

If you have archived all your documents where the old codes have been used then you can certainly re-use them. https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

23/44

3/30/2018


If that is not the case, then better leave them untouched. A change in customizing does in general only affect documents created or changed after, but if you read the discussions about changes in release strategy in SCN, then you can know that quite a lot people still change old documents and wonder that they go again under approval.

Sinead Ryan March 28, 2014 at 8:52 am

Thanks for your reply. We want to use the release codes in new release strategies. The old release strategies that was used for these Purchase Orders will not be re-used. These “old” release strategies can no longer be used (I think they no longer have a class / characteristics assigned to them, if that is the correct way of describing it). Is your advice stil lthe same? Regards, Sinead

Jürgen L March 28, 2014 at 9:06 am

yes my advice is still the same and in alignment with KBA 1635346 – Add a new release code to the release strategy of PR issue

PRASOON AK March 28, 2014 at 9:45 am

Hi, In addition, have a look in to the note: 365604 – FAQ: Release strategies in purchasing and the doc: Deletion of Existing Release Strategy in SAP ECC https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

24/44

3/30/2018


Regards, AKPT

Deepak M July 21, 2014 at 6:58 am

Dear Ami,

Really it is wonderful document for fresher Thanks for your effort.

Regards Deepak

Amit Tunara

Post author

July 22, 2014 at 5:04 am

Hi Deepak,

Thanks for you comment.

Regards, Amit

Siew Tim, Colin Cheong July 22, 2014 at 6:10 am

HI Amit, https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

25/44

3/30/2018


You may need to set the start of the lower end of the value checks with 0.01 instead of 0. Sometimes, when a FOC PO is raised, it is blocked and need to be released.

Amit Tunara

Post author

July 23, 2014 at 2:41 am

Hi,

Thanks for the comment.

Its a general document focusing on concept. If business needs this, we can set accordingly.

Regards, Amit

Timo Rietveld July 28, 2014 at 8:54 am

In our organization we have 176 different release strategies. Still it happens we create PO’s that do not match any of the release strategies. Apparently there are still combinations of characteristics that were not foreseen. What would be the convenient way to solve the many escapes that we experience in our release strategies? Or isn’t there an easy way and should I create a set of release strategies for every exception? How do other companies approach this? Regards, Timo


26/44

3/30/2018


Anil kumar July 29, 2014 at 2:39 pm Dear Amit,

I am new to this thread & SCN forum & I read this document., This is very very well explained and has covered all the aspects required for the configuration.

here i have taken the Purchase group instead of Purchase document as a characteristic

now i face the below error…

Basic checks Release strategies Release strategy PU for release group 02 is inconsistent Release strategy ZY for release group 02 is inconsistent Release strategy 04 for release group 04 is inconsistent Release strategy M1 for release group PI is inconsistent Release strategy S2 for release group RG is inconsistent Release strategy S1 for release group VS is inconsistent Release strategy Z1 for release group Z1 is inconsistent Release strategy ZG for release group ZG is inconsistent

with regards Anil

Marcus Alves August 18, 2014 at 8:27 pm

Hi Amit, Very usefull Doc. I have a doubt regarding it. If I wanna avoid reset a PO release when a field have changed, how can I manage which fields will be relevants for PO release strategie ? i.e. My user have requested that a specific kind of PO have no new PO release requested when the Payment Conditions (ZTERM) at the header or IVA code at the item line (MWSKZ) have changes, for example . I understood that KZFAE is related to this question, but how could I know which are the fields associated to the each KZFAE value ? https://blogs.sap.com/2013/09/18/setting-up-purchase-order-release-strategy/

27/44

3/30/2018


Regards M.V.Alves.

kumar kumar September 26, 2014 at 5:54 am

Hi Amit, Very Nice Document, very use full. Thanks for Sharing the Document. Regards Kumar

Amit Tunara

Post author

September 27, 2014 at 12:42 am

Hi Kumar,

Thanks for your comment. Regards, Amit

Darshak Kathiriya October 2, 2014 at 2:39 pm

HI,

Is there a way to re-trigger release at the GR in case of over delivery ?

Thanks, Darshak


28/44

Setting Up Purchase Order Release Strategy _ SAP Blogs

Recommend Documents