On-hand Pegged To Lower-priority Orders Instead To High-priority
(Doc ID 2729102.1)
Last updated on NOVEMBER 30, 2020
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.6 and later
Information in this document applies to any platform.
We have cases where priority pegging is not followed by the system - although demands are in the same demand window, the lower-priority demands are pegged to on-hand, and high-priority demands are pegged to purchase requisitions.
Only Supplier capacity constraints / Enforce Purchasing LT checked
PTF / DTF checked
Overwrite - None
Demand priority pegging with reservation and pegging - Project-Task
- use common supplies checked
365 days horizon
No decision rules
1 - sales orders/forecast/MDS
2 - request date
MSC: Include Safety Stocks in Priority Based Pegging Yes
MSC: Make Safety Stock Transient Yes
MSC: Minimize Project Cross Peg within Window Yes
MSC: Use Enhanced Project Netting Yes
MSO: Additional Demand Slices for Shared Supply Rescheduling -1
MSO: Avoid non working days for Buy/Transfer order dates Yes
MSO: Demand Window Size 28
MSO: Supply Window Size 500
MSO: Firm Requisitions Within Time Fence No
MSO: Lead Time Control Do not violate minimum processing times
should follow demand priority for sales orders when pegging on hand
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