| # EDI business document Schedule The business document Schedule describes the processing of EDI messages that are used in a supply chain environment, which makes use of purchase schedules to communicate requirements to the selling company. Purchase schedules represent a timetable of planned requirements, and support long-term purchasing practices that have frequent deliveries. Purchase schedules are used in place of standard purchase orders when a more detailed way of specifying delivery dates/times for material requirements is needed. Purchase schedules are unique for an item and are sent to the purchase business partner in a purchase release. 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, Shop Floor Control, or LN Warehouse Management ( 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 by means of the following 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 the following EDI messages: MRL Material Release SHP Shipping Schedule SEQ Sequence Shipping Schedule EDI messages and push schedules A push schedule can use one of the following release types, which you can set in the Release Type field of the Purchase Contract Line Logistic Data (tdpur3102m000)/ Items - Purchase Business Partner (tdipu0110m000) sessions: Material Release Only material releases are sent. Shipping is performed based on the Firm or Immediate requirements in the Material Release (MRL). Shipping Schedule Both material releases and shipping schedules are sent. Shipping is carried out based on the Firm and Immediate requirements in the Shipping Schedule (SHP). The Material Release (MRL) only sends forecasting data. Shipping Schedule Only Only shipping schedules are sent. Shipping is carried out based on the Firm and Immediate requirements in the Shipping Schedule (SHP). No forecasting data is sent to the supplier. Push schedules with release type set to Material Release
Release Type | Linked Requirement Type | Linked EDI messages (BEMIS)
--- | --- | ---
Material Release | Planned | BEM MRL001
Material Release | Firm | BEM MRL001
Material Release | Immediate | BEM MRL001
The Material Release release type is only used by push schedules and only generates the EDI message BEM MRL001. As a result, shipping is performed based on the EDI message BEM MRL001, but only for those schedule lines whose requirement type is Firm or Immediate. Push schedules with release type set to Shipping Schedule
Release Type | Linked Requirement Type | Linked EDI messages (BEMIS)
--- | --- | ---
Material Release | Planned | BEM MRL001
Shipping Schedule | Firm | BEM SHP001
Shipping Schedule | Immediate | BEM SHP001
The Shipping Schedule release type generates both material releases (EDI message BEM MRL001) and shipping schedules (EDI message BEM SHP001). The schedule lines in a material release are released for planning purposes only. The shipping schedule only releases schedule lines whose requirement type is Firm or Immediate. Planned schedule lines are not included in the release. Shipping is performed based on the EDI message BEM SHP001. Push schedules with release type set to Shipping Schedule Only
Release Type | Linked Requirement Type | Linked EDI messages (BEMIS)
--- | --- | ---
Shipping Schedule | Firm | BEM SHP001
Shipping Schedule | Immediate | BEM SHP001
The Shipping Schedule Only release type only generates shipping schedules. No planning data is released to the supplier. The shipping schedule only releases schedule lines whose requirement type is Firm or Immediate. Schedule lines with the Planned requirement type are not included in the release. Shipping is carried out based on the EDI message BEM SHP001. To prepare EDI messages for push schedules in a purchase release Complete the following steps to prepare EDI messages for push schedules in a purchase release: Generate a purchase schedule header in the Purchase Schedules (tdpur3110m000) session and purchase schedule lines in the Purchase Schedule - Lines (tdpur3111m000) session. Generate a purchase release line in the Generate Release Lines (tdpur3222m000) session. Approve the purchase release line in the Approve Release Lines (tdpur3222m100) session. Print the purchase release in the Print Purchase Releases (tdpur3422m000) session with the Final Report and the Prepare EDI messages check boxes selected. Note If the Release EDI Message Directly check box is selected in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session, you need not print the purchase release in the Print Purchase Releases (tdpur3422m000) session to prepare EDI messages. LN automatically prepares the 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 trading partner are stored in the appl_from directory for retrieval by translation software. EDI messages and pull schedules A pull schedule can use one of the following release types, which you can set in the Release Type field of the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session: Shipping Schedule Both material releases and shipping schedules are sent. Material releases are issued through the pull forecast schedule. Shipping schedules are issued through the pull call-off schedule. Shipping is carried out based on the Firm requirements in the Shipping Schedule (SHP). The Material Release (MRL) only sends forecasting data. Sequence Shipping Schedule Both material releases and sequence shipping schedules are sent. Material releases are issued through the pull forecast schedule. Sequence shipping schedules are issued through the pull call-off schedule. Shipping is performed based on the Firm requirements in the Sequence Shipping Schedule (SEQ). The Material Release (MRL) only sends forecasting data. Shipping Schedule Only Only shipping schedules are sent. Shipping schedules are issued through the pull call-off schedule. Shipping is carried out based on the Firm requirements in the Shipping Schedule (SHP). No forecasting data is sent to the supplier through a pull forecast schedule. Pull schedules with release type set to Shipping Schedule
Release Type | Linked Requirement Type | Linked EDI messages (BEMIS)
--- | --- | ---
Material Release | Planned | BEM MRL001
Shipping Schedule | Firm | BEM SHP001
Shipping Schedule | Immediate | BEM SHP001
A pull forecast schedule only generates material releases (EDI message BEM MRL001) that contain Planned lines. EDI message BEM MRL001 is released for planning purposes only. The pull call-off schedule generates the shipping schedule, releasing all the schedule lines whose requirement type is Firm or Immediate. Shipping is performed based on the EDI message BEM SHP001. Pull schedules with release type set to Sequence Shipping Schedule
Release Type | Linked Requirement Type | Linked EDI messages (BEMIS)
--- | --- | ---
Material Release | Planned | BEM MRL001
Sequence Shipping Schedule | Firm | BEM SEQ001
Sequence Shipping Schedule | Immediate | BEM SEQ001
The Sequence Shipping Schedule release type is only used by pull schedules and generates the EDI messages BEM MRL001 and BEM SEQ001. A pull forecast schedule only generates material releases (EDI message BEM MRL001) that contain Planned lines. EDI message BEM MRL001 is released for planning purposes only. The pull call-off schedule only generates sequence shipping schedules and releases all the schedule lines whith the Firm or Immediate requirement type. Shipping is performed based on the EDI message BEM SEQ001. Pull schedules with release type set to Shipping Schedule Only
Release Type | Linked Requirement Type | Linked EDI messages (BEMIS)
--- | --- | ---
Shipping Schedule | Firm | BEM SHP001
Shipping Schedule | Immediate | BEM SHP001
The pull call-off schedule generates the shipping schedule, releasing all the schedule lines, which are always Firm or Immediate. No planning data is released to the supplier. Shipping is performed based on the EDI message BEM SHP001. To prepare 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, the following steps are carried out automatically to prepare EDI messages for pull forecast schedules in a purchase release: 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. A purchase release is generated in the Generate Release Lines (tdpur3222m000) session. The purchase release is approved in the Approve Release Lines (tdpur3222m100) session. The purchase release is printed in the Print Purchase Releases (tdpur3422m000) session. Note If the Release EDI Message Directly check box is selected in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/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 trading partner are stored in the appl_from directory for retrieval by translation software. To prepare EDI messages for pull call-off schedules A pull call-off schedule can only be generated from Assembly Control by means of the Transfer Assembly Part Supply Messages (tiasc8220m000) session, or from Warehouse Management by means of 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, the following steps are carried out automatically to prepare EDI messages for pull call-off schedules in a purchase release: A purchase schedule (header) is generated in the Purchase Schedules (tdpur3110m000) session. Because pull call-off schedules are usually 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. In this way, forecasting data and ordering data are separated. However, if the release type, defined in the Release Type field of the Purchase Contract Line Logistic Data (tdpur3102m000) session is set to Shipping Schedule Only, no forecasting data is generated, and the pull call-off schedule, as generated in the Purchase Schedules (tdpur3110m000) session, has no corresponding pull forecast schedule. 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 a particular call off, such as VIN number, line station, and so on are stored in the Sequence Shipping data (tdpur3517m000) session. 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 Production Synchronous Calls (tdpur3523m000) session. Dependent 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. The purchase release is printed in the Print Purchase Releases (tdpur3422m000) session. Note If the Release EDI Message Directly check box is selected in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/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 trading partner are stored in the appl_from directory for retrieval by translation software. To process 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), or Sequence Shipping Schedule (SEQ), a sales release and corresponding schedule(s) are created in the Sales Order Control module. 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, the following information is automatically entered in LN when EDI messages are processed: A sales release with revision number one in the Sales Releases (tdsls3512m000) session. If a new EDI message is received for an existing sales release, a sales release revision is created with revision number two, and so on. Sales release lines in the Sales Release Lines (tdsls3508m000) or the Sales Release Lines - Sequence Shipping Schedule (tdsls3116m000) session. Sales release line details in the Sales Release Line Details (tdsls3515m000) session. This session is not applicable for Sequence Shipping Schedules. A sales schedule with sales schedule revision number one in the Sales Schedules (tdsls3111m000) session. If new requirements are received for an existing sales schedule, a sales schedule revision is created with revision number two, and so on. The previous sales schedule revision and its requirements are no longer valid if the new sales schedule revision is approved. For referenced schedules of the Shipping Schedule type, no sales schedule revisions are used. 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. Related topics An overview of EDI business documents Push schedules Pull forecast schedules Pull call-off schedules Purchase releases Sales schedule procedure An overview of BEMIS |