Skip to Content

Customizing of a release strategy in MM  seems to be the final exam which separates the wheat from the chaff.

No doubt that many struggle at this hurdle, 6500 discussions in MM are evident. 4.5% of all MM content. And it is known that this topic is discussed in Retail, ABAP, ERP and some other spaces too.

What makes it so tough?

Is it the number of steps to be executed?

Is it because knowledge on classification is needed?

Is it because of the mix between customizing and master data (classification, cost center…)?

Is it lousy documented by SAP in help.sap.com  or by other users in wikis, blogs and documents?

Is the request not well defined by the business?

Is it too complex because of its flexibility with user exits

is it just too abstract for self-education?

You are invited to share your personal answer in the comment section.

I personally miss words, in particular as answer to the question WHY …?

SAP uses quite a lot words and almost no pictures to explain the process and customizing in help.sap.com

The bloggers and tutors in SCN often use only pictures and outline just what SAP had put in words, but also miss to explain beyond.

The self-educators can just follow this one illustrated process, but in the moment the business requirement is a bit different they fail because they never understood the connections, were not able to abstract the shown process enough to get it linked with their own requirement.

I have to admit, the Airline processes for ABAP education is disconcerted to me too. It could have been half as tough for me if they had talked about material master, vendors and other MM tables.  So I had to make two hops instead of just one to apply the training to my personal requirements. I am already curious how our key users do when they need to test with anonymized data in near future. As you see it can hit you everywhere, you will rarely find a 1:1 match to the things you learned, you need to understand it to make it work for you with variations.

I will not repeat the whole setup process here again, instead I will focus on the things that I miss in the existing content of wikis, documents and blogs, and put links to this content, so that this blog can work as a map and navigate you to the right stuff for particular requirements.

Before we even start with customizing we either get a requirement from the business, or we are proactive and “sell” it to the business by explaining the advantages and telling them why they need it.

WHY do we need a release strategy for purchasing documents?

People do (can) not trust each other. The NSA is spying Mrs. Merkels cell phone,  Google all of us. And not really different in the micro cosmos of a company.

Bosses do not trust their employees, have no trust that they perform their job within the given rules, need a controlling mechanism, like SCN has moderators to control that people do not post the 6501st question on release strategy without doing any research by themselves before.

The boss does not want that the nasty warehouse worker requests a Porsche which is then ordered by the careless buyer..

Anyone can be a requisitioner, but they are only allowed to request something within a certain value range, within the environment of their responsibility. Anything exceeding the defined threshold has to be approved by their supervisors. Some values may even require multiple approvals.

The release code in SAP is the electronic signature replacing the handwritten approval on a paper based process.

In my research for this blog I found numerous documents with SAP screenshots, all started right away with the SAP customizing. My projects start differently and the most time and effort is spend prior to the activities in SAP. We are doing Web meetings, the responsible person from business explains what they want, and the SAP expert tells what can be done. We also have different solution sets which are introduced by the SAP expert.

In general we want reduce the many variants and strive for a single release strategy that can be used anywhere in our global company.

Sometimes we even say “No – this is not the way we want a release strategy in our system”. We have to think about the maintenance costs. If the release strategy is built on strange requests then the costs may explode later. An example: One exotic plant wanted the release strategy based on the user. If it is user Smith then a 2 level approval, but in case of Mr. Hoffmann only one approval by the plant manager is needed. In this example is nothing really generic, and with each change of a user the strategy would need to be amended.

 

Here are 4 strategy variants as example for a release strategy on purchase requisitions:

1

No approvals required

If you are authorized to create a requisition, it will be sent directly to Purchasing without review.

2

Two approvals required for all requisitions

Any requisition, regardless of dollar amount, has to have two levels of approval before going to Purchasing.

3

Approval determined by dollar amount
–> Option A

< $500 – no approval required
$500 – 2499 — Level 1 approval
> $2500 — Level 2 approval

4

Approval determined by dollar amount
–> Option B

< $2500 — Level 1 approval
> $2500 — Level 2 approval

 

and a picture with the same information plus one more variant:

ReleaseStrategy1.PNG

ReleaseStrategy2.PNG

And this was just a small set of examples for release strategies on purchase requisitions. I can just recommend to create a  strategy on release strategies to avoid too much variations. Some can be much more complex and could only be understood by the single developer, and you get in trouble if this developer is not with you anymore, like in this more complex requirement.

