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.

Similar Messages

  • 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

  • Release Strategy  for Preq

    Hi SAPgurus...
    I have release strategy implemented in my system with 7 level approvals for the Pur. Req . Now i need to Change the release strategy to 4 levels approval based on one of the Characterstics that is the Preq Net Price. Which cud be the best process to ahcieve it , since if i am going to keep the old one and create a new one then wheneve similar characterstics appear the system cant recognize which strategy to apply.......
    Please can any one advice me how can i approach ...
    Regards
    Balaji

    Hi Lakshman, Srini & Venki
    From ur statements i understand to modify the existing ones , okie as u said i will delete the extra release codes and modify it . Now fine..
    What happens when i moved to prodcution these changes then, say if i have Preq
    with older version of release strategy how it impacts.....How i can handle  this in
    effective manner...To my knowledge i think whenever if i go for a change in preq the new release strategy will be affected....( In this case its fine) what abt the ones which doesnt need a change and has to be released....
    Thanks for the time ...
    Regards
    Balaji

  • Pr& po -new release strategy?

    Hi Friends,
    My requirement is to add new release strategy for pr & po.
    Characteristics & Class are remain unchanged.
    Pl advise to how to proceed, i mean
    i have to set/create new release procedure, ie.,
    New release groups
    New release codes (bcos new codes are added & release levels remained same)
    New release strategies
    How i can retain the Old PRs & POs released with earlier release strategy/release codes?
    PRs & POs not released can be with new release strategy,  but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
    Also, I need ur advise, how the new release strategy works for workflow
    pl help
    thanks & regards
    Srihari

    Hi,
    First of all, if you would only like to create the new release strategies, then the only possible settings you should do are -
    1)   Create the new release code;
    2)   Create the new release strategy;
    3)   Assign the release characteristics values to your new release strategy in CL20N transaction.
    For those old PRs and POs (regardless of if they were released or pending for release), the same old release strategy remains unchanged (and therefore, you should be much careful if you wish to delete the outstanding release codes and/or release strategies through configuration).  Having said that if you would like to keep the same release strategy though changes are to be made to your old purchasing documents, then you will have to assign the proper value to the "Changeability" field of your "released" release indicator.
    In case of release strategy in support by workflow, basically, the workflow item will be triggered (in accordance with the pre-defined logics that you built in terms of task ID).  As soon as the approver determination is made in background, the workflow item will be then sent to such agent who will then take a proper decision (approve, reject or forward).
    Cheers,
    HT

  • How to activate a new release Strategy Of PR without deleting the previous one?

    Dear  All,
    1=I have a release strategy in purchase requisition which is without classification and active in system.
    2= Now i configured a New Release Strategy for Purchase requisition   which is with classification
    My question is i want to activate the New one with classification  in System without deleting the previous one.
    Should it possible? and How?
    Ritesh.

    Dear  Dev,
    My old release strategy at item level.
    But  the New one  is at header Level.
    But the previous  one  showing  the release Indicator.
    But  when i delete  the old configuration the old release indicator vanishes.
    But the thing is  in Pr with out classification we have same Pr doc.Type
    But in New Configuration We want to at header level  and with same doc   type.
    so without  deleting  the old one if i activate the New Strategy whether the system allow me
    to see the New Release Indicator?
    As  My testing when i deleted the old one the Old indicator in Line item Level vanishes.

  • New Release Strategy in case of PO amendment

    Dear All,
    We have the release strategy at PO level on 3 parameters,
    Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
    When ever users edit the PO, again system sets the release strategy as per above logic.
    Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
    Can any one send me a user manual and steps for this.
    Thanks in advance,.
    Vikas

    Hi,
    You can set a control within Config. there is a parameter called as release indicator.
    Follow this IMG path:
    SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
    1     Cannot be changed
    2     Changeable, no new determination of strategy
    3     Changeable, new release in case of new strategy
    4     Changeable, new release in case of new strat. or val. change
    5     Changeable, new release if new strategy/outputted
    6     Changeable, new rel. if new strat. or value change/outputted
         Changeable, new release in case of new strategy
    Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
    Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
    So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
    Hope this explanation was clear.
    Prashant Rathore.

  • 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

  • Configure of New Release strategy in PR for ERSA Mat type

    Dear Friends,
    Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Regards,
    Ask

    ashokkumardash wrote:>
    > Dear Friends,
    >
    > Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Hi,
    Create Characteristic for Material type and Communication structure CEBAN and a create class with 023 and assign character to class and create Release group and code for MRP controller and finally assign this particulate role to the MRP controller User ID and he release the same.

  • 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

  • Extracting values for characteristic on release strategy of Preq

    hello
    we have Preq release strategy based on classification and the release is based on amount. in the class, one of the characteristics contains the amount above which the strategy is being triggered: how can I extract all the values for all the strategies from this characteristic? is there a table for it?

    Hi,
    Please check the AUSP table for release strtegies and CAWN table for characteristics. Please check below link for additional information. Thanking you.
    Release strategy tables

  • Challenge for release strategy in Preq

    hi all.
    our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
    their release is based on several factors:
    1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
    2) amount 2001>6250 it must be released by the following:
    WC1and/or Maintenance manager
    or
    WC2 and/or maintenace manager
    or
    WC3 and/or maintenance manager.
    the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases first the Preq is released and there is no further need to release by WCn.
    anything >6250 must be released by the maintenance manager.
    our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2: how can i set the strategy in such a way that it can perform the release and/or?
    can someone help?

    Hi Alisa,
                 Your Requirement is very Complex,
    first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
    Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
    for that you need to have different Release codes assigned to the user in the roles.
    for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
    Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
    Please revert back.
    Regards,
    Yawar Khan

  • Pr& po -new release strategy? released/locked/incomplete

    Dear MM experts,
    I would like to understand what it is meaning of
    released
    locked
    incomplete
    while doing assignment of object class thru cl24n for new release strategies,
    I am clear on released & locked, I would like to understand what is "incomplete" means as per SAP.
    kindly clarify
    thanks in advance
    srihari

    Incomplete means - When you go to CL02 or CT04
    you are entering the statu for calss or char as locked or released
    but when you are creating and that time if you have keep the status is in preparation  and without changing the status you start maintainig the data in CL24N than you will see the statu as incomplete.

  • Precautions to be taken before going for new PR Release strategy

    Dear all,
    We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
    Need your advice on
    1)If we go for new release strategy as off  with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
    2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
    3)Any other which I missed out, please suggest me
    Thanks
    RS

    Hi,
    It is better to release all existing PRs using your current procedure without classificaton and clean up.
    If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
    REgards
    Ram
    Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

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

  • New po release strategy

    hi,
    i am having xxxxx class for po release strategy with 3 characteristics-(plant, po value and document type)
    now i want to have only 2 characteristics with document type and PO value.
    again i want to use new release codes for my new strategy, keeping the same class for release strategy.
    can i define new release strategy using the new codes?, then what shall be the impact of the same on below
    1. already released PO, now want to amend,(after new release strategy implimented)- what would be the effect on PO?? which release codes shall hit the same?
    2. already release PO(i understand there wont be a problem in GR, as release ia already effected)
    3. new PO shall catch the new strategy- no problem with the same.
    for implimenting the new strategy using the same class, can i delete the old release strategy with codes or i just need to remove the value mentioned in the classification view of the release proceedure.

    thank u.
    my point is while re-defining the release proceedure.
    earlier i had 150 release strategies and arround 40-50 release codes. now only 12 release codes
    i just need to get confirm, if i create a new release code and assign a new release strategy using the same class(only deleting the plant characteristics), what will happen to old po(released) for which now we are amending.
    i assume i need to delete/remove all the data of old release strategy available in classification view, and keeping the release codes as it is in release pre-requisites fr old release strategy.
    or just any body briefe me what are all the condition for changing the exsiting release strategy.if i need to create new release code,release strategy by using the same release class.

Maybe you are looking for