| Purchase releases |  |
| Purchase release header statuses In the Purchase Releases (tdpur3120m000) session, purchase release headers are displayed. Each header contains a release status that indicates which steps in the release procedure have already been carried out and what the next step must be. Naturally, the type of step to be taken also depends on the schedule type (push schedule, pull forecast schedule, or pull call-off schedule). A purchase release can have the following statuses: Preview The purchase release contains lines that all have the release status Preview, or lines of which some have the status Preview and some have the status Scheduled. Scheduled The purchase release is approved and contains lines that all have the release status Scheduled. Sent The purchase release is printed/EDI messages are sent and contains lines that all have the release status Sent. Purchase release line (detail) statuses In the Purchase Release - Lines (tdpur3121m000) session and the Purchase Release Line - Details (tdpur3522m000) session, these statuses represent the following: Preview The purchase release line in the Purchase Release - Lines (tdpur3121m000) session and the linked release line detail(s) in the Purchase Release Line - Details (tdpur3522m000) session, which can contain clustered schedule lines, are not approved. Scheduled The purchase release line and the linked release line detail(s) are approved. Sent The purchase release line with the status Scheduled and the linked release line detail(s), are printed in the Print Purchase Releases (tdpur3422m000) session with the Final Report check box selected, or EDI messages are prepared and sent by Electronic Commerce. Note For non-referenced schedules, you can approve the purchase release line, and consequently the linked release line detail(s), in the Approve Release Lines (tdpur3222m100) session. For referenced schedules, ERP LN automatically converts the schedule lines into a purchase release line and a release line-detail with the status Scheduled. The schedule lines are not clustered. For non-referenced schedules, you can cluster schedule lines in the Generate Release Lines (tdpur3222m000) session. EDI messages are automatically prepared if a purchase release receives the status Scheduled and you have selected the Release EDI Message Directly check box in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/ or the Items - Purchase Business Partner (tdipu0110m000) session. Relation between purchase release header and generating releases When running the Generate Release Lines (tdpur3222m000) session for non-referenced schedules, or when generating schedule lines for referenced schedules, ERP LN first checks whether a purchase release exists in the Purchase Releases (tdpur3120m000) session for the combination of buy-from business partner, ship-from business partner, release type, shipment based/ delivery based schedule, and communication method. Purchase release does not exist If no purchase release exists, ERP LN takes the following steps: A new purchase release is created in the Purchase Releases (tdpur3120m000) session with a release revision number of zero and a release status of Preview for non-referenced schedules, or Scheduled for referenced schedules. A purchase release line is created in the Purchase Release - Lines (tdpur3121m000) session with the release status Preview (non-referenced), or Scheduled (referenced). (A) purchase release line detail record(s) is/are inserted in the Purchase Release Line - Details (tdpur3522m000) session with the status Preview or Scheduled. If the schedule is a non-referenced schedule, the records in the Purchase Release Line - Details (tdpur3522m000) session can be clustered schedule lines. Note If the referenced schedule is a sequence shipping schedule, 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, usually, a release is sent by item. Items in a sequence shipping schedule, however, 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. For details, refer to Sequence shipping schedules. Purchase release does exist If a purchase release already exists, dependent on the purchase release's status, when running the Generate Release Lines (tdpur3222m000) session for non-referenced schedules, or when generating schedule lines for referenced schedules, ERP LN takes the following steps: If the purchase release's highest revision in the Purchase Releases (tdpur3120m000) session has the status Preview, the release lines in the Purchase Release - Lines (tdpur3121m000) session, which can have the status Scheduled and/or Preview, and the release line details in the Purchase Release Line - Details (tdpur3522m000) session, are simply updated. If the purchase release's highest revision has the status Sent, a new release revision is created with the status Preview or Scheduled. If the purchase release's highest revision has the status Scheduled, you must either send the purchase release or run the Approve Release Lines (tdpur3222m100) session with the Rebuild Release check box selected. If you choose the last option, the release lines are generated again for the specific purchase release. The purchase release keeps the same release revison number as the previous one and receives the status Scheduled. Note Rebuilding the release in the Approve Release Lines (tdpur3222m100) session is only applicable to non-referenced schedules. Even if the status of the purchase release's highest revision is not Sent, ERP LN can still generate new revision numbers when generating release lines. This occurs if schedules with various schedule issue dates are stored under one purchase release. Any schedule with a schedule issue date different from the issue date of the last release, receives a new revision number. Pull call-off schedules, for which no schedule issue dates are defined, are automatically stored under the last purchase release revision with the status Scheduled. Because call-off schedules are not released based on schedule issue date, it is better to select the Release EDI Message Directly check box in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/ or the Items - Purchase Business Partner (tdipu0110m000) session. If you select the Release EDI Message Directly check box, ERP LN automatically generates EDI messages for Scheduled purchase release lines, which Electronic Commerce sends to the supplier. Purchase releases - additional information The way in which ERP LN handles schedule lines in a purchase release also depends on the value of the Tax on Purchase Release Line level check box in the Purchase Contract Parameters (tdpur0100m300) session. If, after sending a release, the released requirements of the non-referenced schedule are deleted, you can run the Generate Release Lines (tdpur3222m000) session to create a release with no requirements. Because no lines are available for clustering, ERP LN creates a release line for the item with a quantity of zero in the Purchase Release Line - Details (tdpur3522m000) session. In this way, the supplier is informed about the cancellation of the previously communicated requirements. For referenced schedules, ERP LN automatically communicates the cancellation to the supplier. For more information, refer to Zero required quantity for sales schedule lines. For non-referenced schedules that must be sent in a purchase release, ERP LN retrieves a purchase schedule's warehouse from the Purchase Schedules (tdpur3110m000) session. For referenced schedules, however, ERP LN retrieves the purchase schedule's warehouse from the Purchase Schedule - Lines (tdpur3111m000) session, which can differ from line to line. As a result, the schedule lines of the same pull call-off schedule can be stored under different purchase releases. You can print the differences between two release revisions of a purchase release in the Print Purchase Release Variance Reports (tdpur3422m100) session. You can delete purchase release revisions in the Delete Purchase Revisions (tdpur3222m200) session. Related topics Push schedules Pull forecast schedules Pull call-off schedules Purchase schedule release types To use segment sets To cluster purchase schedule lines |