ReleaseStrategy3.PNG

As you probably know from the documentation you can have release strategies on requisitions, on purchase orders, contracts and schedule agreements, RFQs and Service entry sheets.

Here is a variety of documents in SAP Community, many unfortunately have more pictures than words, and do not at all emphasize on critical parts like item based characteristics in header strategies.

Release Strategy configuration for Contracts and Purchase Order

Release Strategy for Service Entry Sheets – ERP SCM – SCN Wiki

Multi Level Purchase Order Release Strategy

a better one with a good Q+A section at the end

Setting up Purchase Order Release Strategy

and a jewel among all, unfortunately not much recognized since it was uploaded at SDN times and you need to click the link within that document to see the good work:

Release Strategy Enhancement in Purchase Order

(take the chance and rate the documents while you review them)

Why a release strategy for requisitions AND purchase orders?

The buyer could be corrupt and orders at higher prices. The difference to the normal price is then shared between the sales man and the buyer. Not fictive, it happened in the 80s. That is a reason that even purchase orders need to be approved before they are send to the vendor.

If the approver is really capable to identify such fraud is another story, but the example with the Porsche from above certainly is.

 

If you can trust your buyers, and only want the requisitions be approved, fine, then you an save some work.

It could also be turned, instead of doing a strategy on requisitions you could only implement one on purchase orders, because that would be enough to catch the case with the Porsche.

 

Best you know what your internal auditors want, or you even invite them to the meetings, as this can reduce double work in design and realization.

Do you use contracts, wonderful you can generate money for IT, they can have a release strategy too.

What I actually wanted to say, in that case you may want to avoid an approval of the purchase order if the contract is referenced.

But this is only possible with a user exit where you add coding to check this circumstance.

complicated approval processes need more time

Another topic in the meetings is to talk about the approval process in general. How long does it take to approve a document, how long in case of high complex strategies with the maximum of 8 levels. This time needs to be covered with the purchasing processing time (update customizing or include it into th planned delivery time of material masters). Make them aware that just one approver is a bottleneck, a substitute for vacation and other eventualities is needed otherwise you can’t order anything if the approver enjoys beach life and is bitten by a shark on his last vacation day.

Hey developer, stop and think: If you have several possible approvers, does it make sense to put the name of this approver into the strategy?

A clear NO.   Instead of name that may change once per year use something generic like >20000$ approver or plant manager instead of Mr. Bill.

People often ask for the maximum approval levels – I guess this is interview or certification question – the answer is 8 approval levels, but nobody seems really be interested why you can’t have more. Of course it is caused by the SAP design, table T16FS has only 8 fields for release codes. And the release status field (e.g. EBAN-FRGZU) has a length of 8 characters. This fields is filled with Xs for each approval level. This single field is the basis for the display of the  status overview: /wp-content/uploads/2015/01/screenshot_338607.jpg

 

 

 

Header level strategy

 

What else needs to be defined in the meetings?

In case of requisitions you need to define whether your strategy is at item level or header level.

People are creative, they may dismantle the Porsche and order 4 wheels, 2 Recaro seats , 1 motor …

With item level strategy they may stay below a threshold and would not need an approval.

In purchase orders is anyway only a strategy at header level possible. Since you can only send a purchase order as a whole document to your vendor, because there is no message determination at item level either.

However, you must not forget that you get other challenges with a header strategy.

You know that purchasing documents can have several items. So you can have items for different cost centers, items with different material groups, even items with different plants are possible in one document.

In case of a header strategy you cannot have approvers at plant  or cost center level, except you restrict the creation with a BADI and allow only items from one plant or from one cost center in one document. Standard customizing is not able to restrict this, the BADI or exit is needed.

If you are fine with a header level strategy and approvers by dollar level, no matter for which cost center the items are ordered, then you have to prepare your classification accordingly otherwise your release strategy will not trigger.

An example: in a header level strategy the values from the items are summed up. If you have a plant as a characteristic in your release classification, then the plants from item level are as well “totaled” :  Assume you have 2 items, item 1 for plant PL01 and item 2 for plant PL01, then is is quite as PL01 + PL01 = PL01 . But if item 1 is plant PL01 and item 2 for PL02, then the situation is like this PL01 + PL02 = “blank” . And exact this values need to go into your classification otherwise the strategy is not executed.  Your classification needs for the characteristic plant: PL01 PL02 and blank as value.

