JIT Delivery Schedules (Issued Against Scheduling Agreements) With Release Documentation



The term "release" used here refers to the process of advising vendors of precise quantities to be supplied on certain dates, at certain times, or within certain periods, against longer-term purchase agreements (which contain the agreed total quantities to be supplied over the overall validity period only). This concept may be referred to as "calling off" in the UK. It should not be confused with the release (approval, or clearance) process for purchasing documents. In connection with scheduling agreements, the term is short for "scheduling agreement release", a generic term for various specific types of delivery schedule (in the US automobile industry, also referred to as "automotive releases"). In connection with contracts, it may also stand for a release order (a type of purchase order).

As of Release 3.0D, the scheduling agreement functionality includes release documentation for forecast delivery schedules (FRC schedules: the first type of scheduling agreement release). The forecast delivery schedule provides your vendor with information on delivery quantities and dates. As a rule, it is used to give the vendor a medium-term overview of your requirements (e.g. over the next two months). (The equivalent EDI terms for this type of schedule are "planning schedule with release capability" (ANSI 830), "delivery schedule message (EDIFACT DELFOR), and "delivery instruction" ODETTE DELINS. The corresponding German term is "Lieferabruf" (LAB)).

The FRC schedule can be created manually or on a regular basis with the aid of a report. When working with the report (online or in the background) you can either generate releases (delivery schedules) for all selected scheduling agreements, or for those that have changed (i.e. for those in respect of which new schedule lines have been created or existing ones changed).


As of Release 3.0D, you can choose whether you wish to work with or without release documentation when processing scheduling agreements.

Scheduling agreements with release documentation have the advantage that you can always see when you transmitted which information to a vendor.

As of Release 4.0A, when you work with scheduling agreements with release documentation, the relevant functionality that you can already use for forecast (FRC) delivery schedules is also available to you for the JIT delivery schedule (JIT schedule) (the second type of 'scheduling agreement release').

Like forecast schedules, JIT schedules contain information on delivery quantities and required delivery dates. However, the information in the latter type of schedule is usually more precise: specifying exact dates or even hours of the day. That is to say, they serve to provide the vendor with detailed information for the near future. (The corresponding EDI terms for this type of schedule are: "shipping schedule" (ANSI 862), and "delivery just in time message" EDIFACT DELJIT). The corresponding German term is "Feinabruf" (FAB)).

Release creation profile

As of Release 4.0A, a release creation profile for scheduling agreements with release documentation is available within the Customizing facility. Use of it is optional. If you choose not to use it, you can continue to transmit scheduling agreement releases in accordance with the procedure currently used by your company.

You can use the release creation profile to generate and transmit scheduling agreement releases (forecast delivery schedules or JIT schedules) to the vendor. The default profile that appears in the scheduling agreement item is taken from the vendor master record.

As of Release 4.0A, you thus have an additional decision criterion for the generation and transmission of scheduling agreement releases: the creation periodicity of the releases. You can choose which periodicity you specify for a release type (e.g. FRC schedules once a week and JIT schedules on Tuesdays and Fridays).

In the release creation profile, you can specify the following:

Changes to the interface

There is a new sub-menu for maintaining scheduling agreement delivery schedules: "Edit -> Generate JIT schedule" and a new menu within the scheduling agreement menu: "Generate release".

The report for the generation of releases in the background can be found unter the menu path "Scheduling agreements -> Generate release". You can choose which type of release is to be generated for which scheduling agreements, whether a test run is to be carried out, and the scope of the log.

In the material master record, there is a new indicator ('JIT schedule indicator' unter 'Purchasing -> Other' and 'Materials planning -> Procurement') allowing you to determine the materials with regard to which you intend to work with JIT delivery schedules. If the indicator is not set, no JIT schedules can be created for the material.

The following new fields have been included in the additional item data:

There are the following new fields in the statistical data for an item:

Change system parameters in customizing

Please refer to the IMG documentation
Maintain release creation profile for scheduling agreement with release documentation and

Define document types.

You can still use the release documentation functionality even if you are working with self-defined document types for scheduling agreements by setting the "Release documentation" indicator in Customizing under document types. This applies only to newly created scheduling agreements.

As of Release 4.0A, the message type LPH1 is no longer mandatory for the system to update the print-dependent data in the release and scheduling agreement item. Instead, you can control the updating process using the "Update print-dependent data" indicator in the fine- tuned message control facility. You must flag one of your messages as relevant to the updating process for the operations '9' and 'A'.

Please refer to the IMG documentation
Define message types for scheduling agreement delivery schedules.

Further notes

In this connection, please also refer to the Release Info
Administration of scheduling agreements .