PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Hello everyone,
I've run into an interesting problem:
We have defined several PO release strategies. Most of these work in the traditional manner, requiring manual approval by a given user. One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
What would cause this discrepancy? The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
Thank you ahead of time for your help.
-Jarrod

Configuration issue/user error.

Similar Messages

PO Release strategy Workflow issue

Hi All Workflow Experts,
I need a help in one of the workflows in our project.The workflow is for PO Release Strategy.The problem is in the Production environment and is as mentioned below:
''Users are complaining of irrelevant mails with subject "PRD: PO auto release code" delivered to their lotus notes inbox from SAP workflow. Mail does not carry any further details like whats the PO number etc. In some cases this mail should not be delivered to the recipients as they have nothing to do with PO release strategy approval process.''
As I am not very old in Workflows I want to know where should I start from? I mean what all are the possible
areas where I should look into? Also this issue cannot be replicated in QA environment? So is there any environment specific thing I should do?
Please advice.
Thanks,
Saket.

Hi Saket,
Check who are set as the Recipient types of the workflow mail "PRD: PO auto release code". Also check the condition when the mail is getting send. Check at occurance of what event is the mail getting send to the users. Debug the workflow to fidn out these details and check where the issue really is.
Do post your comments if you find any confusion about the same.
For assistance on workflows, the following links would help you:
http://****************/Tutorials/Workflow/Workflow.htm
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/workflow%252bscenario
/people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i
Hope this helps!
Regards,
Saumya

Release strategy does not reset after PO change - tried changeability 4 & 6

Hi,
After my PO is released, I change the item quantity/price such that the net PO value (increased) is changed MORE than the tolerance % set in the changeability. I expect that the PO release should be reset but it does not.
However if my PO value is changed (increase) such that my PO value is now in a different "release bracket/range" -- as it falls into a different release strategy, then the release is reset.
Could anyone advise me what is wrong? I tried everything - i tried changeability = 4 and 6. i deleted the whole release class, release strategies and recreated -- nothing.
According to OSS note 493900 below, it should reset when the tolerance % is breached.
I'm on SAP 4.7.
Anyone could advise?
thanks!
     3. Question :
     Why is the release strategy not reset ?
     Answer :
     A reset of the release strategy only takes place if
            - the changeability of the release indicator is set to '4' in
               case of a purchase requisition and '4' or '6' in case of
               another purchasing document (purchase order, request for
               quotation, contract, scheduling agreement),
            - the document is still subject to the previous release
               strategy,
            - the new TOTAL NET ORDER VALUE is higher than the old one.
     The total net order value is linked to CEKKO-GNETW for a purchase order,
     CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
     for a purchase requisition overall release.
     If you have maintained a Tolerance for value changes during release
     (V_161S-TLFAE), the release strategy is reset when the value of the
     document is higher than the percentage you have specified and if the
     document is still subject to the previous release strategy.

Hi,
Thanks.
The release strategies are able to be determined correctly when the PO is created so I guess that means its all setup correctly?
The issue is only with PO change - how to cause the reset when the PO value increases by more than the tolerance %.
cheers.

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

Issue with PO Release strategy

