PO release strategy for changes in price ($ and %)

Hello,
I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %.  I will need to calculate the difference in the total value between the original PO and the changed PO. 
Example:
Original PO total net value is $1000
PO after a price change - total net value is $1500
Total net value has increased by $500 or 50%.
Tolerance for price change is $200 or $20, so tolerance has been exceeded.
I know I will be using the total net order value (CEKKO-GNETW).  I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table.  I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not.  I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
What I don't know is where will I find the previous total net order value once the PO has been changed?  Is the only place that information is stored in the change logs?  If so, what is the change log table name?  Or is there a different table that would contain this information?
Thanks in advance for any help you can provide.
Sincerely,
Angela

Update:
I utilized function module EXIT_SAPLEBND_002 as a solution to this.  I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

Similar Messages

  • 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

  • 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 for PR with materials having different prices

    Hai Gurus
    Can we make a release strategy for a variant configured material ?
    I mean create a strategy in such a way that price is critical factor and the materials what ever we choose for the PR has different characteristics dependencies like for example ( A chair having different characteristics like color, material ( like steel, leather etc) and other features like wheels etc and whatever characteristics we choose has a different price.......... so when v come to the release strategy it has to be approved by the next level if it reaches $ 1000 and so on.
    please help me out in this issue

    Hello Arif Mansuri
    thanks for your reply, yes I have taken it as total value only. The scenario is I am asked to use three different characteristics ( total value, materials, MRP Controller) and assign them to a class and if the customer picks any number of different materials and if the price is more than 1000 then it has to reach to the next level for approval. i thought i am suppose to use object dependencies here......... can we do this in a normal release order if so how would be the strategy played here?
    thanks for your time

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • 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 PO and RO

    Hi All
    My release strategy for Purchase order and Release Order is same.My release strategy has material group and PO/RO value as characteristics. What I want is that my releaase strategy for PO should be based on value whereas for RO it should be based on material group. Is this possible since we cannot have different release group for PO and RO.
    Pl suggest how to go about?

    HI Satish,
    In the characteristic value screen we not only can give single values ,but also multiple values
    and also range of values.
    Since the Data type for this Feild is character ,that is the reason it is not taking Ranges
    So the same is not working for PO,I too Checked the same.
    So it is that you have to have material group ,then there is no other go but entering all the values for the same.
    As we cant add a new Release Class also
    Becoz the release class cant be different ,so as the characteristic values would be same.
    if i could find something else will post you soon.
    but as of know we cant do nothing in this case but create all the material group as charecterics values and add to that strategy.
    Thanks
    Anjanna.

  • Release strategy for PR and PO

    I have release strategy for PR and PO, suppose there is 3 levels of Release, at second level I want to set an alternative Release code,  if either of the employee releases then it should go to third release.
    How to configure for PO (with classifications) and PR (without classifications). 
    I am not using workflow than how to do it ???

    follow the steps below.
    Release prerequisites should not be checked
    Release statuses do the following settings for alternate release
    based on your requirement
    you can make the release or blocked status manually in release config
    than it will work.
    without classification it will not work

  • Release Strategy for reservation created from PM and PS

    Dear All,
    How to configure the release strategy for reservation generated  from PM and PS.
    Regards,
    Atanu

    do you talk about release strategie for requisitions, or really reservations?

  • Release strategy for Future validity period- (Outline agreements)

    Dear All,
    I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
    E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
    I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
    How to set up release strategy in the above case.
    Thanks in Advance.
    Regards
    Amar

    Hi Amar,
    1) if you maintain a target value (EKKO-KTWRT) in the header of the            
    contract this value is the basis for the determination of the release          
    strategy. If the target value is 0, the system will cumulate the               
    values of the items and will use this value for the determination.                                                                               
    2) So if the target value is 0 and you change the price of a condition         
    with a validity period in the future the system will react in the              
    following way:                                                                               
    Example:                                                                       
       the contract contains one item with quantity = 100 and a net price          
    of EUR 5,-.                                                                    
       all contracts with a target value from EUR 0 - 1.000,- should be            
    subject of a release strategy                                                  
       the contract is created and released on October the 1st                     
       ME32K -> October the 2nd you define a new price of EUR 7,- with a           
    validity period from 03.10.09 - 30-10.09 -> you save the contract              
    -> the release strategy is not reset, as the start date is not                 
    reached yet (system date < startdate of validity period)                       
       ME32K October the 3rd you change a field in the contract -> the             
    release strategy is reset                                                                               
    This is system design that a release strategy can only be reset through        
    an action by the user. The determination of the release strategy can't         
    be triggered automatically in the background.      
    If you create a document which is subject of an overall release strategy      
    (e.g. p.o., contract) the determination of the release strategy takes         
    place when the user hits the 'save' button or chooses the 'check'             
    function.                                                                     
    So there must be a kind of event that tells the system that something         
    has changed.                                                                               
    Regards,
    Edit

  • Release Strategy for Condition Records

    Hi,
    This is a requirement from my client. The client needs to give 4 levels of release strategy for the condition records created. The selling price for the products will be entered by person 1. This has to be approved by the sales execute (person 2); then by the sales manager (person 3); finally by the General Manager (Person 4). The selling price of the products ranges from 10 lakhs to 40 lakhs. so, the release strategy is needed. This type of release strategy is available in MM for PR and PO. Please let me know whether similar facility is available in SD. Any alternative is also solicited.
    Regards,
    K Bharathi

    Hi,
    Thanks for your valuable reply.
    I defined 3 Processing status (Menu path: SPRO >> SD >> Basic Fn >> Pricing >> Define Processing status). They are EU-End user, KU-Key user, MD-Final authority. These processing statuses are assigned to Release status. First two processing status EU, KU were assigned to A (Blocked). The third processing status MD was assigned to Blank (Released). The purpose is: at processing status EU one person will upload the price master. Second person will check the price and will change the processing status to KU if he satisfies with the accuracy of the price master. The third person (final authority) will check the price and set the Processing status MD. Once the condition record gets the status MD, the prices can be used for creating sales order because it is released.
    In the condition record for PR00, when I enterthe processing status  EU or KU the release status shows 'Blocked' release statuses. When I enter MD in the processing status, the release status show 'released'.
    My question is how can assign the responsibilities of changing the processing statuses EU to KU, KU to MD to two different persons.
    Regards,
    K Bharathi

  • Release strategy for Release POs

    Hi Every one,
    We have a requirement.
    A contract is created and approved as per the regular strategy.
    The releases (POs) are created against it and sent directly to the vendor.
    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
    But the business wants the PO releases too to follow the release strategy.
    Can you please look in to this and let me what changes we need to make this happen.
    Regards
    Pavan

    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
    This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
    As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
    So that the Release Process is applicable to PO's created w.r.to Contract also..
    For ex: if you use the field purchase Doc category as a Character  in  the Release , it differentiates whether it is PO or Contract..
    So that you can define different Release Strategy for PO & Contract
    Or  if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
    then the release strategy applies to PO also..

  • Purchase Order Release Strategies for Changed Amount

    Hi Gurus,
    We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
    Example: Configuration is PO total amount <$5K requires only L1 approval.  PO total amount >$5K requires L1 and L2 approval.  PO was created for $8K and was release using L1 and L2 approvals.  Receipts were posted to PO in the amount of $7K.  Now the buyer has added an additional line item for $1K.  The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item).  Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
    Has anyone done this before?  Any ideas??
    Thanks,
    Gabe

    from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
    User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
    This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
    The following user fields are available:
    USRC1
    USRC2
    USRN1
    USRN2
    In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

  • Release strategy for PO on Payment terms..

    Dear friends,
    Is it possible to have Release strategy for PO on Payment terms.....
    I checked in CEKKO, no field availble for payment terms.
    Is there any other way..........
    Plz help
    Rgds,
    Navin

    Hi,
    You can append Communication Structure "CEKKO" and add Payment Term (ZTERM)
    Use User Exit "M06E0004" (Changes to communication structure for release purch. doc.)
    Function module "EXIT_SAPLEBND_002" (Changes to Communication Structure for Release of Purchasing)

  • External mail for workflow of release strategy for PO

    Dear All,
    I have configured the workflow of two step release strategy for purchase order and the internal mail is getting generated in the sap business workplace with the error message SWF_RUN 594 this i have taken care with SWE2 with changing the settings of "Behaviour upon error feedback" from "default" to "do not change linkage"
    Now the requiremnt is that the message has to be send to first level releaser through external mail and once first level release the PO external mail should be send to second level releaser.
    Please help me with the configuration step that is to be done
    Thanks in advance
    Naveen Singh

    Schedule the report Rswuwfml2. this will send workitem from sap inbox to respective user external mail id maintain in user master.

Maybe you are looking for