Professional Documents
Culture Documents
ebsmodule.blogspot.in/2013/02/ascp-pegging-information-logic.html
SCENARIO - 1
==============
Consider we have a Finished Good Item A with the following BOM [Bill Of Material]
A -> Finished Good Item
B -> Subassembly Item
C -> Purchased Good.
So after running the Plan the pegging would like below in the UI [User Interface / Planners Work Bench]...
The ORIGINATION_TYPE is actually a number. represented here as a meaning for better understanding.
So as we see there would be three rows showing which demand is pegged to which supply. The Supply here is
the TRANSACTION_ID.
The below is what you are seeing. >>
The relation between the Planned Order Demand of B with the forecast demand of A is stored in the
PREV_PEGGING_ID .
1/3
The END_PEGGING_ID is the top demand in the whole chain.
SCENARIO - 2
=============
If we consider the quantities and we have 2 Forecasts in our Scenarios then how would the pegging work.
Consider we have a Finished Good Item A with the following BOM [Bill Of Material]
A -> Finished Good Item
B -> Subassembly Item
So after running the Plan the pegging would like below in the UI [User Interface / Planners Workbench]
The ORIGINATION_TYPE is a actually a number represented here as a meaning for better understanding.
The relation between the Planned Order Demand of B with the forecast demand of A is stored in the
PREV_PEGGING_ID .
The END_PEGGING_ID is the top demand in the whole chain.
SCENARIO - 3
=============
If we consider the quantities and we have 2 Forecasts in our Scenarios then how would the pegging work.
Consider we have a Finished Good Item A with the following BOM [Bill Of Material]
A -> Finished Good Item
B -> Subassembly Item
2/3
Also we have a On hand for Component B with quantity 5.
So after running the Plan the pegging would like below in the UI [User Interface / Planners Workbench]
The ORIGINATION_TYPE is a actually a number. represented here as a meaning for better understanding.
The relation between the Planned Order Demand of B with the forecast demand of A is stored in the
PREV_PEGGING_ID .
The END_PEGGING_ID is the top demand in the whole chain.
3/3