Hi experts,
I have problem with Po release strategy in 5 to 10 purchase orders, i have created few purchase orders(2000 Po's) with same document type and company code ..etc and saved, then release strategy has been triggered.
For few purhcase orders release strategy has not been triggered.
If i take 1 po from that few purchase orders(Release strategy has not triggered) as reference and again if i create PO,new purchase order have getting created with release strategy.
Can some body tel how this ican be possible, hope this might be standard syatem behaviour.
Hope i should delete thos e purchase orders and i should create new PO's instead of of old PO's (Without release strategy).
Some experts can share their experiance in this regard.
And how i should proceed further with this issue.??
Thanks

Hi,
You issue in your system has 2000Nou2019s purchase orders with release strategy has been triggered but 5 to 10 purchase orders do have release strategy.
& when you are creating a new PO with reference to old purchase orders (which release strategy has not triggered) and on saving NEW PO created with triggering release strategy.
Cause for above:
PO which release strategy does not trigger because the purchase orders are created before setting release strategy for PO. Those PO triggered release strategy and all are created after setting release strategy for PO.
Action:
Its completely business call for business users to go for options:
Option-- >1# You can use same old PO which release strategy does not triggered, do GR and all other process
Option-- >2# You can create new PO with reference old PO which release strategy does not triggered and upon saving you will have new PO number with release strategy triggered, then release PO & do GR and other related process.
Regards,
Biju K

Issue in Release strategy for PO while adding intermediate rel code/Strateg

Hi Experts,
we have Existing release code 10,20,30,40,50 & 60. Now, we tried to add an intermediate Release Code(say 25) & release strategy(say R3) in existing release set up for PO.
And NO pre-requisite is defined ; final release by the last rel code.
However, the system shows release possible by 30 & 40 for last release strategy also. It`s showing the alternate release as release possible.
Pls throw some light on resolving the issue....
Regards,
Ganesh S....

Thanks Ajit.
I mean the release should get afftected only after release 60. (i.e. final approver) That`s the way it`s been working.
Now, while I tried adding 1 more rel code in between ; it`s afftecting the release with (20+40) instead of the intended 60.
BR,
Ganesh

Issue with Purchase Requisition Release strategy

Hi Gurus,
We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group
3.     Value of the PR
As a result of PM module implementation, there is requirement of additional 30 release strategies.
We configured them but one more field of doc type was added in the characteristics fields.
Now the release strategy was based upon following fields:
1.     Creation Indicator of PR-R (Configured only for manually created PRs)
2.     Purchasing Group-(Configured against new purchasing groups )
3.     Value of the PR
4.     Document type of purchase requisitions.
Classification data was accordingly maintained that is for older release strategies,
Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
We are in testing phase. Many of the test scripts failed due to this issue.
Quick response will be appreciated!!!
Thanks & Regards,
Niti

Dear Niti,
Please check if your "overall release" indicator is consistent for document type and release group:
a)SPRO:MM-PUR-PR-Define Document Type
"overall release" indicator
b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
->Release group
"overall release" indicator
Regards,
ian,Wong Loke Foong

Purchase requisition release strategy issue

I have created release strategy in development, it was working fine with work flow. When I try to import the TR's I found that the document types in development are not in quality so I changed the document type. then I tried to create a PR and when I clicked on messages its not triggering the release strategy don't know why. In total there are 2 characteristic plant and document type.I even tried to delete the plant characteristic and tried again creating PR but still no use. let me put some screen shots comparing the development and quality. Please do help.

Thanks for the quick reply, I just checked that the over all indicator for the development and quality, I found that in development its not activated while its activated in quality will that be of any issue.
In development
In Quality

Issue in Purchase Requisition Release Strategy

Hi guru,
I've got an issue in the release strategy;
I have a PR with 3 lines. After Relase I've deleted the last line and system doesn't allow me to release it by ME55 transaction; I'm able to do it only by ME54N.
Thank you for your help.
M.