This is valid for any field from item level that is used in a strategy at header level. And I have not seen a single document in SCN where this is explicitly shown, but it is seen in the questions quite often and it is said in various wikis and KBAs and OSS notes.

Draft on paper

The result from our meetings is usually a Business Blueprint  and the strategy on paper (in Excel) which can be used as functional specification

Here is an example for a strategy based on cost center by dollar limit. The upper part (Row 1 – 6) is our strategy definition, the lower part (Row 20 – 34) is the mapping to the user roles

Release strat.PNG

Based on Cost Centers (column B) we defined the release groups (column A)

A release group can have just one or many cost centers.

In the example you can see that cost center 98111, 98112 and 98817 belong to the same release group SA

Based on the dollar value we defined the approvers and the  release codes.

Example in column G and H (both columns belong together), Purchase requisitions up to $ 20000 have to be released with release code SC (visible in cell H2)

For each combination of release group and release code we need a strategy code. (for example AC in cell H3 is the strategy for combination of release group SA and release code SC)

For each combination of release group and release code a role is created. (for example role YPSCPX34..  in cell C27  is the role for combination of release group SA and release code SC)

In Cell I27 you can see the description of the role, there is no hint to a dollar value or release group and code.

As you see in the Excel spreadsheet, there are actually 2 parts, the upper part is used to setup the strategy in customizing.

The lower part is used to define the user roles and to assign them to the approvers.

There is no easy link between a user and a strategy. There is usually a n:n relation. There is no report in SAP that can tell you who will be the approver for requisition x.

You would need to obtain the release strategy from the document, look into the customizing to find the release group and code for this strategy  and finally look up the roles which have this combination of release group and code and to which user they are assigned. Sometimes I am asked to check which user is holding up the process. Then I torture myself with SE16N and SUIM transaction to find the potential candidates. It is much easier if the Excel spreadsheet is kept alive and is updated regularly.  Of course an ABAP report would be welcomed. Often requested in SCN, but nobody ever came back to share his program.

With a workflow implemented it is possible to see at which user the workflow  currently is.


A little easier is to know who actually approved a document, because this info is stored in the change log (table CDHDR and CDPOS), still there is no report to list this for a number of purchasing documents.

Release strategy without classification

This is the remnant from R/2 times and only possible for purchase requistions. The release strategy with classification came with R/3 in 1996. But maybe you have no complex requirement and a strategy based on plant, material group and value is just enough for you, then you may want to look into this document for the setup:

Setting Up Release Procedure for PR without classification.

Since the release strategy with classification can be setup for the same criteria you should better use this way instead of spending time learning an out dated method.

No changes

Coming back to the design meetings, make it clear that the outcome should be a strategy which can be used long-term and is not subject to continuing changes and “improvements”. Better improve your preparation.

Changes in a release strategy are not recommended if this strategy is in use and will lead to errors. Create a new strategy, never delete existing strategies. Have no open documents unapproved if you are going to change anything.

Read KBA 1635346 – Add a new release code to the release strategy of PR issue

If you really need to change, then it is very important that you do it in the right sequence.

Deletion of Existing Release Strategy in SAP ECC

Just deleting the release group does not make the depending customizing going away. It is more like beheading a chicken, it can still run through the yard as some videos in Youtube show. However, the SAP customizing is still there and troubles you for more than a minute. Technically it means you have still data in table T16FS, which is the table that stores the release codes to a strategy. This table has the key fields release group and release strategy.

So you can have several entries with the same release strategy. This actually happens frequently after a deletion and new definition, the numerous discussions are evident. The problem is that SAP does not search for a record by the combination of release group and release strategy, it only searches with the strategy, so you have to make sure that the strategy number is unique and exists just once in that table. Otherwise SAP will take just one and this may have a release code that is not covered in any role and nobody can release your document.

Client Rel. Group Rel. Strategy Rel. Code 1 Rel. Code 2 Rel. Code 3 Rel. Code 4 Rel. Code 5 Rel. Code 6 Rel. Code 7 Rel. Code 8
800 AA 01 06 04
800 BB 01 01 <<< THIS IS AN ISSUE
800 CC 02 01

 

