Trigger PO release strategy

How to retrigger PO release strategy after delete the items in ME22N?
It only be retrigger when we increase the price.
Any user exits dat retrigger the changes made?
Where is the user exits located?
Or any standard configuration need to be done.
I already set the Release indicator, changeable = 6, and % = 0.
I am using 470 version.
Please help to provide some solution.
Thanks.
Edited by: Elaine Tang on Jul 3, 2009 8:02 AM

Hi,
As for as I know, SAP has not provided the retrigger of PO release strategy if the Value of PO is decreased than the released PO price. It will only retrigger if PO price is increased than released one.
There is no User exit available for this, you can use the Version management usuage for any changes made in PO using the availble user exits.
There are lot of discussions done on this Retrigger of PO release strategy for any changes in PO -- but till now there is no positive result. Don't why SAP has not taken this issue very seriously.
If any others has found any solutions on this, let them share the information on this .
rgds
gsc

Similar Messages

ML81N Enhancement to trigger the 'Release Strategy'..very urgent !!

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active, because the minimum value should be 5000$ to trigger the 'Release Strategy'.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy (the one for 5000$) even when the amount is less than $2500.
I have already tried with the ser exit EXIT_SAPLEBND_003, its a blank user exit and the structure available is CESSR.
Can any one tell me how to activate the 'Release Strategy' tab and the lowest Release stratedy should be selected ????
What i have investigated is that once i will set the Release Strategy to the lowest Release stratedy then that tab will automatically become active.
Please tell me how to select the lowest Release strategy using the CESSR structure ?
Points will be awarded...
Thanks
Rahul

Use this exit.
MM06E005

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 not triggered after PO printout

Hi Experts,
I have configured PO release strategy and have given 10% tolerance to PO value.
When I change PO value (more than 10%) after releasing the PO, but before taking Print out of PO, the system triggers new release strategy.
But when I change the PO value (More than 10%) after taking PO print out, system do not trigger the new release strategy.
I want the system to trigger new release strategy after PO print out (if its going beyond the tolerance).
Please help.
regards,
Anand

Hi Anand,
you cannot reset the release once the PO is printed.
When the purchase order is printed/faxed the vendor will deliver the goods. Therefore it would make no sense if the system resets the strategy.
Please ensure that changeability of the release indicator should be 5 or 6.
Sanjeev

PO Release strategy User Exit if value is Reduced

Hi,
I need to write a user exit to trigger the release strategy in Purchase order even if the value is "Reduced".
As you may be knowing releases will only be triggered if the value is increased according to standard SAP functionality.
So to trigger the release stratgey even if the value of PO is reduced some one suggested me user exit "M06E0004" Program :ZXM06U22.I guess we need to define a new characteristic called "URSC1".But cannot make out how really i can achieve this.
Can any one please guide,if you have worked on it earlier.
Thanks.

Gentlemen,
Any Ideas....!!!

PR/PO release strategy should be revoked

Hi Experts,
How to revoke the release of a PR /PO if value is decreased. In standard only value increase will revoke the release strategy. I am having overall release of a PR.
Regards

This cannot be achieved through standard release strategy configuration.
Basically the requirement is any change on PO price should result in blocking of the PO. You can create a custom field in the PO header that will function as a Price Change Indicator. Add this indicator to the release class and trigger the release strategy when the Price Change indicator is set to "Yes". Populating this custom field with value "Yes / No" should be carried out using a user-exit by invoking it in the PO change transaction.

Release strategy for PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

Purchase Requisition Release Strategy help

SAP Gurus,
I have set up PR release strategies for item level and it is not working. Our setup is as follows:
Document type NB with "Overall release of purchase requisitions" unchecked
3 characteristics defined: one for Line item total, cost center, and an account assignment category.
1 class with all three characteristics assigned
1 Release group with "Overall release of purchase requisitions" unchecked
104 different release codes
127 different release strategies with varying combinations of cost centers and dollar amounts.
Executed cl24n with all release strategies.
Now when i enter a PR with amounts and cost centers that should trigger the release strategy, it is not triggering.
I executed CL30N with different parameters and none of them register.
The only clue i have as to what could be wrong is when running OMGQCK, it lists that the release group does not exist, but it does. Message 620401/2006 references note 365604 lists the problem i am experiencing, but none of the suggested steps have corrected the problem.
I would appreciate any suggestions anyone has on what i can try to get this release strategy working
Thanks,
Rachel

hi,
Check your release codes and its assignments in the release strategy..
Also do check whether the PR is liable to trigger for the given characteristics as compared to your PR which you are making...
Regards
Priyanka.P

Release Strategy for more than 8 levels

Hi experts,
Can anybody have a clue how to get Release Strategy for more that 8 levels or anybody who have configured the same. Standart SAP supports 8 levels of Release Strategy. So How to enhance the standard feature with additional Levels.
Thanks in Advance

Hi Senthil,
Thanks for the suggestion.
You mean to say :
That a purchasing document which has some 16 llevels of release strategy can be accomplished through :
1. Release Strategy configured through 8 levels.
2. A custom table needs to be created where based on one of the classification (Usrc01) feild of 1st Release Strategy should be mapped to another Usrc01 feild for some other Release Strategy2.
OR
2. Custom table have Release Strategy 1 name and another feild will have Release Strategy 2 lined to 1st Release Strategy.
3. Based on FRGGR and FRGCO and ZTable should trigger next Release Strategy 2. But hou will this be displayed and what about Change History?
Thanks that was an innovative idea but can u please elaborate.
Thanks in advance.
Ashutosh

