Tree of Dependent Objects
A tree originating from the missing parts list is spread out, and it traces every uncovered position in the entire logistical chain until external demand. Hence, the connections are made either from defined relationships (make-to-order production) or through dynamic pegging. Through stepwise expansion, the influence of the missing parts is evident up to the sales requirement.
Information for Purchasing Parts
- Missing part material name and material number
- Requirement deadline for the missing part (date of the first material shortage)
- Missing quantity
- Sales in jeopardy
For the information regarding sales in jeopardy, all customer orders and supplier delivery schedules come from SAP ERP, in that the purchasing parts directly or indirectly flow in and thereby determine quantities in jeopardy and multiply them with the corresponding product price.
Information about the Orders
- Order start time
- Type of object (planned order, fixed planned order, production order)
- Order number
- At-risk quantity and percentage of total quantity in jeopardy with respect to the purchasing parts under consideration.
- Maximal delay time period for the production order that does not endanger the demand.
Quantities in jeopardy arise from the relationship of at-risk components to the quantity produced. This threat is followed along the logistical chain in the order's relationship with and flow into subsequent orders. Furthermore, the margin for temporal shifts results from the predecessor-successor relationship.
Information for the Sales Requirements
- Requirement ID number
- Requirement type
- Customer name, in the case that the requirement is a customer order
- Delivery deadline
- At-risk quantity and percentage of total quantity in jeopardy
- Sales in jeopardy based on the missing part position
- Quantity of missing parts necessary to counteract the danger