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

Similar Messages

  • 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

  • Po Release Strategy Change

    Hi Gurus
    I am changing the release strategy for po.
    Same characterstics and value also same.
    only change is release codes. so that, what i can do. if i add new release codes in same old strategies ?
    Otherwise i can create new release strategies ?
    if i create new what i have to take steps ?
    if i use same old release strategy and in that i can chage release codes what about previous documents ?
    client side cl24n here we can block old stratiges what about the documents created on old ?
    If any body answer right rewarded full.
    Thanks in advance
    Regards
    Laxman

    Hi
    we have also did some changes to relase codes after once in use & we had encountered some problems in the PO.
    For E.g. If you have the previous repease codes as L1 & L2 , & if you are removeing the L2 form the release codes then All the PO's whcih are approved by L1 & awaiting tobe approed by L2 will be in hanging status. You need to go into each PO 7 click on revoke acceptance & Click on check then The new relase codes will appear.
    If you can clearly explain what you are planning to do on the relase codes , then we can advise you in the right manner.
    Thanks & Regards
    Kishore

  • 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

  • PR Item Level Release WF not working after Release Strategy change

    Hi Experts,
               I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
    I really don't understand y after changing the release strategy workflow is not working and giving the following error.
    Even if i restart the workflow in SWPR the same error is occuring.
    Exception occurred    - Error when starting work item 000000390118
    PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
    CREATE                   -  Error when creating a component of type 'Step'
    CREATE_VIA_WFM  -  Agent determination for step '0000000003' failed
    EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
    AC00000148             -  Object type 'TS' not valid
    Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
    Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
    Regards,
    Hari

    Hello Hari,
    please set a breakpoint at function module
    ME_REL_GET_RESPONSIBLE
    and see what happends in section
        CASE t16fc-frgwf.
    * keine Ermittlung
          WHEN space.
            RAISE nobody_found.
    * Ermittlung über T16fW
          WHEN '1'.
    If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
    Best wishes,
    Florin

  • 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

  • Reg: P.O Release Strategy Changes

    Hi All,
    Release strategy is configured for a P.O.The changes in terms of releasing the P.O can be viewed in P.O Screen---Environment -
    Changes.
    Do we have any table for checking the changes made to a P.O in terms of Release strategy?
    Have a Nice Day.
    Regards,
    RaviKumar.S

    Hi,
    You can check this in CDHDR table.
    If version management is active for your PO then you can check the changes in EREV table.
    Regards,
    Bharat

  • How to check the PR release Strategy change date?

    hi,
    how to check when the PR Release Strategy chagned by someone ...?
    Regs,
    S J Solanki

    Hi
    You can directly go into the Purcahse order & check for the Heder changes which will give the Changed Date
    If you need to use two table to find out the date when the Strategy was changed.
    Use Table CDHDR & CDPOS. Object key is the POurcahse order number
    Thanks & regards
    Kishore

  • Retrigger Workflow if PO Release Strategy changes

    Hi All
    I have configured workflow for PO release.Now through work item if I am deleting a line item of the PO such that PO is capturing new release strategy due to change in PO value then workflow does not gets re-triggered again as per new release strategy.How can I achieve this?
    Edited by: satish kumar on Apr 18, 2009 9:13 AM

    Hi,
    For Creation it working fine right, i.e. Event triggering fine
    1) After Changing the PO, save it
    2) And tell functional consultant, whether they configure for the settings for PO change in SPRO
    Regards,
    Surjith

  • Release strategy , changing class

    Once you do release strategy using particular class, is it possible to adjust the  release strategies by changing the existing class?
    eg; class CL contains  one characteristic  total order value and done release strategy
         I want to change the class CL adding one characteristic say doc type, is there any effectby this

    Hi,
    I think it is possible.
    Add the characterstic in class and in classification of release strategy.
    regards
    suresh

  • 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.

  • 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

  • Release Strategy @ Company Code Level

    Hi Guys:
    We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
    Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
    with Characteristics as Company Code ,PO Document Type and PO Value?
    Thanks
    Sweth

    Hi
    For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
    The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
    The characteristics for release strategy for external purchasing documents are
    Plant                - WERKS
    Pur.group        - EKGRP
    Pur.org            -EKORG
    Acc.assignment category-KNTTP
    Document value-GNETW
    Document type-BSART
    The table is CEKKO
    Thanks

  • 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.

  • 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

Maybe you are looking for