Hi Maddy,
Please find some important stuff on Scehduling 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:
http://www.sap-basis-abap.com/sd/schedule-line-categories-and-schedule-agreements.htm
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,
Sateesh.Kandula
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.