EDD Constrained Without Detailed Scheduling ASCP Plan Not Honoring Chronological Sequence Profile
(Doc ID 1453387.1)
Last updated on JANUARY 03, 2023
Applies to:Oracle Advanced Supply Chain Planning - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Users are on 12.1.3 apps and have applied 126.96.36.199 VCP/ASCP patching (upgraded from 188.8.131.52). Users run EDD constrained Without Detailed Scheduling (SCO) plan. The set profile MSC: Minimize changes to chronological sequence of supplies = Yes. For many items this profile seems to be working fine. However for some items, there are supplies inexplicably being pulled in from farther out in the plan horizon earlier than some other existing supplies. Examples:
Item Name = JMBuy
Org Code = PRD:M1
There are two purchase orders with the same qty = 8640:
A. This PO was originally promised 07-SEP-2012 and ASCP is rescheduling this supply to 09-JUL-2012
B. This PO was originally promised 10-AUG-2012 and ASCP is rescheduling this supply to 24-AUG-2012
With the profile set we would've expected the PO promised 10-AUG-2012 to be rescheduled into 09-JUL-2012 exactly opposite of what occurred above
1. Upgrade from 184.108.40.206 patching to 220.127.116.11 VCP/ASCP patching
2. Run EDD constrained without detailed scheduling plan with profile MSC: Minimize changes to chronological sequence of supplies = Yes
3. Many items seem to follow this profile very well but some item supplies are not earlier than other existing supplies. Suppliers get confused as to why an earlier supply would not be due first and this generates illogical rescheduling with suppliers and planners
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