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

Similar Messages

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

  • 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

  • MIGO for schedule lines against total released quantity

    Hi Gurus,
    Is there any standard solution (or user exit) available, so that  MIGO can be performed against total released quantity of schedule lines (Scheduling Agreement) in ME84?
    Currently, MIGO can only be performed once the "Proposed All Item" is ticked, and the quantity proposed is blanked.
    Thanks in advance.

    Hello,
    Yes I have created Scheduling agreement and maintain schedule lines with ME38 and also release schedule lines with ME84 transaction.
    I'm able to do GR, but I wonder if it possible to see all relevant (not yet received) schedule lines (as you can see in ME38 transaction with delicery date) in MIGO transaction? Now I can only see quantity summary of the schedule lines, which are not yet received.
    Regards,
    jaana

  • Purchase Requisition Release strategy for MRP based Requisition

    Hello Gurus
    We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
    Thanks
    Nick

    Hi,
    If you want include the MRP related PR in Release strategy.
    You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
    So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
    there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
    But it will  not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
    I think first one is best suited.
    rgds
    Chidanand

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • Step wise config data for schedule line agreements

    DEar All,
    I need urgently one the foolowing doc:
    step wise config data for schedule line agreements.
    thanks
    regards,
    s KUMAR

    Hi,
    1) Scheduling Agreement is a long term agreement and PO is normally a one-off. When you have long term relation with supplier you will go with SA.
    2) SA need not have delivery schedules at the time of ordering. It's like a contract with vendor for all basic prices, quantities & terms. You will release schedules as & when required. This method is very popular with manufacturing ind (e.g. automotive) where they negotiate prices but delivery schedules are given periodically based on their actual production/sales demands.
    3) In a PO, you must give schedules in PO itself.
    4) If you know contract & release order (or call-off) concept, then SA is like contract and SA schedule is like release order. PO is release order.
    or
    While using schedule agreement, you will create delivery schedule, when ever you require materials.
    Firm and trade off zone in delivery schedule details will be forwarded to your vendor. you can create daily , weekly , monthly schedule lines
    Example : if you have created a schedule agreement for product " A " for quantity 1000, and you require material of 100 nos in the first month, you can create schedule line for this 100 only and this will be transmitted to vendor( if you are using LPA you have to release schedule line). when ever you require further qty based on your requirement you will create another delivery schedule line, then it will be transmited to vendor.
    In case of PO if you are ordering 1000 qty , you need to specify the delivery date in Purchase order it self, and all the dates are immediately transmited to vendor along with Purchase order.
    For configuration steps please follow
    http://help.sap.com/saphelp_47x200/helpdata/en/93/7439fb546011d1a7020000e829fd11/frameset.htm
    Hope this will help.
    Thanks,
    Raja

  • Shipment for schedule line

    hi,
    For our Scenario., schedule line is generated from scheduling agreement with vendor.
    And, Shipment for schedule line is created successfully, using VSR Optimization.
    and in OLTP Generation of deliveries, I am getting List with my shipment for which the deliveries to be generated in ECC.
    but while executing, I am not getting any error (except application log in /SAPAPO/C3) as well as no delivery created in ECC which stopping me for "check Release of planned shipment. " and move the shipment to ECC
    Could anyone suggest me how to process the shipment for schedule line (based on scheduling agreement)
    Regards
    Maran
    Edited by: DP.Maran on Mar 7, 2010 11:33 AM

    Delivery generation was blocked in ECC, cahnged teh confirmation control key in shceduling agreement (0036)
    this allowed me to generate Delviery in ECC

  • PR release strategy for material group

    Hi,
    I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

    Hello
    In PR you can set up this release strategy without classification release strategy.
    w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
    Laxman

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

  • Release Strategy for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

  • Release Strategy for Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and press enter
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Ashok

Maybe you are looking for