Standard Pegging : Need Clarification On Logic
(Doc ID 2571281.1)
Last updated on JULY 30, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 184.108.40.206.1 and later
Information in this document applies to any platform.
We have been using 'Standard Pegging' without any backward and forward window days for the last 7 years in an UnConstrained plan. Our businesses are focusing on creating schedule stability of the incoming shipments and as part of this, they have expressed a strong desire to understand how Oracle ASCP is creating Pegging details for certain PO shipments. The use case is described below -
1) We have incoming PO schedules which have the same 'Need by date' for 3 shipment lines.
2) All these 3 PO shipments have different project number.
3) Pegging records show that these different shipments are getting associated to demands which do not have the same project. ( they all do belong to the same Planning Group and we do know the Oracle out of box capability to net across planning groups)
4) When trying to align Demand and Supply; ASCP seems to be randomly picking up any 1 of the 3 PO shipments on the same day and suggesting a 'Reschedule In'.
We would want to understand how ASCP decides which shipment to Peg if there are more than one record due on the same day. In some cases, we have come across examples where ASCP ignores a shipment which is closer to Demand date but reschedules a later shipment. Screenshots to explain the same have been attached.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document