| EDI business document ScheduleThe 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 rather than standard purchase orders
when a more detailed way of specifying delivery dates and times for material
requirements is required. Purchase schedules are unique for an item and are
sent to the purchase business partner in a purchase release. Purchase schedules The following types of purchase schedules exist: Push schedule A list of time-phased requirements, generated by a central
planning system, such as Enterprise Planning or Project that is 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 a nonreferenced schedule. Pull forecast schedule A list of time-phased planned requirements, generated by Enterprise Planning, that is
sent to the purchase business partner. Pull forecast schedules are only used
for forecasting purposes. To order the items, a pull call-off schedule must be
generated with the same schedule number as the pull forecast schedule. Similar
to a push schedule, a pull forecast schedule is also a nonreferenced schedule. Pull call-off schedule A list of time-phased specific requirements of purchased items,
triggered from Assembly Control, or Warehousing (KANBAN, Time-phased order point). A pull call-off schedule
is a referenced schedule.
Purchase releases The purchase schedule can be sent through 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, the material
release can also include the actual order. In this case, the release is called
a material release with shipping capabilities. A material release can include
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 include 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,
the order, the place, and the time of unloading after shipment. A sequence
shipping schedule can only include pull call-of schedules.
Consequently, the business document schedule includes these
messages: Preparing EDI messages for push schedules To prepare EDI messages for push schedules in a purchase
release: - Create a purchase schedule header in the Purchase Schedules (tdpur3110m000) session and purchase schedule lines in the Purchase Schedule - Lines (tdpur3111m000) session.
- Create a purchase release line in the 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 or the Item - 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 pull forecast
schedules A pull forecast schedule can be generated only 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 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.
Preparing EDI messages for pull call-off
schedules A pull call-off schedule can be generated from Assembly Control through
the Transfer Assembly Part Supply Messages (tiasc8220m000) session, or from Warehousing through
the Generate Orders (KANBAN) (whinh2200m000) or 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. 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, a pull call-off schedule is
created with the same schedule number as the pull forecast schedule. In this
way, forecasting data and ordering data are separated. 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.
- 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, and line station 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, a
release line detail record is generated 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, because
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.
- Depending on the settings of the Generate Release per Vehicle and Generate Release per Item check boxes in the Purchase Releases (tdpur3120m000) session, the release is either created by vehicle or
by item or business partner.
- 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), or Sequence Shipping Schedule (SEQ), 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). When EDI messages are processed, this data is
generated: - 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) session.
- Sales release position details in the Sales Release Position Details (tdsls3515m000) session, for referenced schedules of
the Shipping Schedule type. The Schedule Revisions for Referenced Shipping Schedules check box in the Schedule Terms and Conditions (tctrm1131m000) session
determines whether sales schedule revision numbers are used for referenced
shipping schedules. If this check box is cleared and if you receive an update
of a referenced shipping schedule, no new sales schedule revision number is
created. 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 Position Details (tdsls3515m000) session. Consequently a sales release
position detail refers to a sales schedule line.
- 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, 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 after 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. | |