If PO changes must go to release strategy again

Dear Expert,
Present release strategy is changable.After final release , PO can be change. My client want if changes took place in PO , it should go into release strategy again. please help

Hi,
Please go to SPRO -> MM -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders -> Define Release Procedure for Purchase Orders -> Release Indicator
Here you have to maintain Chgable as 6 i.e Changeable, new release in case of new strategy and % Value change as 0.
Please note even if you maintain as above, in case if you are lowering value of PO the changes won't go for release. It will work only when the changes are on positive side. Else you need to use User Exit for same.
Hope it helps.
Thnx.

Similar Messages

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

Release strategy: problems after changing the price

HI Experts,
I have the follwing problem.
I´ve setup the release strategy for Purchase reqs.
The strategy includes 3 approval levels.
release indicator with changeability 4 and a value of 0,1% for the first two approval levels.
I´m able to release it, but if I release the first two appoval levels and change the Preq the release strategy goes back to the first level. Fine.
But the problem is now that I´m able to release the first level but if I try to release the second one I get a error message.
I guess the problem is the changeability - but how can I solve this issue?
The system have the cancel all approvals if someone changes the price.
Any ideas?
Thanks
Alex

HI RJ,
the exact message is "Release prerequisite not fulfilled".
The system should act in the following way:
Approval levels:
1. Supervisor
2. Manager
3. General Manager
1 and 2 is approved.
Then the requisitioner changes the price.
Release will be changeled (Releases already effected will be cancelled).
OK that work, now the release process starts with level 1.
1. Approved --> OK
2- try to approve and get the message "Release prerequisite not fulfilled".
1 and 2 have the same release indicator with 4 and 0,1%.
Thanks
Alex

PR release strategy reset after change in quantity/inclusion of line item

If a user adds a line item or increases the quantity of an existing line item to a fully released purcahse requisition, then the system does not render the PR for reapproval. Is there any way to configure SAP such that the release strategy resets if any of the above changes are made in a fully approved PR?

Hi,
the release strategy will ONLY be reset if one of the fields that are contained in your classification are changed.
For example
If you strategy is determined by Plant and value, if the plant or value doesn't change then the release strategy will not be affected.
So if you change qty and do not change value then the release strategy will not be reset. This is a basic limitation of the design.
But if you ARE changing one of the characteristic values of your strategy and you are saying that the release strategy is not being reset, then something else is wrong.
Steve B

What is the name of the table where Release Strategy changes are maintained

Dear Friends,
Every time I make the changes in the Release Strategy Codes the Signature of the Approver changes in the Output. The problem is that it even changes for the Older PO's which are already approved by some other approver. Is there any way this problem can be sorted out? or can any one give the name of the table which records the changes made in the Release Strategy along with time and date? I will be really thankful if you guys can help me out!

Hi Chintan,
I hope you are talking about the release codes, which we attach later on to user Ids and signature means its description. I hope followed correctly.
In standard system, as and when you change the description of release code at back end, it gets reflected on front end. No matter whether its old or new PO. There is no way out to stop this. Every time you display the purchase order, the release codes checks for description at back end and displayes the same. Still, it should not bother you, as the already released PO dosent get affected for any changes you do at back end in the entire release strategy.
Beside the tables mentioned by other friends AUSP is the table where all release related entries gets stored.
I hope it clarifies.
Regards
sachin

Release Strategy - Purchase requistion go back to unreleased

Hi Friends,
I am facing two problem in release strategy in our client system.
Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
Current System Settings;-
Release Procedure:- Procedure with classification ( Also setting available for setup procedure without classification maintained )
Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
Value maintained in CL24N for plant , Creation indicator.
Release Indicator:- 1 Stage:- X. Blocked
2 Nd Stage:- 4.RFQ/PO no changes
Scenario :- When PR is created and released , If any one changes the Purchase Group in any line item which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
I checked all the system setting and it seems to be correct except when i use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
Checks re requisns. with item-wise release 3
-> Checks re release group and release class 2
-> No release group exists 1
Problem. 2:- Purchase Requisition not triggering when PR is created from other source linked to SAP.
Please suggest the solution for the above problem.

Hello Kunal,
A few thoughts and questions on your problem:
You generally can't have both release procedure without classification and release procedure with classification working at the same time.
To get the system with classification working, you have to have several things in place and consistent: You need a release group. It should have a class. That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release). You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
You have to choose item-based or overall release for each requisition document type. You mark this on the document type. You must also choose the same option for the release groups that the document type will be assigned to. Example: document type NB is item-based. Document type ZB is overall. Document type will be a characteristic. CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ. Release group NN will be marked as item-based. Release group ZB will be marked as overall-based. Usually, I think, you will just use one or the other, and it will be less complicated, but the release group must match the document type.
The indicators themselves have some configuration, including a field for changeability. Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
If you are using workflow, there might be custom events related to the business objects involved that can change things, as well.
Are you using workflow?
Are you using overall or item-based release?
Good luck,
- Jeff

Cancellation of release strategy

Hello to all,
i have release strategy defined for purchase requisition and i want that when a post is deleted from the purchase requisition, the release strategy is canceled and must be released again.
How to setup this.
Regards.
Zied.

Hi ,
In the release indicator mention 4 for chageability and mention some % for the value change.
You have to check your scenario for the release indicator.
Also for change in value only Release strategy will be reapplied and not in any other case.
Regards
Ankur

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.

Problem in purchase requisition release strategy code