Release strategy for RFQ's not triggered after change

Folks,
Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
1) document type (AN)
2) purchasing type (RFQ purchasing document)
It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
Message was edited by:
MdZ

Hi,
For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
As RFQ don't have any specific table where the data is stored related to RFQ.
So we Use CEKKO which only identifies the document type of RFQ.
In your case in initial process while creating the RFQ release strategy is active.
What change you have made to the Released RFQ.
rgds
Chidanand

BAPI_PO_CREATE1 not triggering Release Strategy

Hi,
We are using the BAPI, BAPI_PO_CREATE1 to create Purchase Orders Programmatically. But this way the Release strategy is not being triggered and the PO is directly being sent instead of blocking for the Releases.
Whereas the appropriate release strategy is being triggered when the PO is created using ME21N using the same data that was used in the BAPI (Same Purchase Value, Purchase Group etc..).
Is there any Option in the BAPI to trigger the Release Strategy or any OSS Note or any customization requirement to resolve this issue.
Regards,
Rajeshwar Rao J

Hi,
I hope this issue was resolved...
Please help how it was released .
i am also getting the same problem (my system is upgraded from 4.7 to ecc6 in ecc6 only we have implemented Bapi to create PO)
Thanks
A. Prasad

Release strategy should refresh when deleted PR is undeleted .

Hi all,
My client requires as below for PR's,
The PR release strategy should get to intial at any stage if the PR is released for some releae codes earlier, deleted & after the PR is undeleted.
Regards
Ashish

This cannot be achieved through standard release strategy configuration.
Basically the requirement is any change on PO price should result in blocking of the PO. You can create a custom field in the PO header that will function as a Price Change Indicator. Add this indicator to the release class and trigger the release strategy when the Price Change indicator is set to "Yes". Populating this custom field with value "Yes / No" should be carried out using a user-exit by invoking it in the PO change transaction.

Release strategy should trigger in different systems EHP7 and ECC6

Hi All,
At our client side some are using ECC 6 and few are on EHP7.We need to define the release strategy in a such a way that both the user can approve the PR in cross system.For example- user A is using ECC6 and he created PR ,now he need to take approval from his manager and manager is using the system EHP7 in such scenario-
how does the system understand who is the approver?
How to maintain the same user in both the system? so that approval process can not be disturb .
What about the release code ? how to define release code in both system for single release strategy
Thanks

Hello,
1st thanks for reply.
We have ECC 6.0 as live system but getting used in only A & B country.We bought new fresh,blank system EHP7 for C county. We defined release strategy in EHP7 but we have HR module in ECC6 .So all portions are defined in ECC 6.
For example- I am creating PR in EHP7 & last level approver is in ECC 6 .
The issue is, in the ECC 6 system how will he get the email notification of approval mail.?in EHP7 there is no HR module configured.
Thanks,
Snehal

Purchase Requisition Release Strategy wont trigger

All:
I have set up what i thought was a simple purchase requisition release strategy. Parameters are as follows:
1.) Doc Type = NB set up as CEBAN-BSART
2.) Acct Assn Category = k set up as CEBAN-KNTTP
3.) Purch Org = 300 set up as CEBAN-EKORG
4.) Overall Value = 0-1000, 1000-10000, 10000-50000, >50000 set up as CEBAN-GFWRT
Release group is set for overall release, i've checked the release strategy with OMGQCK and everything was good to go, checked CL30N and everything was triggering, checked table T16FS and there weren't any fishy entries. Oh also, i've tried deleting and recreating the entire release strategy at least 3 times.
Whenever i create a purchase requisition, i get no release tab. Not sure what else i'm missing here.
Any help is appreciated!

I created 4 characteristic with the above mentioned criteria (doc type, purch org, net value, & account assignment category). I assigned all 4 of these characteristics to a class.
Matrix is as follows:
0-1000, doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01
1000-10000 doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01 & 02
10000-50000 doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01, 02, & 03
>50000 doc type NB, purch org 3000, acct assignment 'k' needs approval from release code 01, 02, 03, & 04

User exit ML81N.....Name of user exit to trigger 'Release Strategy'..urgent

Hi Guys,
ML81N work in a manner such that if the net amount for any PO/Service entry is less than $2500 then its 'Release Strategy' tab is not active.
I have a requirement where i have to make that tab active and select the Lowest Release Strategy when the amount is less than $2500.
Can anyone please tell me the name of the user exit that controls the 'Release strategy'.
Points will be awarded...
Thanks
Rahul

Hi
Your settlement rule says "Settle to Cost Center" only.... I dont think any user exit can help in this case, if you want to settle occasioanlly to 2 cost objects
Try with these options
Option A
1. Remove the 100% validation tick in the settlement profile...
2. Maintain 2 settlement rules... i.e. One with Cost center and another with PSG... If any warning comes, ignore it
3. Execute settlement now
Option B
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, Menu GO TO > DETAILS and maintain Cost Center also....
3. Now execute settlement...
Option C
1. Maintain settlement rule with PSG as settlement receiver
2. In the same Settlement rule, populate Cost Center also as a Valid Characteristic
3. Now execute settlement...
BR,Ajay M

Trigger PO release strategy

Similar Messages

Maybe you are looking for