EDI business document Schedule

Purchase schedules

LN supports the following types of purchase schedules:

• Push schedules

  A push schedule is a list of time-phased requirements, generated by a central planning system, such as LN Enterprise Planning or LN Project that are sent to the purchase business partner. Push schedules contain both a forecast for the longer term and actual orders for the short term. A push schedule is also called a non-referenced schedule. A non-referenced schedule is a schedule that contains lines without a reference number. Because no specific requirement exists for the schedule line, non-referenced schedule lines can first be clustered (grouped to send the lines in one purchase release) and then ordered, shipped, and received together.

• Pull forecast schedules

  A pull forecast schedule is a list of time-phased planned requirements, generated by LN Enterprise Planning, that are sent to the purchase business partner. Pull forecast schedules are only used for forecasting purposes. To actually order the items, a pull call-off schedule must be generated with the same schedule number as the pull forecast schedule. Like a push schedule, a pull forecast schedule is also a non-referenced schedule.

• Pull call-off schedules

  A pull call-off schedule is a list of time-phased specific requirements of purchased items, triggered from Assembly Control, Job Shop Control, or LN Warehousing ( Kanban, time-phased order point). A pull call-off schedule is a referenced schedule. A referenced schedule contains lines with reference numbers. When goods are shipped, received, and invoiced, the reference numbers are used to communicate with suppliers and other LN packages. Because a specific requirement exists for the schedule line, each single schedule line is ordered, shipped, and received separately.

Purchase releases

The purchase schedule can be sent using these purchase releases:

• Material release

  A schedule on which forecast information is provided about shipping times, delivery times, and quantities. In general, a material release can be considered as a planning release. For push schedules, however, the material release can also contain the actual order. In this case the release is called a material release with shipping capabilities. A material release can contain push schedules or pull forecast schedules.

• Shipping schedule

  A schedule on which detailed information is given about shipping times or delivery times and quantities. A shipping schedule facilitates just-in-time (JIT) management. A shipping schedule can contain push schedules or pull call-off schedules.

• Sequence shipping schedule

  A supplement to the material release or the shipping schedule with precise information about the production or deliveries of the requirements. This schedule can include the production or delivery sequence, and the order, the place, and the time of unloading after shipment. A sequence shipping schedule can only contain pull call-of schedules.

As a result, the business document Schedule includes these EDI messages:

• MRL

  Material Release

• SHP

  Shipping Schedule

• SEQ

  Sequence Shipping Schedule

EDI messages and purchase schedules

If the Release EDI Message Directly check box is selected in the Purchase Contract Line Logistic Data (tdpur3102m000) session or the Items - Purchase Business Partner (tdipu0110m000) session, LN automatically prepares the EDI messages when a purchase release receives the status Scheduled in the Purchase Releases (tdpur3120m000) session.

Use the Direct Network Communication (ecedi7205m000) session to generate the outgoing message. A report will list the messages that were generated. The outgoing messages for an external EDI business partner are stored in the appl_from directory for retrieval by translation software.

For information about release types, requirement types and corresponding EDI messages, refer to .Purchase schedule release types

Preparing EDI messages for push schedules in a purchase release

1. Create a purchase schedule header in the Purchase Schedules (tdpur3110m000) session and purchase schedule lines in the Purchase Schedule Lines (tdpur3111m000) session.
2. Create a purchase release line in the Generate Release Lines (tdpur3222m000) session.
3. Approve the purchase release line in the Approve Release Lines (tdpur3222m100) session.
4. Print the purchase release in the Print Purchase Releases (tdpur3422m000) session with the Final Report and the Prepare EDI messages check boxes selected.

Preparing EDI messages for pull forecast schedules

A pull forecast schedule can only be generated from the Generate Order Planning (cprrp1210m000) session in Enterprise Planning and cannot be created manually. Based on the parameters and triggers, these steps are completed automatically to prepare EDI messages for pull forecast schedules:

1. A purchase schedule header is generated in the Purchase Schedules (tdpur3110m000) session and purchase schedule lines are generated in the Purchase Schedule Lines (tdpur3111m000) session.
2. A purchase release is generated in the Generate Release Lines (tdpur3222m000) session.
3. The purchase release is approved in the Approve Release Lines (tdpur3222m100) session.
4. The purchase release is printed in the Print Purchase Releases (tdpur3422m000) session.

Preparing EDI messages for pull call-off schedules

