Skip to Content
avatar image
Former Member

scheduling agreements in sd

Hi gurus

i need detail steps regarding config of sheduling agreements...and also when to use the doc type lz and lzm ....pls guide me its very urgent



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Aug 20, 2007 at 09:23 AM


    A schedule agreement contains details of a delivery schedule but a contract just contains quantity and price information and no details of specific delivery dates

    Schedule line Agreement :

    Use the T.code VA31 (and choose Scheduleline agreement) : This agreement lets you to predetermine scheduling of different materials with in a given period of time (This is same like the other contracts).

    First enter the material with quantity say for example Material 1 Qty: 40, go to Edit from the menu >> Item >> Schedule line

    There select within the time period defined two dates, say for example on 12: 01: 2005 20 quantity and on 13: 01: 2005 another 20 (The qty has to be same as the one in the sales order) .

    Once this is done you have created a schedule line agreement.

    Call this agreement in your sales order (with reference) and use them.

    Note: You will be able to deliver only 20 qty on the 12th and 20 qty on the 13th, even though the sales order is for qty 40

    Configuring Scheduling Agreement

    Creating Scheduling Agreement

    Analysis and copying scheduling agreement

    Reward if USeful

    Thanx & regards.


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 20, 2007 at 09:25 AM


    Give your Email id



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 20, 2007 at 09:32 AM

    Hi Rajesh,

    Please find the complete Notes on Scheduling Agreements below:

    Schedule line agreements types are of two types LP and LU.

    LP-Scheduling agreement (with release and without release)

    LU-Transport order type scheduling agreement (For internal schedules)

    The planned Scheduling agreement r geneally created through MRP run,

    but if u want to include some customer for short period u can create manually which is what u called as general Scheduling agreement.

    Using tcode -ME31L.

    It contains specific order qty and delivery dates.

    U can create schedule line when u create scheduling agreement or u can create it later.

    To fulfill schedule agreement deliveries are created as and when the schedule lines got due for delivery.

    on SD side there are following types of scheduling agreements:

    LP (or DS) - scheduling agreements without delivery schedules, they work similar to the standard order with multiple schedule lines per item;

    LZ - scheduling agreement with delivery schedules, they get the delivery schedules (mostly via IDOCs, but possible also manually in the transaction VA32); the forecast schedule is intended for the long-term planning, JIT schedule is intended for the concrete delivery dates and times; planning delivery schedule can be created by you on the basis of the forecast schedule and in accordance with your Customizing settings. You can create a direct delivery from LZ agreement.

    LZM - scheduling agreement with delivery orders, is similar to Lz, but contains no JIT schedule and cannot be delivered directly. The document flow here is: scheduling agreement LZM => delivery order TAM => delivery. The LZM agreements are reasonable, if your customer pick ups the quantity himself.

    LK - scheduling agreements with external agent delivery. You get forecast and/or JIT delivery schedules, but deliver the goods into consignment storage location. The external agent will pick up the goods from there and send them to the customer. The document flow here is: scheduling agreement LK => Delivery => External agent delivery (with reference to LK directly) => Delivery

    LZS - scheduling agreements for self-billing, are similar to LZ, but you cannot bill them. The invoice must be sent from MM-customer via IDOC which will be processed via the function module IDOC_INPUT_SBINV

    LZJ and LZJS - JIT scheduling agreements, are available in the Automotive (IS-A) system only, they can be delivered only via some special JIT functions.

    Pl check the following link:

    Example: - Live Example for Scheduling Agreement

    1. For contracts you can take example of service scenario of a machine.

    Here you will fix a yearly maintenance value as well as spare parts replacement for key parts.

    2. Scheduling Agreement

    Lets take the example of a IS Auto in SAP

    Customer will place an order for say "Steering Wheel" or "Wheel" or a "Chasis".

    In this case the customer will send the requirements normally once in a week either in the form of "Forecast" or "JIT" schedule.

    Each time customer sends a DELINS IDOC to the vendor where a Sales Scheduling Agreement is maintained in SAP of type LZ or LZJ

    Each time the IDOC updates the schedules in the forecast and JIT depending upon the customer's requirements.

    Customer need not create a Sales order each time. He needs to send the schecules / requirements to the vendor and this will update the scheduling agreement.

    Accordingly JITK t-code is used to create JIT delivery followed by shipment and Invoice.

    This is where Scheduling agreements are used extensively when compared to other industries.

    Please Reward If Really Helpful,

    Thanks and Regards,


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 20, 2007 at 09:33 AM


    Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-ABART). Standard SAP you should have two sets of tabs - of schedule lines. One Forecast & the other JIT. Forecast forwards the schedule lines to planning (seen in MD04) and JIT passes them to shipping (VL10). They can be identical or different. Typically these are used for component supplier customers (namely Automotive). The customer will provide you 4-10 weekly buckets (usually a

    Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship dates - which are entered on the JIT. It comes down to the customer not knowing exactly what they need next week, but they don't want to surprise you with a large order qty, where your lead times are 5+ days. The foretasted qtys they sent last week should account for this.

    Schedule agreements are very nice when the customer sends EDI data (830s = forecast or 862s = JITs). Outside of that they can really cause trouble regarding daily maintenance, missing requirements, cum qty corrections, year end processing, etc.

    One alternative would be to use customer independent requirements - entering the weekly, monthly forecasting qtys and entering standard sales orders (with or without multiple schedule lines) to represent the true firm qtys.

    Add comment
    10|10000 characters needed characters exceeded