Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA.  Based on which trigger should happened.  But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date   AEDAT
Item Delivery Date   EINDT
Schedule Line is "Fixed  "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document  FRGKE
Release status  FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on  document type level ,I am also confused on this .
  Please assist  on this

Similar Messages

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

  • Appluing release strategy for scheduling agreement

    Dear Sapguru,
    Can anybody explain.How to apply release strategy to scheduling agreement.I'm working on MRP implementation project.
    Here already release strategy using for PO.
    Pls explain steps of release strategy to scheduling agreement.

    Hi,
    Welcome you post on the forum.
    Have you searched the forum already? Such as:
    http://forums.sdn.sap.com/search.jspa?threadID=&q=%22applyreleasestrategy%22&objID=f245&dateRange=all&numResults=15&rankBy=10001
    Thanks,
    Gordon

  • ME38 resets Release strategy of Scheduling agreement

    Hello,
    It seems when the users change the delivery date  in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
    I cannot understand why this happens.
    Has anyone encountered such a problem before.
    Thanks
    Sunil

    Below are the (changed) item fields :
    Purchasing Document Item Change Date   AEDAT
    Item Delivery Date   EINDT
    Schedule Line is "Fixed  "FIXKZ
    Below are the (changed) header fields :
    Release Indicator: Purchasing Document  FRGKE
    Release status  FRGZU
    Purchasing document processing state PROCSTAT
    Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on  document type level ,I am also confused on this .
      Please assist  on this

  • Release strategy for Schedule lines in SD

    Hello All
    Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
    I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
    Thanks in advance.

    Hello,
    I think you are in the wrong forum. Please choose the right forum category and post it there.
    Matthias

  • Release strategy for sheduling agreement

    Hi,
    pl suggest me about release strategy of sheduling agreement.
    Is there any different release class required for SA other than PO?

    Hi,
    Release Procedure method is same for all the External Purchasing Documents (RFQ, PO, Contract and Scheduling Agreements)
    You have to use class with class type 032 and characteristics with Communication Structure CEKKO

  • Release strategy for Schedule Lines

    Hi,
    The requirement is MRP should not run for Line item unless it is released by an authorized user. Logically availability check has to happen at the time release of the requirement line for the consideration of realistic manufacturing time. Also, user should not be able to cancel the release, or edit the schedule line once Planned or Production Order is generated for the requirement line.
    What we want is a Release Strategy in sales order for each schedule line individually similar to PO Release.
    I have currently set up a status profile, which has 2 levels Processing and approved, which effectively block creation of DELIVERY doc, but I am unable to control the schedule line.
    Any ideas?
    Cheers.
    Edited by: Sowmya Mohan on Sep 12, 2008 1:14 PM
    Edited by: Sowmya Mohan on Sep 17, 2008 10:17 AM
    Edited by: Sowmya Mohan on Sep 17, 2008 1:03 PM

    Hello,
    I think you are in the wrong forum. Please choose the right forum category and post it there.
    Matthias

  • Release date and release no of Scheduling Agreement

    Hi All,
    I have a problem with Scheduling agreement.
    I have created a scheduling agreement with long validity period.
    I maintained delivery schedules within that validity period.
    I have generated forecast schedules. then using ME84, creating a releases.
    the problem is occurs here.
    it was not updating the release no and release date for the schedule line.
    still it is showing a *yellow light* .
    where is the problem and why it was not updating.
    and can u please explain the process and significance of those lights.
    Thanks in Advance.
    Regards
    Kishore

    Verify the table T161M has the values
    kvewe = 'B'
    kappl = 'EL'
    druvo = 1
    kschl = LHPA
    as mentioned in the code.
    The solution is add in SPAD the

  • Difference between Approval process signature strategy and Workflow

    Hi Everybody,
              I just wanted to know the difference between the approval process and Business workflow. How both of them useful in PLM prospective ??
    Thanks,
    Rajesh

    Hi,
    Approval or digital signature process in PLM involves creating authorization groups, signature strategies and assigning individual signatures to signature strategy groups.For example, to create digital signature for Engineering Manager, you create authorization group say ENGMGR and define it as individual signature and assign it to a signature strategy group.
    Business workflow is used to automate a business process.For example,it can be used in PLM-DMS for document review process.This can be triggered by status change(has to be defined in customizing) in document.
    Hope this helps.
    Cheers,
    Pavana
    Message was edited by:
            Pavana Mallavaram

  • Return process of stock transport scheduling agreement

    Hello there,
    We use stock transport scheduling agreement (TSA ) for inter company stock transfer. Would like to consult if it is possible to set up return for TSA. From MM configuration menu, there is only return setting under Purchasing order. I do not see anything under scheduling agreement.
    Thanks a lot in advance!
    Susan

    Hi,
       Even if the STO is done with scheduling agreement, you may create the return STO as normal STO return, without scheduling agreement. You may use the delivery type NCR and item category NCRN.
       You may refer the doc: Returns Stock Transfer Order – Overview and Implementation in SAP
       Revert back in case of further clarification.
    Regards,
    AKPT

  • 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

  • Printout of schedule agreement before Release

    hi all,
    i have created release strategy for schedule agreement at three level EX, MM & GM, problem is that i want to print schedule agreement number thru ME9l after releasing it from EX level. can anyone please tell me that is it possible to print schedule agreement before releasing from all three EX, MM & GM?
    if yes then how? or plzz tell me if any other option to print the same.
    regards saurabh.
    Edited by: saurabh srivastava on May 5, 2009 12:20 PM

    If your strategy is set up so that all three levels must release the agreement before it is final released I do not believe you can generate a printout.
    Regards

  • Change in scheduling agreement schedule lines .

    Dear All ,
            We have activated release strategy for scheduling agreement .Previously while maintaining schedule lines it was not going for release .
             But now while maintaining schedule lines in ME38 it is going for release .I want to know what is the reason and I want to stop this .
             We have made some changes in Closed PO amendment ,like we have changed the release indicator value R -6- 10% to R - 6 -0% .
    Like whenever we make change in price of a PO even a 1paise
    it should go for release .
              The release strategy for SA and PO is same .

    Hi,
    Since you have changed the release indicator it is again going for release for any change.
    Please change the release indicator to 2 from  6 so that you can change the schdeule lines or any modiifcation again release will not set
    Please check the release indicator in P.O and SA
    G.Ganesh Kuamr

  • Release strategy not trigerred if PR changed after Approval

    Dear Gurus,
    I have a requirement kindly help.   We have a PR generated from PS module, This PR is released by the approver. After the Approval, PS user change the PR qty and value has been increased. Now my client wants that this PR should be again sent for approval and release strategy should be trigerred. After the approval my release indicator is 2 RFQ/Purchase Order. I have set the Changeability indicator to 4 and define the tolerance to 0.1 %.
    But PR release not trigerred even after this. Kidnly help.
    Thanks.
    Johi

    Hi Johi,
    Check note 493900 point 3:
    3.  Question :
    Why is the release strategy not reset?
    Answer :
    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.
    I hope this helps.
    Regards,
    Ashwini.

  • Return process in Scheduling agreement and correction delivery creation

    Hi Experts,
    I have couple of Questions:
    1) I want to know the return process in case of scheduling agreement, how exactly we should go about it.
    2) Regarding creation correction deliveries in the scheduling agreements.
    I enter in a valid scheduling agreement number into transaction VA32, click the "JIT DlSch" button, click "Corr. Delivery" button and then enter in a date and quantity.
    After I hit "Save" button, I am taken back to the initial VA32 screen and see the following message...
    Sched. Agr. w/ Rel. ####### has been saved (no delivery created)
    Message no. V1261
    Does anybody have any insight to why this is happening? Thanks in advance.
    Sourabh

    Whether it is a scheduling agreement or sale order, in case of returns, you need to generate the following:-
    a)  Return Sale order or scheduling agreement referencing the parent billing document
    b)  Return delivery if goods are taken back in parent plant via VL01N
    c)  Credit note to customer via VF01
    d)  Excise credit via J1IH
    Last but not least, please spell the name correctly.
    thanks
    G. Lakshmipathi

Maybe you are looking for

  • Mid-2009 macbook pro 13" shuts down randomly when unplugged

    When my MBP is plugged in, it has never restarted on me. Most of the time when it is unplugged it doesn't either, but for the last month or so it will randomly power off (it pauses for a half-second, screen dims and it turns off .) I have Mavericks o

  • Safari quit unexpectedly while using the librooksbas.dylib plug-in

    First off this is on my husband iMac.  He Was running FoxFire with Safari and was having some problems so he moved Foxfire to the trash and ran a App to clean up anything left behind.  Well now he can't open Safari without getting "Safari quit unexpe

  • Replacing JAR files loaded by custom ClassLoader

    Hi all, I am trying to create an auto-updater for a stand alone application, which can look for new versions of relevant jar files on the internet and download them. I have code which will look for newly downloaded versions and can replace the old ja

  • Hyperlinks no longer working after browser upgrade

    IE works fine Firefox does not open websites after clicking hyperlinks

  • ITunes on locked disk?

    Just got new computer and created a new user account on it but now I cant use iTunes. Get error message saying it's on "locked" disk! I'm the Admin and the sole owner on computer. Help!