| Purchase schedule release typesRelease types A release can be of the following types: Requirement types The following requirement types can be
communicated: Immediate These schedule requirements have a start date in the past at
the time of creation. These requirements must be shipped as soon as possible. Firm These schedule requirements are handled as actual orders that
can be shipped. Planned These schedule requirement are sent to you for planning
purposes only.
Release types and requirement types The schedule's business partner determines from which session LN retrieves the
logistic data to determine the type of purchase release and the requirements
that can be sent. Internal business partner Data is retrieved from the Items - Purchase Business Partner (tdipu0110m000) session. External business partner Data is retrieved from the Purchase Contract Line Logistic Data (tdpur3102m000) session.
Items - Purchase Business Partner (tdipu0110m000) Based on the Release Type in the Items - Purchase Business Partner (tdipu0110m000) session, a purchase release can be of
the following Release Type and can contain purchase release line
details with the following Requirement Type: Release Type in Items - Purchase Business Partner (tdipu0110m000) | Release Type | Requirement Type | Linked EDI messages (BEMIS) |
---|
Shipping Schedule Only | Shipping Schedule | Firm or Immediate | BEM
SHP001 | Sequence Shipping Schedule Only | Sequence Shipping Schedule | Firm or Immediate | BEM
SEQ001 | Shipping Schedule or Sequence Shipping Schedule | Material Release | Planned | BEM MRL001 | Shipping Schedule or Sequence Shipping Schedule | Shipping Schedule or Sequence Shipping Schedule | Firm or Immediate | BEM SHP001 or BEM
SEQ001 | Material Release | Material Release | Planned, Firm, or Immediate | BEM MRL001 |
Purchase Contract Line Logistic Data (tdpur3102m000) Based on the Schedule Message Types in the Purchase Contract Line Logistic Data (tdpur3102m000) session, a purchase release can be
of the following Release Type and can contain purchase release line
details with the following Requirement Type: Schedule Message Types | Release Type | Requirement Type | Linked EDI messages
(BEMIS) |
---|
Use Material Release | Use Material Release for Firm Requirements | Use Shipping Schedule | Use Sequence Shipping Schedule | yes | no | yes | yes | Shipping Schedule or Sequence Shipping Schedule | Firm or Immediate | BEM SHP001 or BEM
SEQ001 | yes | no | yes | yes | Material Release | Planned | BEM
MRL001 | yes | yes | not applicable | not
applicable | Material Release | Planned, Firm, or Immediate | BEM
MRL001 | no | no | yes | not
applicable | Shipping Schedule | Firm or Immediate | BEM
SHP001 | no | no | not
applicable | yes | Sequence Shipping Schedule | Firm or Immediate | BEM
SEQ001 |
Note - For push schedules, shipping can be performed based on the
EDI message BEM MRL001, but only for those schedule lines whose requirement
type is Firm or Immediate.
- EDI messages are only generated if the value of the Communication Channel field in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session is set to EDI.
- Segment set(s), which
consist of several segments, are linked to
requirement types. Which segment set(s) can be entered in the Items - Purchase Business Partner (tdipu0110m000) or Purchase Contract Line Logistic Data (tdpur3102m000) session, depends on the chosen
release/message type(s). Dependent on the release/message type(s) and the
applicable requirement type, specific EDI messages can be generated in time
when sending the purchase release to the supplier.
- Because pull call-off schedule lines are not clustered and are automatically converted to
purchase release line details with the status Scheduled, no segment set(s) are used. As
a result, the requirement type is always Firm.
- For push schedules lines, requirement types in the Purchase Schedule Lines (tdpur3111m000) session are calculated during the regeneration process, which
you can perform in the Regenerate Schedules (tdpur3211m000) session. The requirement types in the Purchase Release Line - Details (tdpur3522m000) session are directly calculated from
the schedule's applicable segment set and issue pattern. If you do not
regenerate the schedule line, the value of the Requirement Type field in the Purchase Schedule Lines (tdpur3111m000) session has the same value as the Requirement Type field in the Purchase Release Line - Details (tdpur3522m000) session. Which schedule lines are
included when you generate release lines in the Generate Release Lines (tdpur3222m000) session, depends on the push schedule's
release/message type(s). For example, if the release type is defined as Shipping Schedule Only, no material release is created, so the purchase release does not
contain Planned release lines.
| |