When customers publish routine demand, it is sent as a release. The release contains header information and schedules for various parts. Each schedule contains requirements for a specific part. Through SupplyWEB, customers and suppliers share the same view of the requirements. Customers can add or modify requirements. Suppliers can ship against the requirements, fulfilling the demand.
Customers can send Material Releases, Shipping Schedules, or both. If sending both types of schedules, the Shipping Schedule is fulfilled by shipping while the Material Release remains unaffected as a planning document.
If using the Supplier Managed Inventory (SMI) module and a schedule is sent for an SMI- controlled part, the schedule also remains a planning document, which is unaffected by shipping.
If using the Kanban module, a corresponding eKanban schedule is automatically created for each signal. The schedule can be viewed and shipped against.
Depending on the customer configuration, suppliers may be able to reject Material Release or Shipping Schedule demand at either the requirement or schedule level. All demand initially has an accepted status. If using this option, customers define a period of time in which suppliers can change the requirement status before it becomes static.
Through SupplyWEB, customers and suppliers can also view the demand summary. The summary report shows demand for all parts going to a specific destination that is due to leave the Ship From within the next seven days.
As suppliers ship against a current release, requirements are decremented in FIFO (first-in-first-out) order by requirement date/time and optionally by pull signal. The customer configuration determines how staged (unpublished) and in-transit shippers decrement requirements when new demand schedules are published.