PO Release strategy question

Hi,
In PO release startegy,
Plant- XXXX
YYYY
BLANK
Purchase group, Total net order value, order type are the characteristics currently defined.
PO is created at company code level..with multiple plants-i mean, XXXX, YYYY.
rekease strategy does not work in case, if line items have account assignment and item category.
pl help

CEKKO is a structure for purchase order header.
The plant in purchase order header is only filled in case of UB stock transport order, where you do not have a vendor, here you would only have the supplying plant.
You are talking about plant in item level, which is requesting plant, not the supplying plant.
You can never reach your goal until you CHANGE your design.
you either create only POs which have only items of one single plant (must be controlled via user exit) or you just cannot have a release strategy that works. It is just black or white.

Similar Messages

ME54N Release strategy question over delivery tolerance limits

I set up a release strategy base on the over delivery tolerance level. My problem is when a Purchase requisition is saved as rejected, and i click on the button cancel reject it deletes the last release strategy level because now it is looking at the actual total value disregarding the over delivery tolerance level.
It works fine when the Purchase requisition is not rejected, and i can cancel or reject the purchase requisition without saving it and it does not delete the last line of the release strategy taking into account the over delivery tolerance level. I am using the user exit ZXM06U13.
Can someone give me some insight into this ? Thanks.

Hi Siva:
You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
Good luck
Z.T

Another Release Strategy Question - Multi currency

Hello,
I have been searching for an answer to my delema to no avail on this board, but no answer yet.
My problem:
We have a Purchase Req. strategy with approval by Plant, Cost Center, and Total PR Value.
The PR Value Characteristic is in US Dollars, but one of our companies is in Europe so we also need to have a PR Value Characteristic in Euros.
Currently we have:
Characteristic: Z_PR_AMT referencing field CEBAN-GFWRT. This is in US Dollars.
                         Z_PR_WERKS referencing field CEBAN-WERKS
                         Z_PR_KOSTL referencing field CEBAN-KOSTL.
Class:              Z_PR_CLA with references to Characteristics: Z_PR_AMT, Z_PR_WERKS, and
                         Z_PR_KOSTL.
Release Group: A1 that is assigned to class Z_PR_CLA
Also, currently all PR's under $1000 (US Dollars) go through Workflow for release, and if the PR is over $1000 (US Dollars), requires a 2nd release.
But, since we have a company in Europe, we also need to be able to have a Release Characteristic for Euros so that PR's in Europe under 1000 Euros go to a new release strategy, and PR's in Europe over 1000 Euros go to a 2nd release strategy.
Can I add a new Characteristic to the Z_PR_CLA refering to the same CEBAN-GFWRT field, but use currency EUR (lets say Characteristic ZPR_AMT_E). Then in CL20N (Classifications) when I am adding the actual values, leave the value information blank for the European Amount characteristic and fill in the US Amount and assign to a US Release Strategy.   Then leave blank the US Amount charastieric field and fill in the European Amount characteristic field for Europe Release Strategies?
Will this work?
Thanks in advance.

That is the problem we are trying to avoid. We do not want to have to put in a manually converted 1,000 Euros to US Dollars.
Currently we have a US Dollar limit for our European plant set at $1,474.30 which is to represent 1,000 Euros. But this number changes with the fluxuation of the currency rates.
So far in testing I do have 2 Characteristics defined for Currency, one for US Dollars and the other for Euros. Both Characteristics have amounts loaded in them (via the CL20N screen).
I do see in my debug sessions that there is a currency conversion to foreign currency in the LEBNDF01 include program, but since I have 2 Characteristics for Currency in the CL20N screen for this particular Release Strategy, this is messing up the conversion to foreign currency.
I still have more debugging to go.

Release Strategy Question

Hi,
Can anyone explain me with example, why is it that we can have only one class and not more, when configuring groups in the release strategy.
Why is it mandatory to have only one class for overall and one class for line item release, can someone explain with examples.
The system allows creation of multiple groups, but all have to use the same Class when it comes to overall release/ Line item release.
I am not able to understand the reason behind this restriction as of now, can someone share some insights.
Thanks
Shailesh

Hi,
Better & always keep one release class ....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.Under each separate class keep your requires characteristics.Then do necessary confuguration for release statergy.
For more check the links:
/people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
Re: Class and release group and code in release strategy??
Regards,
Biju K

Release Strategy - question about requisitioner??

