Release strategy affecting old POs

Hi Experts,
When we tried to cancel the material document by tcode MBST , we got the error  message  u201C Purchasing document  not yet releasedu201D
This  PO and  related GRs were created before we implemented PO release functionality.  Even then, the system looks for PO release while reversing the old GR documents.
If we release this PO now,  it will go to top management level for further approval.
Please advice whether we can  process OLD POs without  effecting releasing  procedure
Many thanks,

thankyou for the replies.
finally we got minor price change done manually in all the POs to get the new rel strategy on them
Open POs , no change done - Did not pick release strategy (then it was no problem at the first place)
Open POs , change done in price - picked the new release strategy
Open POs ,  no change done but click on 'check' button in change mode - Could not test this one bcoz all POs are now converted. But I put break point in save user exit (which also plays part in determining the new release strategy) it did not stop at the break point and I gave message 'No data changed' so I think this action will not redetermine release strategy. It was very useful if it did though.
thank you.

Similar Messages

  • How to apply newly transported release strategy to existing POs ?

    Hi,
    We transported a new release strategy to production
    The new POs created are catching the rel strat B if they meet criteria
    But some of the existing POs also meet the criteria for B and they should also take up this new release strategy
    We cannot change the POs in ME22N, busines refuses to make any change to POs
    How can we apply our new rel strategy to these POs ? has the SAP provided any standard function module to report?
    thank you
    B

    thankyou for the replies.
    finally we got minor price change done manually in all the POs to get the new rel strategy on them
    Open POs , no change done - Did not pick release strategy (then it was no problem at the first place)
    Open POs , change done in price - picked the new release strategy
    Open POs ,  no change done but click on 'check' button in change mode - Could not test this one bcoz all POs are now converted. But I put break point in save user exit (which also plays part in determining the new release strategy) it did not stop at the break point and I gave message 'No data changed' so I think this action will not redetermine release strategy. It was very useful if it did though.
    thank you.

  • Release strategy for Release POs

    Hi Every one,
    We have a requirement.
    A contract is created and approved as per the regular strategy.
    The releases (POs) are created against it and sent directly to the vendor.
    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
    But the business wants the PO releases too to follow the release strategy.
    Can you please look in to this and let me what changes we need to make this happen.
    Regards
    Pavan

    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
    This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
    As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
    So that the Release Process is applicable to PO's created w.r.to Contract also..
    For ex: if you use the field purchase Doc category as a Character  in  the Release , it differentiates whether it is PO or Contract..
    So that you can define different Release Strategy for PO & Contract
    Or  if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
    then the release strategy applies to PO also..

  • Purchae requisition Release strategy not Invoked

    Hi,
    I  have Purchase requisition Release startegy.
    Criteria is
    1. Account assignment category -K
    2. Material Group suppose -001
    3. Plant - 4001
    4. Valuation Price - 1000 USD.
    Then Release staregy got Invoked. Presently it is working fine.
    I have Created another Release strategy for with same criteria but I have added another criteria with user name- ernam.
    Same thing I have created characterstic and assigned to Class.
    CL24N and CL20N also Maintained.
    But this New Release stragey Not Invoked and Old one only invoked at the time of requsition created.
    Please guide me is there any configuration to Invoke this new Strategy?
    Regards,
    Sridhar.

    Hi Indranil,
    Thanks for your response.
    I thought user name will differentiate the new release strategy with old one.
    I am using same parameters in both strategies.
    Plants, Material groups, Cost center same with old one.  New release strategy very few members are going to use.
    Business is few users will create Pur Req. Users are not having release codes. Tracking number also used in another release strategy.
    Regards,
    Sridhar.

  • Old POs affected by release strategy change

    Hello,
    Recently major changes were made to a group of release strategies for our business. The new release strategies are being applied correctly to all new POs. However, even POs created before the change of release strategies are showing the new strategies. Even the old POs which have already been released and goods received are showing the new strategies. How can this be corrected? POs created before the change should be showing the old strategies. Thanks in advance.
    Regards

    Hi,
    First of all, I don't suggest to bring back the old release strategies as it will mess up the entire system and to me it does not make sense at all as the efforts to solve these issues with old POs are significant and believe me, you will encounter a lot of pains and frustration.  What I suggest hereunder is as simple and effective as I thought given your current situation -
    1)   In regard to those old POs (I hope the number is small up to now) to which the new release strategies are applied, you will have to use ME28 for mass release.  Of course, you can develop the simple ABAP program which can allow mass approval (if you wish to).
    2a)   If you did not eradicate your old release strategies through configuration (i.e. you used only "2" to block your old release strategies in CL20N Transaction), then you can select the proper value in the "Changeability" field of your "released" release indicator that was used in your old release strategies.  This selection will allow the fact that no new release strategy will be applied for your old POs in case of change.
    2b)  If it turns out that your old release strategies were deleted from the current system (which I don't really know why), then the only solution you should do is to inform your end users of not making any change in the old POs.
    Cheers,
    HT

  • New release strategy should not trgger for PO released with old Rel Strategy

    Hi All,
    Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy  XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
    But requirement is if there is  any change or value decreasing in fully released Pos with old strategy  it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
    Please help me on this.
    regards,
    Rohit

    HI Rohit
    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 most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
    The commom steps are:
    1- make sure all of the old POs should have been released.
    2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
    3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
    Kind regards,
    Lorraine

  • New release strategy / Old PReqs

    Hi,
    New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
    But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
    Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
    Many thanks in advance for your clues.
    Regards,
    Grzegorz

    Hi,
    Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

  • 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

  • PR Old Release Strategy - triggering NEW Release strategy any change OLD PR

    Dear Gurus,
    We have implement item level PR release strategy,
    characteristic used:  1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
    BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
    Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
    Please advice
    REgards
    RS

    HI,
    If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
    ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
    Is this is standard behaviour? pleae advice
    Regards
    RS

  • Old PR release strategy - release completed status change

    Dear Gurus,
    We have impletemented Item level release strategy for PR.
    There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
    Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
    Please advice
    Regards
    RS

    Hi,
    Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
    Check the value of Changeability of purchasing document during/after release  ( 1 - 6).
    Choose the appropriate value based on your req.
    Regards,
    Udayasankar Rajagopalan
    Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

  • Affect on release strategy by ME22N

    Dear All,
    I want to know that in which scenarios, ME22N will affect the release startegy in a relaesed PO or under release PO like any change in PO or some standard scenarios.
    Thanks with regards,
    Ankit Gupta

    Hi,
    Release startegy :
    In the standard system, Release strategy will trigger  changes in PO are done in  to the quantity,unit of measure, or price .
    This is controlled by Changeability indicator in release strategy.By this you can determine that release procedure will restarted if purchase order changed & value of item is increased by certain percentage or any change in the value.
    Thanks,
    AMIT

  • Release strategy for POs:

    Hello
    My customer is asking to have a released PO submitted againt to a release strategy if the item description (short text) is modified.
    any idea how can this be set up?
    thanks in advance
    Kind regards

    Hi,
    The MAIN problem is that PO release strategies are at the HEADER level and not the item level and so you cannot have item fields in the strategy (It does actually allow this but it takes the first line only and ignores the rest) so the short answer is that you can't do this.
    If this was a header field, to get the release strategy rechecked after a change, the field being changed MUST be one of the characteristics used in the release strategy.
    You would not have to actually use the field in the release strategy check, you can have it so that ALL valid entries are allowed (i.e the value of the characteristic is set to 0 to zzzzzzzz or similar) This would mean that it plays no active part in deciding the strategy but if it is changed, the system could be made to recheck the strategy.
    So, I am sorry but I don't think that you can achieve your requirement (without a modification or user exit)
    Steve B

  • Release Strategy changesin PR will effect the previous PR/PO also?

    Dear Experts,
    PR Release strategy should be changed(Release users increased). Can anyone clarify how the changes will affect. Will it apply to the previous PR/POs. If so what about closed POs. Pl advise.
    Thanks

    Hi,
    If you change any existing PO or PR the release strategy will be checked. If a new one exists (which will be the case) the system will find it and the release process will be restarted. Same happens for closed POs if you undelete them.
    I would suggest to create new release strategies instead of changeing the old ones.
    Best Regards,
    Arminda Jack

  • Can an existing Release Strategy be deactivated?

    Hi MM Gurus,
    We have configured Release strategy which is working fine. Now, a new requirement has come up.
    We donu2019t want to use the old Release strategy codes and want to create new one.
    Is there any way which we can deactivate the old release groups/strategy/codes? What is the standard practice? Can we also delete the same?
    Thanks in advance
    M

    Hi,
    Addition of new release code will not affect previously created POs .
    but for newly created POs it will add one more level.I think it is desirable results.
    regards,
    sujit

  • 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

Maybe you are looking for