Schedule page

Use the Schedule page to view the schedule details.

Dock
Code representing the dock at the shipment destination (Ship To).
PO Number
The purchase order number associated to the requirements.
Engineering Level
Customer defined code indicating the required version of the part that is associated to the requirements.
Customer Part
Part number as established by the customer.
Customer Part Description
Customer-defined information about the part.
Supplier Part
Part number as established by the supplier.
PO Line Number
Specific purchase order line number associated with this requirement.
Ship/Delivery Code
Whether the requirement date is when the part is due to be shipped (SH) or when it is due to be delivered (DL).
Model Year
Code associated with the part that indicates to which run it belongs.
Generation Date
The date the release or purchase order was created by the customer.
Publish Date
Date the release was sent (imported).
Last Update
The date the schedule was last modified.
Release
Number associated with the release that contained the schedule. To view the schedule for a different release, select the release from the menu and click the View button.
Part Release Status Code
The status of the part at the time of the release. For example, a B (balance out) can indicate that the part is being phased out or a F (final code) can indicate that this is the final release for the part.
Raw Material Start
Date tracking of the Raw Material Amount starts.
Raw Material Amount
The amount of material the supplier is authorized to purchase.
Fabrication Start
Date tracking of the Fabrication Amount starts.
Fabrication Amount
The quantity of parts above the firm and planning requirements that the supplier is authorized to have on hand.
Last Shipper Number
Shipper number of the last shipment received by the customer that contained the part.
Last Ship Date
The date the last shipment for the part was received.
Last Ship Quantity
Quantity of the part received in the last shipment.
CUM Required Prior
The total number of parts requested before the release was published.
CUM Shipped (YTD)
The total number of parts that are either shipped or staged. The value is calculated based on the inbound schedules and value specified by the admin user in the Additional CUM Fulfillment field of the Characteristic Set.
Viewed
Indicates whether the requirement has been viewed by the supplier. The supplier must open the requirement with the view icon for the requirement to be viewed.
Date
Due date for the parts. Based on the Ship Delivery Code field of the Release Information, this is the date the parts are due to be shipped (SH) or the date the parts are due to arrive at the Ship To (DL).
Required Quantity
Number of parts required.
Shipped Quantity to Date
The quantity previously shipped against the requirement that partially or fully fulfilled the requirement.
Due Quantity
The open quantity (unfulfilled amount) of the requirement. The original Required Quantity minus the Quantity Shipped To Date.
Type
The kind of requirement:
  • Firm. A requirement authorized to be shipped.
  • Planning. A planning requirement.
  • Production. Live production requirement, usually means the part is to be produced and shipped.
  • Test. Purpose of "Test" is defined by customer, usually signals a trial run of data for testing purposes, and requires no shipment of parts.
Frequency
How often the parts are due. The requirement frequency is either Daily, Weekly, Flexible, JIT, or Monthly.
Pull Signal
Code defined by the customer and associated with the requirement. For example, RAN (receipt authorization number), DON (delivery order number), or KANBAN. Generally when a pull signal is used by the customer, the exact requirement must be shipped, and the pull signal must be printed on the shipper and published on the ship notice.
Related topics