Hello,
I have set up a release strategy for my PR based also on the requisitioner (CEBAN/AFNAM).
If specific requisitioners (listed into my characteristic RELEASE_REQUISITIONER) create a PR, the PR should be released before creating the PO.
BUT if an other requisitioner who creates a PR doesn't belong to my release strategy, this requisitioner is allowed to create this PR without any release procedure behind it, and then he's free to create the PO.
How can I avoid this ?
How can I say to my characteristic to take in charge ALL requisitionner (I tried with * or xxxx or... but however I don't know if there is a specific word to say "all").
Thank you for your help...
François.

Unfortunatelly this is not the case.
On the PR, when I change the requisitioner with one who doen't belong to the defined release strategy, the release strategy tab disapears from the PR and I get this warning "Requisition not subject any release strategy following changes"
The PR is automatically ready for PO....
In fact I would like to work like this:
If requisitioner is AAA or BBB, work with release strategy X
For all other requisitioner from my company, work with release strategy Y
But this is "all other requisitioner" I cannot translate to my release strategy...
Thank you for your help

Acknowledging old P.O's : retriggers Release Strategy?

Hello,
I know that when you acknowledge an old Purchase Order in the Confirmations tab, it can retrigger the Release Strategy, therefore disapproving the P.O.
Does this apply also if we acknowledge a P.O line item that has the Account Assignement Category "Y" (Non-Recurring)?
Example:
P.O line item #1: part number ABC, already acknowledged
P.O line item #2: "Y" non-rec charges, not acknowledged
If we acknowledge line item 2, will it retrigger the Release Strategy?
Patricia

Hi,
   The release strategy re-triggering depends on the release indicator used and it will re-trigger only if there is a value change or new strategy is determined. If you are simply flagging acknowledgement in a PO, it wont make any value change / new strategy and hence new release wont be triggered. Please check the note: 493900 - FAQ: Release Strategy Question number 3
   Also, please check whether version management is activated for the PO document type and version number is used as release characteristic. The release strategy will reset when version is set to complete and the new total net value is higher than the old net value. Refer the note: 1961482 - Reset release strategy when version number is set as Characteristic in Customizing
   You may note the above two points and analyze whether new strategy will be triggered for the corresponding changes in PO.
Regards,
AKPT

Release strategy H8 Update

Hi Experts,
We wanted to know who changed the release strategy H8 value in our SAP system.
Found that PRD System release strategy GT value has been updated somehow with in six months.
please let us know how to check find out who updated value?.
Thanks
Malai

Hello Malai,
I think that for "Release Strategy" questions you should opan a thread under category SAP Community Network Forums » SAP Solutions » ERP - Logistics Materials Management (MM).
Please, go to and formulate your question.
Best regards,
Rafa

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

How to Display PO Release Strategy in Enjoy Screen

Dear all,
I have a PO with a release strategy, which contain several release codes to release the PO (i.e. M1 & V1).
However, I am only able to display the release code (i.e. M1 & V1) in t-code ME23. I could not do the same in the enjoy screen t-code ME23N for the same PO number.
In the item level, there should be a tab with release strategy to display the PO release strategy (similar to PR), but it is not appearing.
Could anyone tell me what is the problem here? I just could not find the tab or menu to view the release strategy of a PO in the enjoy screen. Similar goes to other PO. I could not view it as well. But in the old screen, I could view it.
Thanks a lot.

Thanks 4 the reply Rahul.
I understand that it is only possible to release at header level. What my problem is that I am unable to view the release strategy (which code to release and who to release) for the PO in enjoy screen.
In my earlier thread replying to Ankur, I am simply describing that I could just select a line item, click on the release strategy button and the release strategy is displayed. A different line item with different value generated a different release strategy of course. Different amount require different set of release strategies, usually more level of approvals.
So, actually this question is not about where or how I can release a PO, but actually I could not view who is releasing for a PO in ME23N.
I even simulate it in the development server and still the same thing happen. Is it the same for everyone else? If yes, how to view who is releasing the PO in ME23N? Version of system is 4.7.
Thanks and appreciate if anyone could help.

With a lock item in a purchase order, release strategy works?

Dear All,
I have a very important question for myself.
I have a purchase order with only one item.
I have set this item to locked.
Release strategy works without problems.
Is this situation correct?
I don't understand it but maybe the release strategy works normally too....
Please help me with a explanation
Thanks in advance

Yes, if a release strategy is applied to a PO, then even if you block / delete an item, it will still have the release strategy.
This is standard behaviour, because you can later remove the deletion indicator or unblock the PO, whence the PO will again have to go through the Release Procedure.

Change in Purchase Order Release Strategy Values

Dear All,
I am in process of changing Purchase Order release strategy values.
I have following release strategy -
                       Current Value                  (Proposed Value)
Level 1 -         Upto INR 0.1 Mn               (Proposed value - Upto 1.0 Mn)
Level 2 -         From 0.11 Mn to 0.5 Mn   (Proposed Value - From 1.01 Mn to 5.00 Mn)
Level 3 -         From 0.51 Mn to 1.0 Mn   (Proposed Value - From 5.01 Mn to 10.0 Mn)
Level 4 -         Above 1.0 Mn                  (Proposed Value - Above 10.0 Mn)
My questions are -
1) Will this change affect the existing Purchase Orders (already created) which are not yet released?
2) Will this change affect the existing Purchase Orders (already created) which are released?
3) Are there any risk factors?
Can you pl. put light on above questions?
Regards,
Prashant Kolhatkar

