PR Release Strategy Re-determining due to Change in Text

The PR release strategy was configured by a previous company. There are existing PRs that are not completely approved (Release Indicator = 2). The SAP instanced was transitioned to the company that broke away.
The PR release has now been re-configured with new release strategies (groups, codes..etc). What we are experiencing is that the existing PRs that are "released" do not show the new release strategy when the combination of release strategy/release group does not exist- This OK as well.
When a user made a change to the Item Text and nothing else, SAP re-determined the release strategy and started the release process over again. Is there a way to stop these PRs from re-determining and therefore restarting?

Hi There
Though the release strategy is different, i think all the classifications are same or old classification (even 4 or 5 parameters) may also part of your new full release strategy(You may be trimmed from old release).
So when you do any changes or just go to the change mode and Check (F7) , system may find the new rel strategy.
i have not tested the above scenario, i could recall some older posting based on that i did suggest the above
Thanks Senthil P

Similar Messages

Purchase Requisition Release Strategy not to run when change to PGrp

We have buyers that are required to change the purchasing group on the purchase requisition before a PO is created. We would like to allow them to do this without triggering the release strategy. Any ideas?? Thanks.

release strategy will change only in the case if you cahnge value or oquntity other wise it will not retrggering.
If you change the Purcvhase group system will not tregger the release
let me know if oyu have any other problems

Release strategy not trigerred if PR changed after Approval

Dear Gurus,
I have a requirement kindly help.   We have a PR generated from PS module, This PR is released by the approver. After the Approval, PS user change the PR qty and value has been increased. Now my client wants that this PR should be again sent for approval and release strategy should be trigerred. After the approval my release indicator is 2 RFQ/Purchase Order. I have set the Changeability indicator to 4 and define the tolerance to 0.1 %.
But PR release not trigerred even after this. Kidnly help.
Thanks.
Johi

Hi Johi,
Check note 493900 point 3:
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.
I hope this helps.
Regards,
Ashwini.

Need workaround - Release strategy

Hi,
I have done three release strategy(R.S.) for PO.
First R.S. is from 0 t0 9,999
Second R.S. is from 10,000 to 99,999
Third R.S. is from 100,000 to 500.000.
When the PO value is 250,000 the third R.S. comes to picture and it is released by people concern.
When the same PO value is decreased from 250,000 to 90,000 the PO is de-released and it goes back to second R.S.
wherein the enduser is not comfortable as the PO is already released with third R.S..
Enduser do not want to release again using second R.S.
Please suggest to stop from derelease after it is released by third R.S.....

Hi Vishnu,
See Note 662993 on conditions based on which release strategies are reset.
When quantities or values are decreased, the system resets the release
only if a different release strategy is determined for the lower
quantity or the lower value.
If no different release strategy is determined due to the quantity or
the value decreasing, the system retains the releases that already
exist.
This is the desired standard system behavior.
As it also says: "This function can be changed only by a customer-specific modification."
So there is no standard way of achieving this.
Hope this helps.
Purnima.

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

Overall Purchase requisition Release strategy : Changed after Rejected

Hi All,
I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
Problem I have is when PR is rejected .
When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point.
ME52 changes for PR is not trigerring any event which can trigger the WF.
Is there any way we can trigger Workflow in this scenerio.
Please suggest.

Hi Subhashini,
This all depend on release strategy. release should reset completely on tha change.
For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
Sanjeev

Release Strategy to be reset for any change in purchase order

Hi Experts,
At present the release strategy configured is for any change in the value of the purchase order, the release strategy is reset. Now the the client wants that for even any text change of a word, text, quantity, value, addition, deletion the release strategy should be reset.
Can any one guide to configure the release strategy for any change. Also please provide the list of standard parameters/scenario (E.g. change of price, change of quantity etc) for which the release strategy can be configured to be reset.
Thanks in advance.
AJ

Hi Diwakar,
I too have the same problem. I tried with Changeable indicator "1". The system does not allow to make any change to the Purchase Order even after the first level of Release. But the requirement is that the system should Reset the Release Strategy for even minor Change in the PO.
Regards,
S.Raghavan

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

PO release strategy ONLY for change

I have a requirement to only have a release strategy for a purchase order only when it is changed
The problem is that even if I can disable the event to be triggered when created, the release strategy is written down to the EKKO-table when the PO is created meaning that the purchase order still needs to be released before being used for example in MIRO.
How can I avoid having the release strategy written to the EKKO-table when the PO is created?
How can I have it written to the EKKO-table when it is changed?
Good answers will ofcourse be rewarded with points!
Edited by: Snowroller on Feb 11, 2012 4:00 PM

Dear,
Check this and try. Not tested.
Set up Version management for Purchase order and keep all relevant fields of PO relevant for version change.
Add charaecteristics PO_Version value as 00000001. So, When you create PO the version will be 0 so no release strategy. Whenever relevant fields changes the version changes to 0 to 1 and release strategy triggers.
Try this option.
Regards,
Syed Hussain.
Forget to mention please search with 'PO release strategy based on Version Management in SAP' you will get many SDN posts.
Edited by: Syed Hussain on Feb 11, 2012 7:27 PM

Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

Hi Friends,
I have a issue to fix. The issue is releated to PR.
There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
I have to retrigger the release strategy for all the affected PR's.
The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
Regards,
Manjunath K

Hi,
Refer the discussion to triggers release again on release code addition/change in release strategy.
release code is changed on PR release strategy - old PR can´t be approved
Regards,
Biju K

PO release strategy is not triggering if Quantity pre.Qty

Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.

Hi.
According to note 493900, question 4, release strategy is reset only
for some specific case. Alternatively, please question 5 from this note
release strategy might be redetermined. However in order to determine a
new release strategy the field that is changed in PO must be included
as one of the fields in the strategy. Thus there is no standard way
for resetting/redermining release strategy for a change of e.g. text
on header or item level.
Please also kindly refer to other 2 useful notes for this area:
662993 Resetting an already occurred release
365604 FAQ: Release strategies in purchasing
BR
Nadia Orlandi

Sap release strategy

dear gurus,
             I have created a release strategy. it is working fine. if i edit it in such a manner, that the po value increases, it goes for re-releasing. but the issue is, if i edit it in such a manner that the PO Value decreases it does not go fo re-release.
              so my requirement is that, if the PO value goes down it should go for re-releasing
thanks
ujwal

Hi,
please see the note 662993 Resetting an already occurred release.
"When you reduce quantities or values the system only resets the release
if another release strategy is determined for the lower quantity or the
lower value.
If no other release strategy is determined by the reduction of the
amount or value, the system will keep already existing releases.
This is a standard functionality and is desired.
A change of this functionality is only possible by means of a
customer-specific modification."
In standard there is no customizing setting to change this behaviour.
You need to use userexit EXIT_SAPLEBND_002 or modify
the standard function module ME_REL_STRATEGIE_EKKO for this.
Regards,
Edit

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.

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

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
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.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

PR Release Strategy Re-determining due to Change in Text

Similar Messages

Maybe you are looking for