Change release strategy

Hi!
I have a problem with release strategy.
When i create purchasing order, i need to change release strategy.
How can i do that? I'm trying use exit M06E0004 (EXIT_SAPLEBND_002) but i don't know how fill this fields.
Anybody has any example?
I need to change the fields "Release group" and "Release strategy" in ME22N.

Hi,
Open the existing PO's in change mode and close . New Strategy will become effective
Regards
Reward Points if useful

Similar Messages

  • Changing release strategy - PR change history

    Hello,
    I have following situation.
    I changed release strategy for PR by adding one new release level.
    The change effected unreleased PR's and of course new strategy is valid for new PR's. This is ok.
    But, the problem is that I lost change history for PR's from the past. There is no change history log for items from old PR's. Also, tables cdhdr and cdpos lost change information, these tables are empty for old PR's after inserting changed release strategy.
    Do you know how can I add new level in release strategy without losing PR change history?
    br
    Dragan

    Hi,
    Are you sure the change log was deleted due to new release effected in PR?
    Does the change log was certain fields for PR.
    Do refer the below KBA, which explains the change that there is no change log updated for certain fields.
    KBA : 1895575 - ME5*N/ME2*N : No change log for certain fields

  • 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

  • Re-set release strategy of rejected PO,after doing respective changes to po

    Hi friends,
    I have created release strategy for Purchase order with release indicator 6 (Changeable, new rel. if new strat. or value change/outputted), and with 3 release codes (3 approvers)..
    Now in this case, After Rejection of a approver (creator of po will get an mail telling that its rejected). After rejection, the creator has did required changes and save the PO.
    However the release strategy is not reset...So i want to know how to reset the release strategy in this case..
    Where as in case after the approval, if creator do any changes in purchase order then release strategy is resets...  
    Here PO printout is possible only after the final approval...
    Pls give some inputs in fixing this issue..
    Thanks in advance....
    Regards
    Shashidhar...

    Hi
    What are the characteristics of your strategy?
    Try to change one of them save and then rechange it to the original
    eg.
    If the strategy depends for example on the Purchasing Group (PG)
    i mean according to different PG's different strategies working
    then with ME22N change the PG save and rechange it again to the original.
    or
    for example If the strategy depends on Materail Groups (MG)
    then do the change with MG
    With ME22N change the MG save and rechange it again to the original.
    I guess this will trigger the strategy again.
    Hope it helps
    Best Regards

  • 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

  • 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

  • PO Release Strategy not changed after deletion of few line items with less

    Subject : PO Release Strategy not changed after deletion of few line items with less Total PO
    Dear Friends
    We have issue with PO Release strategy. We have created the PO. with release strategy  with multiple approvers.  After approval of first approval manager , one of the PO line item got deleted and Total PO value is reduced . The new PO value should have changed the PO release strategy. But it is not changed. Old release strategy only showing in the PO which is wrong. 
    Details of the PO
    PO no 4500000123 with 5 line items Total PO value : 100,000 USD Release strategy : AB
    PO line item 5 deleted. Now total PO value changed to 50,000 USD and the PO release strategy should have been changed to AA but not changed. Still showing PO release strategy AB only.
    Are there any OSS notes available to correct his bug.
    Please let me know if you need more details
    Thanks in Advance
    Thanks
    MVS

    Hi,
    release indicators  change it to 4.It may works. Please explore to all 6 indicators..........
    i.e,
    1-cannot be changed
    2-changable,no new determination of strategy
    3-changable,new release in case of strategy
    4-changable,new release in case of strategy or value change
    5-changable,new release if new strategy/outputted
    6-changable,new release if new strategy or value changed/ outputted......
    And check   Characteristic description and value in Classification  of Release strategies ........
    I hope this will help you. Thanking you.
    Regards,
    Venkat.

  • 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

  • Reset Release Strategy for any change in the Purchase Order

    Hi,
    Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
    If so, where do we need to make the configurations.
    I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
    Thanks in Advance.
    S.Raghavan

    hi sandesh,
    sorry, i know it's too late.
    i tried your suggestion, it works blocking the purchase order after release strategies are setted.
    sandesh, raghavan:
    i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
    regards
    f

  • Want to change my existing Release strategy for - PR, PO & Service Entry

    Hallow Experts ,
    Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
    1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
    2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my  service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
    thanks in advance.
    regards
    vb

    Dear Vikrant,
    1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
    Sol:  Not  Required but , doing it is recomandaed
    2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
    thanks in advance.
    Sol: No Only thing you have to  do is that   go to your class 32 and   chek what is the charaterstic define for the purchasing group  copy it
    2 Now go to  Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
    3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group ,  that  group will now in fact of release Strategy

  • Release strategy retrigger for all non significant changes

    HI,
    My client has the below requirement:
    The Purchase requsitions and Purchase orders are released by different approval authorities. Any change made to any field like material short text, cost centre, payment terms, material long text, etc. the sytem has to cancel all the previous releases and release strategy need to be retriggred from the beginning.
    I request all to provide me with an user exit or badi if any available in the system to achieve this.
    Regards,
    Rayeesuddin

    Dear Ray,
    First discuss this with your functional consultant (MM) from functional point is there is any setting.
    Regards,
    D.Srinivas.

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

  • PO status if you change the release strategy procedure

    What will happen to the half released PO/PRS if we change the release strategy?

    Hi,
    It won't Happen for Half release PO Document. The rerelase will get affect once the final release done or No release initiated to the document.
    SAM

  • 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

  • Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO

    Hi All,
    I have the following requirement/scenario
    1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
    2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
    To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
    This is what I hoped for would work after doing the necessary config,
    For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
    For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
    The problem
    Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan.  I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
    Is their any other identifier I can use to address the requirement above? Let me know.
    Thanks
    Ashvin

    Thanks Charlie for your response.
    The conditions in the PO is not equal.
    On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
    On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
    So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
    Let me know your thoughts.
    Thanks for your feedback.

Maybe you are looking for

  • How do I transfer App data from iPod Touch to a new iPhone?

    When I restore from my iPod backup, the Apps that came with my iPhone are deleted. Where are the data files located so that a couple of games and other App data files can be moved over?

  • Time machine backup from 1TB iMac to 512GB MacBook Pro

    Hi all, I sold my iMac now a few months ago and been hanging out for the new one, but just about to be pursuaded to buy a 512GB MacBook Pro. My only problem is that we did a Time Machine back up on the old computer, and afraid I won't be able to acce

  • Highly customized JList- change selection logic

    I've written a highly customized JList that lays cells out horizontally, wrapping, and is editable. This is presenting a problem with one piece of default JList behaviour that I need to change or remove and install my own functionality. My JList can

  • Firefox locks up intermittenly when Google Search is executed

    Most of the time it works fine - but often Firefox will lock up whenever I try to execute a search via Google (interesting - but BING does not lock it up) -- I actually think it may be a JVM issue -- I have tried clearing cache ... but the only fix s

  • AS5350XM - Compatible IOS version for 'ip host ... srv' command.

    Hi Friends, I'm having AS5350XM model of Voice Gateways in CVP8.0 environment working with ICM8.0 and CUCM8.0. I'd like to define static hostname-to-address mappings in VG for my CVP CallServers along with command argument 'SRV' to use  all 4 CVP ser