Hi Marco,
I had a problem with ME55 and i wrote to SAP OSS.
The first OSS answer was:
Can it be that your requisition has some deleted items?. If yes, then
take into account the following:
Please consider the definition of ME55 "Collective release":
You release ALL requisition ITEMS or COMPLETE requisitions that are
awaiting processing by your release code.
And also the definition of "the field overall release of PReq":
Determines that the items in a purchase requisition are ALL released at
at the same time (rather than individually).
That means:
If there are some items which can't be released (may be they are
deleted), the transaction ME55 can't be used - so you have to release
over the individual release (and that's why you get this
message in ME55).
If you get such a message for a purchase req. in ME55 you can go over
the menu to release this item(so you don't have to call ME54 directly):
Select the item and choose Goto -> Individual release.
There is a difference between overall release and collective release.
Overall release means that a purchase requisition is released on
header level and not on item level. Collective release means that
several purchase requisitions can be released at the same time.
When one line of a requisition subject to overall release is deleted
you are asked to use the "single release" functionality in transaction
ME54.
Once you delete a line item you MUST work with ME54 to release each
item. By deleting a line you effect the whole purchase requisition
hence collective cannot be used. This is standard SAP functionality.
In this case, you have to individually release each requisition item
through transaction ME54.
I hope this is useful to you.
Ciao
Alberto

PO Release Strategy Issue

HI,
We have created a PO release strategy workflow.All scenarios are working fine except 1 scenario.
That is,when a PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.
If the release strategy is for a different user,its triggering the workflow.
I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Can anyone tell the solution for why the workflow is not triggering for only this scenario?
Thanks,
Aparna.

Feddie wrote:>
> Kjetil, I am not clear still, could you explain me a bit clear. I have not seen any tool tip in my release tab.
Don't you see any buttons in the subscreen? The tooltip is not for the tab (title) it is for the button. I am quite sure there is a button there for cancelling the rejection, but without access to a system where this has been set up I can't check it. I just had the same issue before Christmas, where the users said the solution didn't work for the same reason mentioned here - no workflow was sent after changes where made. In fact the solution did work flawlessly as soon as they cancelled the rejection.
See also [documentation at help.sap.com|http://help.sap.com/erp2005_ehp_02/helpdata/en/4c/16443c4a089537e10000000a114084/frameset.htm|ERP release ECC 6.0] for the workflow for rejected purchase orders.

Issue: Purchase order release strategy with storage loaction.

Hi Friends,
I have created release strategy for purchase order considering following characteristics.
1. Plant
2. Purchase organization
3. Purchase group
4. Document type
Hence the release strategy is working fine.
Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
Can any one tell me how to maintain this LGORT filed in structure CEKKO.
Thanks in advance
Shashidhar

HI Shashi ,
Thanks for your quick response,
I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
Also we written the code :move: i_cekko = e_cekko, in user User-Exit M06E0004 function exit
FUNCTION EXIT_SAPLEBND_002.
However, the release strategy is not triggering when PO is saved,
also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
in it.
Kindly reply.
Thanks ,
Shashidhar

Scheduling Agreement Release Strategy Issue

Hi,
We have a typical problem in Scheduling Agreement Release Strategy.
Once the SA is released for the first time it should restart the release strategy again if there is a change in Quantity or Value or Purchasing group. The release strategy is getting restart for some of the release strategies and not for others. I compared the characteristics, class for both the release strategies and I am not seeing any difference.
Can anyone please help me in this regard.
Thanks in advance.
Regards
Ram

release strategy can be rerigger in case where qty or price change and the changes is over the percentage you defined for Release indicator
goto release indicator config and in SPRO for release strategy and check the Value change %
maintian 0.1 here
so any change above 0.1 will retrigger
and maintian value 4 in chgable field.

Import container contains errors issue for Release Strategy workflow

Hello Experts,
I have copied the standard workflow WS20000075 for PO approval on Release step.
the copied workflow works fine in sandbox system, but in the test system I get an error saying 'import container contains errors (are any obligatory elements missing?)' I guess 'ReleaseCode' is not getting passed to the Workflow from the PO creation T-code.
I went thru few SCN post, did check all the Linkages as said, everything seems to be ok. but still cannot trigger the workflow.
need guidance as to where I may be going wrong.
Regards,
Jibran

Hi Jibran
If the WF is working in sandbox, it means that your definition, linkages etc are correct.
Please check if the following note is relevant for you or not:
1770720 - PO workflows run into error SFW_RUN594 - Import container contains errors
It's about correcting the settings in SWEC and SWE2 (correct for your custom workflow definition)
If not, then confirm with your MM consultant if the release strategy is configured correctly or not....take hints from the following SCN thread:
http://scn.sap.com/message/14682486#14682486
Regards,
Modak

Issue with Purchase Requisition Release Strategy (Approval)

Hi There,
I am facing an isssue with the PR Release Strategy. Please read the description below.
When a PR is created the PR Release Strategy is getting determined correctly. But the problem is that for example, if the Strategy has found a two level approval, the system is allowing level 1 user to approve both the levels, which should not be the case. User 1 should be allowed to approve only Level 1.
Though the system is currently allowing the same user to approve both the levels. If User 1 approves only Level 1 and saves the PR then the PR approval notification goes to User 2. So there is nothing wrong with the workflow or notification.
It is just that system is allowing the User to approve both the levels.
Any help is appreciated and rewarded.
Thanks,
Chan

Hi,
I believed releases strategy correctly designed with release prerequisites.
Now need to check following in basis side by having a purchase order release matrix.
Lets say you have following release codes
C1 & C2
AND
Having following users
U1 & U2
Now give authorization to user U1 to release with release code C1 and user U2 to release with release code C2 ONLY.
Regards,
Biju K

Re-set release strategy of rejected PO,after doing respective changes to po

Hi friends,
I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...
Here PO printout is possible only after the final approval...
Pls give some inputs in fixing this issue..
Thanks in advance....
Regards
Shashidhar...

Hi
What are the characteristics of your strategy?
Try to change one of them save and then rechange it to the original
eg.
If the strategy depends for example on the Purchasing Group (PG)
i mean according to different PG's different strategies working
then with ME22N change the PG save and rechange it again to the original.
or
for example If the strategy depends on Materail Groups (MG)
then do the change with MG
With ME22N change the MG save and rechange it again to the original.
I guess this will trigger the strategy again.
Hope it helps
Best Regards

PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Similar Messages

Maybe you are looking for