Hi,
Actually, what you had given is not enough to determine if the existing PO will be impacted or not
If you are just changing the classification but not changing the number of release level of the release code in the release strategy, the partial released PO will not be impacted unless there's PO changes. PO that are released will definitely not be impacted unless there are changed.
In general, after a release strategy is determined for PO, SAP will retrieve the latest list of release code of that release strategy for display for that PO. If this list never change (mean you only change classification of the release strategy), then they will not be apparent to the user. But if this list change (you add new release code, replace existing release code or remove release code), then you will see some discrepency on screen as you will only see the modified list of release code and not the old list of release code
Hope this help

Purchase order -- release strategy

Dear Friends,
I have a requirement for Purchase order Release.
The problem area is in purchase order ... there will be 2 Relase approvals
01 Mr. Abcd
02 Mr. Xyz
After level 1 approval and before level 2 approval ... i want to do some actions.. these actions are related to another product named savvion .
My question is can i stop the document to be edited by 02 ( Mr.Xyz ) untill i complete my process after 01( Mr.Abcd ) has finished his work.
This is to be done on top priority.
Please help me.
Cheers
Jitesh.

Hi,
Yes, We can stop the document to be edited by 02 until 01 has finished his work.
After 01 approved the document need to be correct, go to PO header menu release strategy TAB and 01 approved to be revoked (means double click on the tick mark, it will revoked).
Hope it is useful for you.
Regards,
K.Rajendran

PO release strategy report

Dear Experts,
we are creating one report.
PO release strategy report for Audit purpose.
Who created
When created
TIme should be display
user id and user code.
for example, we have 4 levels for PO release.
All 4 persons should approve for this PO.
we need to know level wise when they released who released.
how to take this

Moderator message: Basic frequently asked question - Please search forum for answers and read the docu in help.sap.com
See as well our rules of engagement: http://scn.sap.com/docs/DOC-18590
This blog describes how to use the SCN search:http://scn.sap.com/community/about/blog/2012/12/04/how-to-use-scn-search
Another good way to search the forum is with google. See this blog with details for a good search
http://scn.sap.com/community/support/blog/2012/04/16/getting-the-most-out-of-google-optimizing-your-search-queries
The discussions are not a replacement for proper training
Thread locked

Purchase Order not subject to release strategy

Good day everyone!
I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
My question is: How to assign purchasing document to release strategy?
Please help. Thank you in advance.
Anisah

hi
yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
now below i am giving u one by one steps , follow and let me know .
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic   e.g. NETVALUE
Click Additional data Table name CEKKO      Field name GNETW    and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X    Mutliple values
X    Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group   Rel. Object   Class                 Description
02                                 REL_PUR        Rel. Strategy for PO
Release codes - New entries
Grp         Code
02           01
Release indicators
Release indicators           Release        Description
      0                                                        Blocked
      1                                     X                Release
Release Strategy
Release group   02
Rel.strategy    01
Release codes   01
Release status   0
                        1
Classification   Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a 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 have to use ME28 to release the Purchase Order.
regards
ravikant dewangan

Purchase Order Release Strategy didn't trigger

Hi Gurus and SAP People!
Good Day!
I currently have a problem regarding one purchase order which didn't trigger a release strategy. I checked the classification/conditions/classes and it's all satisfied. I tried replicating the scenario in our Development server and I always end up triggering a release strategy.
Moreover, as far as i know, the release procedure is not locked as it is one of the most commonly used release group and code. Can anyone have any ideas why that certain PO didn't trigger any release procedure upon saving?
More details that might help.
1. PO was initially on hold status then saved. (tried to replicate this as well and yet a release strategy was triggered)
2. Upon saving, PO triggered an IDoc successfully. (my replication results always stayed "yellow" as it is still waiting to be released/approved before the actual Idoc generation (green)).
3. Line item details had been changed between the PO being on hold and the actual saving. (but yet it still satisfies the release classifications)
4. Line items came from PRs, Contracts, RFQs.
Will greatly appreciate your help.
Thank you very much!
Regards,
JV

Hi Suzy!
Thanks for the answer.
I already checked the classification and searched our documentation repository if there were changes made and did not find any. Development and Production environment customization are the same.
I forgot to include that after a few days the PO was created, they deleted one line item. That deletion made the PO trigger a release strategy.
Nevertheless, the question still remains - why the PO didn't trigger any release procedure upon the initial saving.
Regards,
JV

PO Release strategy question

Similar Messages

Maybe you are looking for