PO release strategy on Overall limit of the PO

HI All,
Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
For limit PO it triggered on Expected value but we want to trigger it on Overall Limit value.
( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
Please help on this.
we have used the enhancement used :  M06E0004 , Exit EXIT_SAPLEBND_002.
But I do not find the table or field showing the overall limit of the PO so that I can put the same in my purchase order release stucture.
Thanks in advance, will appreciate any help on this regard,
Anurag Goel

Hi
The expected value is the value that the item is not likely to exeed. in std SAP the expected value serves as a creterian for a possible release procedure for limit p.o
Thanks

Similar Messages

  • PO Release strategy on Overall Limit

    HI All,
    Presently release strategy in R/3 Purchase order is triggered on Total net order value ( i.e. CEKKO - GNETW ) > 250.
    For limit PO it triggered on Exepected value but we want to trigger it on Overall Limit value.
    ( If Overall limit = 1000 and Expected value = 100 release strategy should trigger on Overall limit)
    Please help on this.
    Thanks in advance
    Vikas

    Dear Vikas,
    you can use enhancement M06E0004 , Exit EXIT_SAPLEBND_002.
    This allows to change values in structure CEKKO based on specific conditions.
    First after activating you have to put this line:
    e_cekko = i_cekko.
    This means that no change will be made to cekko structure. Then if you want to change gnetw value, do something like this:
    e_cekko = i_cekko.
    If xxxxxxxxxxxxxxx.
    e_cekko-gnetw = xxxxxxxxx.
    endif.
    Maybe you can have multiple items so you will have probably to loop on IT_BEKPO table to get the total  Overall Limit for all items in your document and then transfer the total value.
    Good luck,
    SL

  • 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

  • Release Strategy for Credit Note un the QM Module

    Good SAP Guru's,
    I have a very important question for you:
    Is it possible within in the QM module (Transaction QM12) to implement a Release Strategy based on the value of the credit note to be created.
    This should work on the same lines as the Purchase Order Release strategy.
    Any guide lines and/or assistance will be gratefully appreciated.
    Kind regards,
    Leslie

    Dear Leslie
    We had done a similar kind of development in notification, not for credit memo though , but certainly can be incorporated in this case.We had done this for approving Short shipment and devaitions. If there has to be short shipment to be sent to a customer  a notification will be trigered to manager and if he approves it will go for higher approval.
    Please find my suggestion for this development
    1) Make 3 task codes. for eg Task 1 for  credit note is for less than u20AC500.00 . Task 2one for more than 501 and Task 3other one for more than 2001.
    2) According the need of the credit notes to be created let the user assign the task and release it.
    3) For task no 2 and task No3 a workflow triggers to the corresponding roles Sales manager & General Manager. ( please note that notifications are workflow freindly and standard workflows are available for the same)
    4) if Manager wants to approve he can make the Task Complete. ( Notification tasks have 4 stages, outstanding, release, complete, Succussful)
    5) Based on the status of the task you can make use of the action box in notification for creating the credit memo.
    6) The credit memo creation will have to be  developed. You will have to get ABAP support for this. They can either do it through user exit, or call transaction , and incorporate the same in the Action box of notification. (QQMA0001: User Subscreen for Notification Header, QQMA0014 Checks before saving notification )
    please let me know your apprehensions
    Regards
    gajesh

  • 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

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

  • PR Overall Release Strategy Problem

    Hi Expert,
    I have set the following
    Characterisrtic Name:
    1) ZPR_Release_Plant, Char : CEBAN-WERKS (Char format : 4)
    2) ZPR_Release_DOC_Type , char : CEBAN-BSART (Char format : 4)
    3) ZPR_Release_Pur_Grp, Char: CEBAN_EKGRP (Char format : 3)
    4) ZPR_Release_Total_Value, Char: CEBAN-GFWRT   (Curr format : 15 and  EUR)
    I assign the above to Class : ZPR_Overall_Rel
    I created Release Grp R1 and assign the class and tick "Overall Release" checkbox. There is only one class, no others in the list
    I created two Release codes, F1 - Senior Finance Manager, C2, CEO
    I created two purchasing group, LLL and LYL
    I used the standard indicators for S - block  2 - RFQ/PO and I created two release strategies A1 and A2 for Rel grp R1.
    A1 - release Code: F1, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LLL
    A2 - release Code: C2, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LYL
    The problem is when I tried to created the PR, it doesn't work at all. No trigger whether I click the "check" button at the toolbar of the PR (i.e., the release strategy tab not appearing at the header). I also tried saved and display the PR and see if the Release strategy appears at the header but still not triggering.
    Can you folks advise?
    Thanks
    Lo

    Forgot to check the box "Overall Release" forthe Nb doc Type. The problem is now solved.

  • MIRO invoice amount exceeding the blanket po overall limit

    Hello Gurus,
    I'm having trouble with invoicing against a blanket purchase order. Can anyone please explain why and when does invoice amount can exceed the blanket po amount.As I understood from the SAP documentation I should not be able to invoice for amout greater than the overall limit on the blanket PO.
    Here is what i did.
    1. I have created a blanket PR for 1000$  (Purchase requisition document type - Frame work requisition , overall limit - 1000$ , No limit flag - unchecked)
    2. I created a P.O ( Order type - Frame work order, validity start date - todays date , validity end date  - 1 year from today's date ).
    3. I checked the tolerance limits in OMR6 - for the above company code , tolearance key (LA) , check limit is blank , for tolerance key (LD) the check limit is 100.
    4. However I was able to invoice for more than 10,000$ against this Purchase order.
    My question is , am i missing anything so as the invoice amount not to exceed the blanket po amoutn ?
    My requirement is - MIRO invoice should not allow the user to post in invoice with amount exceeding the blanket p.o amout.
    Why would the MIRO invoice not checking the blanket po overall limit ?
    Appreciate your responses .
    Thanks.

    Hi Kirit,
    For tolerance key type 'LA' (Amount of blanket purchase order) , upper limit I set the check limit val to blank , and for percentage , i checked the do not check flag.
    For tolerance key type 'LD' , upper limit absolute check limit value is '100.00'.
    Where do i set the status of message , infact I'm not getting any message while posting the invoice.
    Appreciate your help.
    Thanks
    Rad

  • Item category control the release strategy?

    Hi,
    Currently the purchase of a material needs to be released.
    My issue is that as soon as I change the item category in the sales order,
    the material does not need to be released.
    How does item category control the release strategy?
    Sincerely,
    Ketan

    Hi Ketan,
    You can set item category in the characteristic of a release strategy.
    In your case, I guess the item category characteristic is already created. So you can just add the desire value into the characteristic.
    Go to SPRO > IMG > Material Management > Purchasing > Purchase Requisition > Release Procedure > Procedure With Classification > Set Up Procedure With Classification > Release Strategies
    Select the related release strategy, double click to view the detail. You will see there are 4 buttons in the bottom of the screen. Choose 'Classification' and enter you value of item category.
    Thanks & regards,
    JT

  • Release strategy: problems after changing the price

    HI Experts,
    I have the follwing problem.
    I´ve setup the release strategy for Purchase reqs.
    The strategy includes 3 approval levels.
    release indicator with changeability 4 and a value of 0,1% for the first two approval levels.
    I´m able to release it, but if I release the first two appoval levels and change the Preq the release strategy goes back to the first level. Fine.
    But the problem is now that I´m able to release the first level but if I try to release the second one I get a error message.
    I guess the problem is the changeability - but how can I solve this issue?
    The system have the cancel all approvals if someone changes the price.
    Any ideas?
    Thanks
    Alex

    HI RJ,
    the exact message is "Release prerequisite not fulfilled".
    The system should act in the following way:
    Approval levels:
    1. Supervisor
    2. Manager
    3. General Manager
    1 and 2 is approved.
    Then the requisitioner changes the price.
    Release will be changeled (Releases already effected will be cancelled).
    OK that work, now the release process starts with level 1.
    1. Approved --> OK
    2- try to approve and get the message "Release prerequisite not fulfilled".
    1 and 2 have the same release indicator with 4 and 0,1%.
    Thanks
    Alex

  • Regarding overall purchase requisition release strategy

    Hi,
          For following combination PR release strategy  is not working.
    1.Total value of requisition
    2.Purchasing Organization
    3.Name of Requisitioner/Requeste
    But when we take any one of them it is working. But when I tried to put together, these field system is not picking any release strategy.
    What would be the reason? is there any inter connection between these fields?
    Regards,

    Dear Aj,
    Chek is theare any other release strategy in the syestem wth mentioned chraterstic,
    also chek all chraterstic are ticked in the release strategy?
    Some time syestem is not able to find the unique release strategy,
    Please let me know

  • Release Strategy Triggered even if the characteric values were not correct.

    Hi,
    I have configured release strategy based on characteristics
    Purchasing group and
    Document type
    It has 2 release indicators with 3 levels of release.
    There are 2 release strategies assigned to same group 01 but have  different release codes namely 01,02,03,04
    Release Strategy A1has
    Doc type NB and Purchasing group 120
    Release Strategy A2 has
    Doc type ZINT and Purchasing groups 130,131,132,134,135,136,137,138,139
    However a strange thing happened.The release strategy was triggered for doc type NB and Purchasing group 190.
    This purchasing group is not listed in either of the 2 strategies 
    Can any one explain why the release strategy got triggered?

    That means the old release strategy is not cleraed from the system
    do one test
    Go to CL30N tocde and enter you release class and class type 032
    hit enter
    now here enter the value of your char which is in the PO and hit Find in initial class from header
    see which release strategy is pulled by the system
    here you will see the release strategy and make sure that is not other than what you expect

  • Expected Value and Overall limit value usage.

    Hi Sap Gurus,
    if the frame work order we have these 2 field Expected value and overall limit field value to be filled,
    and the system allows Invoice (or GR) up to the maximum of the overall limit value. and only if the value entered crosses the overall limit value the system issues a Error Message ( which is agreeable)
    but the logical requirement is that, if the value crosses the Expected value limit the system should display a warning message, indicating that the value has crossed the expected value.
    is there any config or note to be applied to get this funtionality.
    Thanks and regards
    Priya S

    Hi,
    Please refer to the Online documentation:                                      
             Material Management                                                   
             -> External Services Management                                       
                -> Procurement of Services: Processes                              
                   -> Accelerated and Simplified Processes                         
                      -> Use of Value Limits (for Unplanned Services)                                                                               
    Inside this documentation, it is stated that there is a variety of             
    limits (combinations) to be used:-                                                                               
    - Overall limit only                                                         
      - Overall limit and limit on services covered by contract item(s)            
      - Overall limit, limit on services covered by contract item(s),              
      - and other limit                                                            
      - Overall limit and other limit                                              
      - Overall limit on services from model specifications or standard            
        service catalog                                                            
      - Expected value                                                             
    The expected value is used in the update of the               
    PO item value and this is the value used in the release strategy.                   
    Here is the f1 help:                                                                               
    Expected value - ESUH-COMMITMENT                                                    
    Value that the unplanned services (or the materials) covered by this                
    item are not expected to exceed.                                                                               
    Use                                                                               
    If you are working with the release (approval) procedure for purchasing             
    documents, this value serves as the basis for a release strategy applied            
    to this document.                                                                               
    If you tick 'No limit',you don't need to enter 'Overall limit',but must             
    enter 'Expected value'.Because 'Expected value' will affect the release             
    strategy. Please read the note 440601 connected to this.     
    Concerning the variability of actual cost of a purchase order,                   
    expected value means that the unplanned services (or materials)                  
    covered by this item are not EXPECTED to exceed.                                 
    It is not mandatory that it has the same value like total limit value.           
    Expected value can exceed, it is used for comparison with total limit            
    value in cost control.                                                           
    Expected value can also be combined with unlimited total limit in a              
    purchasing document.                                                                               
    Regards,
    Edit

  • Sales Order released even though Credit limit exceeded VKM1

    Hi,
    I have got a scenario where a Sales order has been released(Delivery,Invoicing has taken place) even though the credit limit of the Customer has exceeded.
    Steps:
    The user check the order from VKM1 (push button check and save), but he didn´t release it, then checking the order changes we found that it was released by his user number.
    The order at the begining was blocked but after running just the check it was released automaticly.
    Checking from OVAK the document type has Automatic credit control.
    On OVA8 the static check is activaded and also the open orders and open deliveries
    What could be the reasons as to release of Sales order even after exceeding Credit limit????
    Thanks

    Hi Randall,
    From your description it is clear that the sales order was released by the user unknowingly, so when ever you release sales order all the sudsequent documents (deliveries&billing) would be relesased. There is no fault with the process, the user would be hidding some facts, so there is no way out. If you want to block the order again, you make some changes at the delivery level or sale order level and save it, the sale order will be blocked again. Next time see that the release strategy should be restricted for the limited users only. This can be done by BASIS consultant.
    regards
    prasad

  • Problem with purchase order release strategy

    Hi Guru's
        i am dealing with problem of  service purchase order release strategy , when i making the service  po ,  i am not giving any over fulfillment tolerance  ,  after release & making Service entry sheet of PO ,   when i go to the change mode and change
      over fulfillment tolerance say 90%  , system allow me to make , and not applying release  strategy again  ,  so  there can be a miss use of this Scenario ,  so is there any possibility that release strategy , will appear again when change the tolerance ,
    0r  any other idea from your side , to avoid this ,
      your suggestions are really always helpful to me ,  please guide me for this also
    Thanks & regards
    Neha

    Hi Neha,
    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 total net order value is linked to CEKKO-GNETW for a purchase order,
    CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
    for a purchase requisition overall release.
    If you have maintained a Tolerance for value changes during release
    (V_161S-TLFAE), the release strategy is reset when the value of the
    document is higher than the percentage you have specified and if the
    document is still subject to the previous release strategy.
    Review the SAP note 365604 and 493900 for more
    information about Release strategy.
    Regards,
    Ashwini.

Maybe you are looking for