Planned Order Quantity For Primary Component Based On Residual Quantity Of Substitute
(Doc ID 834624.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 126.96.36.199 and later
Information in this document applies to any platform.
This problem can occur on any platform.
On 188.8.131.52 (RUP #33) in Test:
In an Enforce Demand Due Date (EDD) plan, when profile option 'MSO: Use Up Existing Supply of Primary Components Before Substitute = YES', ASCP suggests two planned orders for the primary component instead of one. The first planned order for the primary component is based on the residual On Hand quantity of the substitute component.
Example: Bill of Material where 1 parent item (gdsubparent) requires 40 primary components (gdsubcomponent). The substitute component (gdsub) quantity is also 40.
There is 100 On hand for the substitute component and zero On Hand for the primary component and the parent item.
Demand = 200
ASCP will use 80 substitute items to build 2 parent items.
This means that another 198 parent items need to be build. 198 * 40 = 7920 component requirements.
ASCP recognizes that there are 20 left on hand for the substitute component and appears to be
taking this figure to create the first planned order for the primary component, i.e. one planned
order for 20 for the primary component. The additional 7900 required are met by a second planned
When we increase the On Hand for the substitute component to 110 and rerun Collections and ASCP,
the residual quantity for the substitute component will now be 30.
The primary component requirements are still 7920 but ASCP recognizes that 30 are on hand for the
substitute component and will create two planned orders for the primary component: one planned
order for 30 and one planned order for 7890.
Expect to get one planned order for 7920.
The issue can be reproduced at will with the following steps:
1. From the ASCP responsibility, run an EDD constraint plan with BOM component substitution turned on
The issue has the following business impact:
Component substitution is critical to our business. We are using constraint planning only to
leverage this feature and its paramount that this works properly for us.
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