Check your customizing with OMGSCK to ensure it is consistent and error free before you  test it or even release it for production.

see also OSS note 2417519 – Release strategy selected in transaction CL30N but does not exist in configuration in customizing

 

 

Workflow

Further you need to decide if you want to make use of a workflow. This means that the purchasing document is directly routed to the approver(s).

Any extra feature has advantages and disadvantages. An advantage is certainly that a manager get an email when a new document is waiting for approval and does not need to execute release transactions in SAP to see if there is anything to approve.

A most common error is that the person who gets the workflow has not the roles to approve the document. Workflow for approval does not replace the user roles. It is your developer task to keep roles and workflow synchronous. The workflow requires  discipline by the users.  When you decide to go for workflow, then make it clear that the people execute the release through the workflow only. The workflow is an extra process which stays open if you use the normal transactions to release the documents. So you have extra work to end the workflow.

If the workflow is made on individual users instead of groups then the users have to activate a forwarding rule to their substitute  in SBWP Business workplace transaction when they take vacation.

Blogs an documents related to release strategy and workflow in SCN are

SAP MM: Purchase Requisition with Classification and Workflow Approval

Work Flow Mail Generation for Release Procedure in Sourcing Module

Release strategy Vs Workflow release of purchasing documents

in the modern world you even approve with tablet computers and smartphones:

SAP FIORI : Approve Purchase Contract App

Online Purchase request (PR) Approval Application Using Blackberry

A workflow Application to Release A Purchase Order…

Multiple currencies

Purchase requisitions are internal documents which either take the value from material master, or if there is no material master the user is forced to enter a value as estimate. This value is always in the value of the company code.

A purchase order is an external document which may have the value in your vendors currency.

Your release strategy  can be defined to be used in several companies around the world with different currencies.

All these case may require to define a release strategy with multiple currencies.

See the SCN content on multiple currencies:

Use of multiple currencies in Release Strategy – ERP SCM – SCN Wiki

Purchasing Doc. Release with Multiple Currencies

Multiple Currencies in Purchase Order Release Strategy

and the official KBA: 1739381 – Multiple currencies in purchase order release strategy needed

Transport Strategies

Transport of release strategies is not easy as a release strategy with classification is a mix of customizing and master data (classification) and eventually even program coding if you make use of the exits.

Please read OSS note 86900 – Transport of Release strategies (OMGQ,OMGS)

Master data is usually not transported and need to be created in QA and PRD systems again manually, which is a source for errors too. An way out is to use ALE distribution for the classification. You have to decide yourself how much data you would need to maintain manually again and if ALE can save you time, or just creates another complicated hurdle.

Beside of many discussions we have 2 documents on transporting of classification:

Characteristic value movement across Systems through ALE in Release Strategy Implementation

a better one (my personal view): Transport of classification across systems/clients – Quick Reference

ABAP to close the gap between standard and business requirement

The user exit for release strategies was already explained in Release Strategy Enhancement in Purchase Order

Still there might be other requirements that are not foreseen by SAP, here are a some documents and blogs explaining some special developments

Release Strategy: Restrict lower users to revoke PO after the complete release by superior

From the ABAP space, but you should be able to read ABAP, as some developers are not able to describe it for non-ABAPers  How to Reset Purchase Order Release Strategy

Sending  EMail Notification when PR is released from ME54/ME54N/ME55

if you have so many strategies and you need to load them instead of doing customizing: Mass Upload of Purchase Order Release Codes and Release Strategies – A Function Module Approach

This document closes the knowledge gap between functional and ABAP world, worth to read it from both parties:

Triggering of release strategy for a Purchasing document – a developmental overview

Printing purchase order with release strategy

In SAP standard it is not possible to print a document which is not approved. This makes sense, otherwise you could submit a document which is legally binding to your vendor while you did not have the approval. Of course there are ways with ABAP methods to get around this restriction, in that case you have to take organisational measures to avoid sending this document. Or the ABAPer programs it to print with watermark “DRAFT” . If your document prints while it is not fully approved and it is not wanted, then call your ABAPer as it is a homemade problem.

more background is given in OSS note 61871 – Output of messages and release strategy

In case of email and fax the last approver will be used as sender (hence he need to have a valid email address in his profile).

