This page is a bit old!
Click here to look at the most recent version of this page.
This table contains the purchase orders of your supply chain (replenishment you are purchasing from your suppliers), either proposed by frePPLe or confirmed.
This table is populated with new proposed purchase orders when frePPLe generates a plan. It is also possible to load purchase orders that are already approved or confirmed in your ERP system.
Unique identifier for the purchase order.
For approved or confirmed purchase orders that are imported from your ERP system this field should be populated with the identifier the ERP generated.
For purchase orders newly proposed by frePPLe, a unique numeric identifier will automatically be generated.
|item||item||The item being purchased.|
|location||location||The location receiving the purchase order.|
|supplier||supplier||The supplier shipping the purchase order.|
|quantity||number||The quantity delivered.|
|ordering date||datetime||The date when the purchase order is leaving the supplier location.|
|receipt date||datetime||The date of the purchase order delivery.|
|start date||datetime||Deprecated alias for the ordering date.|
|end date||datetime||Deprecated alias for the receipt date.|
Blank/unused for make-to-stock items.
Identification of the batch for make-to-order items.
This field should have one of the following keywords:
|demands||demand||The demand(s) (and quantity) pegged to the purchase order. This is a generated field.|
The Inventory Status is a calculated field that highlights the urgency of the purchase order with a red/yellow/green visual indicator.
Sorting the purchase orders using the Inventory Status column (red ones first) allows the planner to immediately focus on the purchase orders that should be treated first.
More details can be found on Inventory status
Read-only boolean flag indicating whether the purchase order is violating any material, lead time or capacity constraints.
This is very handy in interpreting unconstrained plans.
The criticality is a read-only field, calculated by the planning engine.
It represents an indication of the slack time in the usage of the purchase order.
A criticality of 0 indicates that the purchase order is on the critical path of one or more demands.
Higher criticality values indicate a delay of the purchase order will not immediately impact the shipment of any demand.
A criticality of 999 indicates a purchase order that isn’t used at all to meet any demand.
Note that the criticality is independent of whether the customer demand will be shipped on time or not.
The delay is a read-only field, calculated by the planning engine.
It compares the end data of the purchase order with the latest possible end date to ship all demands it feeds on time.