A pull call-off schedule can only be generated from Assembly Control using the Transfer Assembly Part Supply Messages (tiasc8220m000) session, or from Warehousing using the Generate Orders (Kanban) (whinh2200m000) and the Generate Orders (TPOP) (whinh2201m000) sessions. A pull call-off schedule cannot be created manually. Based on the parameters and triggers, these steps are completed automatically to prepare EDI messages for pull call-off schedules:

1. A purchase schedule (header) is generated in the Purchase Schedules (tdpur3110m000) session. If the pull call-off schedule is preceded by a pull forecast schedule, LN searches for the corresponding pull forecast schedule in the Purchase Schedules (tdpur3110m000) session. Once found, LN creates a pull call-off schedule with the same schedule number as the pull forecast schedule. If no forecasting data is generated, the pull call-off schedule, as generated in the Purchase Schedules (tdpur3110m000) session, has no corresponding pull forecast schedule.
2. Schedule lines are generated in the Purchase Schedule Lines (tdpur3111m000) session. If the release type that is linked to the pull call-off schedule is Sequence Shipping Schedule, a schedule line for each call-off is generated in the Purchase Schedule Lines (tdpur3111m000) session, but the sequence details for the call off, such as VIN number and line station are stored in the Sequence Shipping data (tdpur3517m000) session.
3. A purchase release is generated with the status Scheduled in the Purchase Releases (tdpur3120m000) session. With every generation of a schedule line, LN generates a release line detail record in the Purchase Release Line - Details (tdpur3522m000) session. This record has a one-to-one relationship with the schedule line.

   If the schedule is a sequence shipping schedule, however, the following applies:

   • Only a purchase release header is created. No purchase release lines and purchase release line detail records are created. The reason for this is that items in a sequence shipping schedule are required for a combination of vehicle number (VIN), line station, and assembly kit. For this reason, a link exists between the release header in the Purchase Releases (tdpur3120m000) session and the release lines in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session.
   • Depending on the setting of the Generate Release per Vehicle check box in the Purchase Releases (tdpur3120m000) session, the release is either created per item or per vehicle.
4. The purchase release is printed in the Print Purchase Releases (tdpur3422m000) session.

Processing EDI messages

You can use the Direct Network Communication (ecedi7205m000) session to receive the customer’s new release or to update an existing release.

When you receive a new Material Release (MRL), Shipping Schedule (SHP), Sequence Shipping Schedule (SEQ), or Pick-up Sheet (PUS), a sales release and corresponding schedule(s) are created in Sales. Depending on the release type, an update to an existing sales release results in a new revision for the sales release and the corresponding schedule(s), or in updated sales release/sales schedule(s).

As a result, this information is automatically generated when EDI messages are processed:

• A sales release with revision number one in the Sales Releases Overview (tdsls3512m000) session. If a new EDI message is received for an existing sales release, a sales release revision is created with revision number two, etc.
• Sales release lines in the Sales Release Lines (tdsls3508m000) session.
• Sales release position details in the Sales Release Line Details (tdsls3515m000) session, for referenced schedules of the Shipping Schedule type. If you receive an update of a referenced shipping schedule, LN does not create a new sales schedule revision number. Instead, the sales schedule is updated. If an update arrives for a sales schedule line, also the sales schedule line is updated. To keep track of the updates, LN files the sales schedule line updates as revisions in the Sales Release Line Details (tdsls3515m000) session. As a result, a sales release position detail refers to a sales schedule line.
• Sales release lines for pick-up sheets in the Sales Release Lines - Pick-up Sheet (tdsls3109m000) session, if the schedule is of the Pick-up Sheet type.
• Sales release line details for pick-up sheets in the Sales Release Line Details - Pick-up Sheet (tdsls3116m100) session, if the schedule is of the Pick-up Sheet type.
• A sales schedule with a sales schedule revision number of one in the Sales Schedules (tdsls3111m000) session. If new requirements are received for an existing sales schedule, and sales schedule revisions are used, a revision is created with revision number two, etc. The previous sales schedule revision and its requirements are no longer valid if the new sales schedule revision is approved.
• Sales schedule lines in the Sales Schedule Lines (tdsls3107m000) session.
• Sequence shipping information in the Shipping Sequence (whinh4520m000) session, and shipping sequence detail revisions in the Sequence Shipping Information (tdsls3517m000) session, provided the schedule is referenced and of the Sequence Shipping Schedule type.

As with all incoming EDI messages, the Remarks in Copied Messages report is generated. The report displays the sales release number and corresponding lines added along with related remarks.