There is a SAP note with a modification to change this behavior: 561593 – Sender of the message (fax and/or email) is wrong.

Other valuable content  and important SAP notes

Rahul explains his findings when working with different scenarios in Release strategies

Release Strategy Scenarios

this wiki gives design insight regarding deleted documents in regard to release strategies

Release Strategy with deleted Purchase Requisition and Purchase Document – ERP SCM – SCN Wiki

I have not seen many questions on release strategies with purchase orders on hold, but it was nice to read the background of the design in

KBA 1981241 – Missing release strategy tab for purchase orders put on hold

Some more questions were posted recently about release strategy and version management

Release strategy with Version number is in general only triggered if the version is complete.

2 important KBAs on release strategy with version management are:

1961482 – Reset release strategy when version number is set as Characteristic in Customizing

1961585 – Release strategy is not triggered when Version number is set as a Characteristic

Make sure you have gone through the FAQ notes before  you post a question in SCN:

16 question and answers in OSS note 493900 – FAQ: Release Strategy

some more in OSS note 365604 – FAQ: Release strategies in purchasing

and 10 more on services in OSS note 672719 – FAQ: Release strategies in the service

and a SAP given PDF documentation in OSS note 207490 – Release procedure purchasing: Documentation for Customizing

Please never miss to read the related notes that are mentioned at the bottom or in the text of these notes.

Analyzing issues and errors

If you have studied all referenced content above then I actually do not expect any more errors and issues. But you may have overlooked an important information or you really have a new problem.

There is a SCN blog with a check list in case of issues and as well a KBA in the market place and many wikis in SCN

MM – Check List to detect and solve Release Strategy Issues

1497235 – Release strategy is not determined for Purchase Requisition in t-code ME51(N)/ME52(N) or Purchase Order in t-code ME21(N)/ME22(N)

Check List to detect and solve Release Strategy Issues – ERP SCM – SCN Wiki

Why is no release strategy determined – ERP SCM – SCN Wiki

Beside of that explicit mentioned content we have 6500 discussions for release strategy. Here you should search to see if your issue was already addressed before you create a question.

But if you create a question, then please not a one-liner like this: “My Release condition is in PO level,when i am creating PR and converting to PO the release procedure is not working at PO level.

This sentence has almost no information to work on. What does “not working” mean? is there an error message? does the strategy not trigger? It is not told on what criteria the release strategy is built and no evidence that the data entered matches with this setup.

A release strategy can be compare with this geometry brick box for children (2-4 years old). The box is your customizing, the bricks is the data in your document. This has to match exactly, and when all your bricks at put into the right holes, then the release strategy triggers.

intelligenzrelease.PNG

Hence if you have a problem, give information about your box and show us the bricks, but do not present an empty image:

empty.PNG

To report this post you need to login first.

50 Comments

