Demand: Requirements page

View the detail of the requirement information.

Customer
The one who has created the schedule.
Ship To
The purchase order number associated to the requirements.
Customer Part Number
Part number as established by the customer.
Requirement Start Date
Depending on the Ship Delivery Code, the date in which the parts must be shipped or delivered to the customer.
Frequency
How often the parts are due. The requirement frequency is either Daily, Weekly, Flexible, JIT, or Monthly.
Quantity
Quantity Due
The open quantity (unfulfilled amount) of the requirement. The original Required Quantity minus the Quantity Shipped To Date.
Manual
Facility
Name of the destination issuing demand to which parts are to be sent.
Dock
Code representing the dock at the shipment destination (Ship To).
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.
Requirement End Date
Depending on the Ship Delivery Code, the end date by which the parts must to be shipped or delivered to the customer.
Cum Quantity
Shipped To Date
The quantity previously shipped against the requirement that partially or fully fulfilled the requirement.
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.
Rejected
The schedule has been rejected by the supplier.