Hi
We are facing a problem in purchase requisition, a new release strategy was created and change request transported but when PR is displayed in release strategy chart a same user is showed in different release strategy code.
Note: new strategy was copied from other.
Thanks in advance.

hi,
As you said tht you have copied the release stategy n created the new one...
If you do so, you would have copied the class also...to which the release group is attached...
If this is the case, then system doesn't recognise the new one, and inorder to solve it you have to define the new characteristic and class...then assign this class to the release group and make your release strategy again...
Once you do this check the release strategy at OMGSCK...and then try at PR...
You do all settings at :
SPRO >> IMG>> MM >> Purchasing >> PR >> define release strategy >> W/o classification >> here edit characteristics/class and all other link are provided...
Regards
Priyanka.P

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.

Release strategy tab is not coming in SES

Hi All,
I am facing a issue where I have created an SES, and release strategy is assigned to this SES. Problem is somehow the user is not able to see the release tab when he go wants to release the SES. The release tab is missing from the SES.
Am sure somebody has faced this kind of issue and have any idea how to correct this.
Thanks

Hi,
The direct reason that there is no release icon available in ML81N
is inconsistency in the field ESSR-FRGRL for affected SES's.
This field should be filled with 'X' as all those SES are subject
for release.
Have you changed customizing for involved release strategy recently ?
If a relase strategy is created with a certain name and documents are
created with respect to it afterwards, this release strategy should be
changed then IF AND ONLY IF a NEW name is assigned to it as well. In
other words, if such a strategy is already use, it should be RENAMED
before applying the desired changes.
Otherwise you will run into the observed inconsistencies when trying to
edit documents which were created BEFORE the strategy was changed
(since the system at some point always checks the NAME of the strategy
to be changed, NOT the content).
So if this case happens only for already created SES a good solution
for it is to delete affected SES and create a new one with changed
release strategy.
I would delete affected SES and create it again.
It seems to be the fastest way to resolve this issue.
If you need a correction for this inconsistency issue, please open a SAP ticket for your problem.
Regards,
Edit

Block PO in ME22N - release strategy

Hello Abapers,
I have been trying to block a PO under the following scenario.
A user creates a PO for 1000 and submits to manager.
The manager approves the PO.
The user amends the PO and reduces the amount.
What the functional guys want to happen is that in this scenario, the PO should be blocked until the PO is reapproved by the manager.
I have tried user exits and BADIs and have changed the field EKKO-FRGKE to 'B' (blocked) upon saving when the conditions are met.
When I look at EKKO in SE16, the field FRGKE = B, so it looks like the change was successful.
However, when I look at the PO, the tab for 'Release Strategy' in the PO header is missing. The functional guys assure me that this tab should be visible.
So, my question is, is my logic too simplistic (changing EKKO-FRGKE to 'B' )?
Should I be changing data for the release strategy as well?
Thanks in advance,
Kevin

Thanks Christine.
I know that functionality is already in place using classification characteristics, that if the PO is over a certain amount, then the PO is blocked.
However, the functional guys told me that it is not possible to check for reductions in PO amount using classification data.
I will check out the FM in your post.

Purchase Order Release strategy revoke when Delivery Comp indicator Ticked

Dear Experts,
There is PO for 100.Release strategy is activated for PO.PO is released.
Inbound Delivery for 100 was done .after which for 70 Goods reciept was done.
Then User wanted to Short close as no more quantiy is going to come.
So user went to ME22n and Done Delivey completed indicator was ticked which can be done Without Re-Release.
But When i am seeing the Log of PO (Both Header and Item Changes) The Release strategy is again Getting Revoked,
And going to Release again.
What should i do for not revoking Release strategy.And Also Price is getting Changed.
with regards,
GMP

hi,
Release strategy is revoked via release indicator settings done via settings up the release strategy...
If you don't want any revoke even if any field is changed then used the changebility as '1'...
Also as per std sap settings, once you make changes to com. indicator in PO, system will revoke the release again...
so, decide and make settings as you need...
Regards
Priyanka.P

Scheduling agreement Release strategy release indicator

Hi all
For the Scheduling aggreement Release strategy is present & release indicator is 6 , Now the requirement is whenever user is changing the any value Scheduling agrrement it should go for rerelease. for any minor change in value even the value lies between the same Release strategy
Release strategy is configured on Purchase group & Value character
Also what is the difference between release indicator 4 & 6. for any changes in the SLA release strategy will be reset in this two release indicator.
Thanks & Regards,
Rajesh

Hi,
This is a standard phenomena any change in value (increase)will reset the release stategy
and indicator 4 & 6 are same only in case od indicator 6 if you have taken the oout also it will get affected

Release Strategy in Contract

Hello Guru
I have Created a Contract and when ever i want to change the Contract my release Strategy has to be re triggered and my version management is Active.
I tried to change the Value in Contract and when i do change the Value and if i ticked the Version on the Header of the Contract then my new release Strategy has to be re triggered but its not happening. when i checked the tick box in version in Contract it is saving but when i come out of the Contract it is showing unticked again.
I am unable to re trigger the Contract and if i tick the Version in the header of the Contract when i close it untick the verison it is not saving, how can i do this, please let me know
Sreedhar

Release strategy will trigger again when the version will be completed.
You have to tick the flag as version complete for contract, only the release strategy will be reset.
Be sure you release indicator has the Changeable as 6.
Then make the version complete for release strategy as below :
Once you will click the version complete flag, then version complete tick will also displayed.
Have a look into the similar discussion Re: Release changeable indicator 6 not working

If PO changes must go to release strategy again

Similar Messages

Maybe you are looking for