You must be Logged on to comment or reply to a post.

  1. Mohsin Abbasi

    Dear Sir,

    I recently have the good fortune of reading your above mention Blog regarding Release strategies. It is very well-written and contained sound, practical advices. In fact, I have already benefited from your discussion on Release strategy as well.


    Superb and in depth explanation …………….. 😳



    Best Regards

    Mohsin Abbasi

    (0) 
  2. PRASOON AK

    Thanks for sharing the excellent doc, Jurgen. This doc will be the wiki for Release strategy related issues 🙂 .

    Regards,

    Prasoon

    (0) 
  3. vidya G

    thank you Jurgen  for sharing detail explanation about release strategy it help to get a clear idea on release strategy.. 🙂

    (0) 
  4. Melih Özbağı

    Hi Jürgen,

    Excellent blog! Explains almost every side of release strategy.

    But it has almost been 15 years that SAP introduced release strategy for purchase documents. Since then, without programming, we still can’t reset release strategy, expect reasons explained in note 493900, or can’t use different class for releasing purchase documents such as purchase order, RFQ and outline agreement.

    I really wonder at which release SAP will handle topics.

    (0) 
  5. Patrick FMK

    Hi Jurgen

    Excellent Document.

    You pin point one issue I’m facing with my Client. He wants to restrict lower users to revoke PO after the complete release from the CEO. In the same time, approvers could reject PO at their level. I understand why the moderator reject my post on yesterday 😕 because so much debates already exist.

    This is such evidence from a business standpoint to restrict lower users. Why do SAP did not think about such aspect. 

    (0) 
    1. Jürgen L Post author

      maybe they did think about it and did not find valid reasons for this restriction.

      The time between a final release and printing the PO is usually short. After printing (faxing, email sending) you can no longer reject a release. Reversing a decision needs to take immediate effect otherwise you are bound to your order.

      The information is often distributed, if one person had all information then you would not need several level of approvals. If all approvals together release a document, then 1 reversal of a decision has to stop this release since the preconditions are no longer given.

      I can understand that a CEO does not want to get overruled by a lower level employee, but he had actually never known about this document if it was never approved by this low level employee.

      Going with the cascade requires that the information that this document approval needs to be withdrawn  has to flow by email or phone from one level to the next, or does a supervisor really call the CEO?

      And then reversing the approval level for level backwards takes time and extra human interaction. I think this huge effort is not needed for something that you want to stop from being ordered.

      (0) 
  6. Peter Kamenik

    Man,

    I just…wow… I have experienced just few situations like that. State when you realize that there is a being on this world who went through the same stuff as I did, got the same opinion on particular issues.

    For several years I am trying to struggle with PR workflow, wrote many ABAP enhancements to make it easy for users as possible (automatic authorization for deputies, reports from CDPOS and predicting the approvers, etc) however it got out of my hands completely. I got around 300 release strategies in one system and its not even half of the organizational structure of the company. It was such a small cute puppy in the beggining, ten years ago, release strategies only for maintenance PRs, 10 organizational levels, three “dollar value” levels. And now it has grown to the fiery beast. I think the time has come to implement a fully number-9-rule workflow codes and to make a custom algorhitm for the workflow. Kill the beast and start again, avoiding the mistake that we made before. Like to get married again 🙂 . God give me the power to push this idea to the highest bussines user.

    Thank you and OMGQ forever.

    (0) 
  7. subburam v

    Hi Mr.Jurgen,

    Very good document… This particular document will clarify all doubts regarding Release Strategy Process.

    Great Work!!!! 🙂

    Regards

    Subbu.

    (0) 
  8. Thiyagaraaj Shanmugam

    Hi Jurgen

    Awesome article with interesting funny facts in between (like porche, approver’s vacations and shark bite etc.,). Gave me good information on release strategy and off-course good laugh 😆 .

    Regards

    Thiyagaraj Shanmugam

    (0) 
  9. Periyakaruppan Renganathan

    Hi Jurgen

    Awesome Explanation. It will help a lot for both who working in support & implementation Projects. Its like a master note. You played it well. Hats off to you.

    Regards,

    Periyakaruppan Renganathan

    (0) 
  10. Amit Anasane

    Dear Jurgen,

    Exceptional document for Purchasing release strategy, covers each and every part of it. hats off to you.

    thanks for sharing, writing and educating all of us.

    (0) 
  11. mayank solanki

    Dear Jurgen,

    An amazing blog with loads of useful information on Release Strategy. All doubt clarification at one place, I really appreciate that.

    I have one more doubt in my mind, if you can clarify that(Please).

    What is significance of release group ?

    Can there be a scenario where we have to make different release group for release of PO only. If yes , what condition will determine that we have to use different release group.Please clarify. I am bit confused at this point.

    To be more clear on my point, as we can assign only one class to all release group(if many release group is created for PO). We can achieve same scenario by creating only one release group and distinguish the release on basis of classification.

    (0) 
  12. Pablo Vignale

    Excelent Post.

    I have a new Question….. Whe have converted a PR to a PO, and by mistake someone cancel the PR approval 2 months later….. How can we avoid this behavior? is Possible?

    Thanks a lot! ➕

    (0) 
  13. Amit Tunara

    Hello Sir,

    Very well written blog and covers all aspects.

    Thank you very much for your continuous effort on SCN for educating us.

    Regards,

    Amit

    (0) 
  14. Christine Kühberger

    Hello Jürgen,
    thank you very much for the excellent information.
    I have a question because I am just implementing a release strategy for purchase requisitions based on cost centers and approval amounts, I guess similar to your example. I am trying to find out whether multiple release groups would be a benefit of any kind for my scenario. Until I saw the excel screenshot in your blog I thought it is common to use only one release group for header level approval and I would like to understand the benefit of using more than one release group).
    I was planning to create the following:
    – one release code per approver ( I think you use the same release code for several groups of costcenters?)
    – one release strategy per group of cost centers and Euro amount range (1 approver until 500€, two approvers until 2000,…)
    – one authorization role per release code

    I have the feeling I am missing something, but I think the overall ongoing maintenance effort cannot be reduced by using more than one release group, is that right? You still have to maintain the classification for every combination of value and group of cost centers and you still have the same amount of authorization roles.

    Can I somehow optimize the ongoing maintenance effort (new cost centers have to be entered in the classification for multiple release strategies, … )?

    Thank you very much in advance.

    (0) 
  15. Martin Verner

    hello Jurgen,

     

    Great blog, really helpful! Unfortunately it seems some of related documents are not available anymore, like the one you call a jewel :/

    (0) 
    1. Jürgen L Post author

      I know about this and hope that SAP restores the documents that were lost in transition, because of this hope I had not removed the link yet.

      If you search the web by the titel like this “Release Strategy Enhancement in Purchase Order”

      then you can find a copy of it in other places, as SCN content is often copied

      (0) 
  16. Alexandros Ntais

    HI again Jurgen,

     

    Once again excellent document, many thanks for your constant support. One question.

    I have frequent requirements of PO approval based on CC or WBS.

    How did you do it in your example (as CEKKO structure do not have these values)? Did you append CEKKO and passed the value of CC there and then with the ME_PROCESS_PO_CUST badi to restrict multiple PO account assignment?

    Is this a good business solution (as we are then missing the multiple account functionality).

    BR

    (0) 
    1. Jürgen L Post author

      The  account assignment line with the largest value is used for strategy determination. And the approvers are  responsible minded managers, as the approvers accepted this standard approach there was not need to restrict the  system functionality  of multiple account assignment.

       

      (0) 
  17. Alexandros Ntais

    So you pass the account assignment of the largest value to CEKKO (append) and define the RS or you just have specific levels of approval and you search with an exit the approver?

    I am trying to understand how they approve the PO, thought ME28? If it is through wf and Fiori app it’s ok but from ME28 every cost center approver is able to approve every PO, correct?

     

    BR

    (0) 
    1. Jürgen L Post author

      there is no extra activity from me, it is just standard SAP that it takes the cost center from the largest value, searches then for a suitable strategy with that information to finally get release group and release code which is needed to release this PO. And everybody who has a role with that group and code can release.

      (0) 
  18. anthony custodio

    Thanks for this wonderful document! Hope you will not get tired of sharing your knowledge…

    And maybe a document like this for MRP would be your next blog 😀 😀 😀

     

    (1) 
  19. Niru Mani

    Great blog.   Detailed explanation.  I have one question to ask here.

    I have an existing Release Strategy with 2 Release codes.  Example RelGrp. AA, Rel Strategy B1 and two Rel.codes – 01(Manager), 03(General Manager).  Now the business unit wants to add Rel.Code -02(Snr Manager) in between RC 01 and 03.  I did changes to Rel Strategy in Dev and there are values in the classification like (PR Type, PR total value, Plant, Cost Center, AAC). I know transport from DEV to QK or QK to PROD will only transport the structure and not the classification values.

    My question here is while transporting structure from one environment to other what will happen to the values in classification ?  Do I need to delete the values before transporting TR and re-keyin values again after transporting ?  OR shall I leave it untouched during transporting ?  what will happen ? Please advise.

    I appreciate whoever replies.  Thanks in advance. 🙂

     

     

    (0) 
    1. Jürgen L Post author

      Somehow you must have read to quickly through the blog as you missed the sections “No Changes” and “Transport Strategies”

      (0) 
      1. Niru Mani

        Hi Jurgen

        I read about “No Changes” section, but my company Rel Strategy was implemented quite long ago.  We cannot avoid changes when there is a change in business requirement.

        There should be some way to do that.  I am looking for a solution for my issue.

        I appreciate anyone who has a solution.  Thanks.

        (0) 
        1. Jürgen L Post author

          The solution is quite easy: you have to customize a new strategy.

          Make use of your search skills and find some hundred discussions where people screwed up their strategy with changes. SAP has not released the KBA’s that I mentioned for no reason.

          (0) 

Leave a Reply