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

Similar Messages

  • 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

  • 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

  • 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

  • Badi for release strategy me22n

    details Code for released status strategies on tcode me22n with function module .

    please check there is BADI ME_PROCESS_PO_CUST for PO Process and checks can be built in various method availble in BADI before PO release. For release strategy check user exit EXIT_SAPLEBND_002 .
    In case of any other details do revert back.
    anya

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

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

  • PO Release Strategy not triggerred for particular Total Net Order Value

    Dear,
    I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
    For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
    All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
    But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
    Please suggest for solution.
    Thank you.
    Warm Regards.

    Dear All,
    While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
    But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
    May I know how the value for this field gets calculated.
    Thank you.
    Warm Regards.

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

  • 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

  • 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

  • Purchase order release strategy Workflow not working

    Hi All,
    I am working on PO Approval release strategy and it is not working fine . The release strategy set up is configured by my functional consultant . I just copied the standard workflow template WS20000075 and making changes to my custom workflow template . When ever po is created an event "RELEASESTEPCREATED" get triggered and the first approver receives an workitem and when he approves it goes to Second Approver and it is working fine . But when rejected then a notification email goes to initiator . Now when an initiator login into ME22N and made any changes ( even material text change ) in it then again "RELEASESTEPCREATED" event getting triggered . But I need to trigger my workflow only when there is change in PO Net value .
    Kindly help me how to achieve this functionality .
    Thanks and regards
    Dilip

    Hi Vikram,
    There is already an existing entry for BUS2012 with event CHANGED against the change doc EINKBELEG .
    Acutlly when login as initiator and try to change PO through ME22N here are my observations :
    case 1:   When Buyer click on  " Cancel Reject " button and do any changes ( even text change ) then RELEASESTEPCREATED and CHANGED events  are triggering  . But since the event linkaged is set to RELEASESTEPCREATED workflow get restarted again.
    Even the CHANGE event does'nt have 'RELEASECODE' as parameter to restart workflow .
    Case 2:  When Buyer doesn't click on " Cancel Rejection" buttion and do any changes then only CHANGE event get triggered
    which do nothing since there is no event linkage .
    Is to  click on " Cancel Reject" button mandatory ? .  But even though we make " Cancel Reject"  as Button mandatory then RELEASESTEPCREATED Button triggering for any change but we need to trigger it for only net Value change .
    Thanks and regards,.
    Dilip Kumar

  • Purchase Order E-mailing with Release Strategy

    Hello,
        We are experiencing an issue when e-mailing a Purchase Order which has a release strategy. When the order is released, the confirmation e-mails are going to the person who releases it when it is supposed to go to the person who has created the P.O. We are using a Smartform P.O. based on /SMB11/BL_MM_PO_L and print program /SMB40/FM06P. I must note that there was a bug found in the aforementioned print program and before that was fixed e-mailing would not work at all.
      We have also attempted to use all combinations of standard unmodified print programs and standard unmodified smartforms and have had no luck at getting the confirmation e-mail to send to the correct person this way either.
      SAP has recommended that we use program SAPFM06P with form Medruck. While this combination does work correctly, Medruck is not a Smartform. Has anybody here used a smartform Purchase Order with a release strategy and had the confirmation e-mail send to the created and not the releasor?
      Below is a list of the print programs and forms we have tried in various combinations. We are running ECC6/Basis 7
    Print Programs:
    /SMB11/FM06P
    /SMB40/FM06P
    SAPFM06P (Sapscript Only)
    Forms:
    /SMB11/BL_MMPO_L
    /SMB11/MMPO_L
    /SMB40/MMPO_L

    Hi,
    Purchase order via e-mail in SAP sys,the configurations and pre-requisites are follow:
    1. You must maintain an e-mail address in the address in the vendor master.
    2. The same applies to your own user master. You also have to specify an e-mail address there in order to identify the sender.
    Note that it is not possible to change the e-mail address of the vendor via the SAP purchase order transaction (ME21N, ME22N, and so on). The system only uses the e-mail address of the vendor that is maintained in the vendor master!
    3. For the output type for default values, a communication strategy needs to be maintained in the Customizing that supports the e-mail. You can find the definition of the communication strategy in the Customizing via the following path: (SPRO -> IMG -> SAP Web Application Server -> Basic Services -> Message Control -> Define Communication Strategy). As a default, communication strategy CS01 is delivered. This already contains the necessary entry for the external communication. Bear in mind that without a suitable communication strategy it is not possible to communicate with a partner via Medium 5 (external sending).
    4. Use the standard SAP environment (program 'SAPFM06P', FORM routine 'ENTRY_NEU' and form 'MEDRUCK') as the processing routines.
    5. In the condition records for the output type (for example, Transaction MN04), use medium '5' (External send).
    6. You can use Transaction SCOT to trigger the output manually. The prerequisite for a correct sending is that the node is set correctly. This is not described here, but it must have already been carried out.
    7. To be able to display, for example, the e-mail in Outlook, enter PDF as the format in the node.
    For more details, check SAP note:191470
    Regards,
    Biju K

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

Maybe you are looking for