The Sugg Start Date of the Assembly and the Sugg Due Date of Component Does Not Match
(Doc ID 2274455.1)
Last updated on SEPTEMBER 01, 2023
Applies to:
Oracle Advanced Supply Chain Planning - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
When running unconstrained plan, Sugg Start Date of the Assembly and the Sugg Due Date of component does not
match if Sugg Start Date of the Assembly in weekly bucket and the Sugg Due Date of component in daily bucket.
Example:
Assembly:(Leadtime=10)
Sugg Start Date:04/28/2017 00:00:00
Sugg Due Date:05/12/2017 00:00:00
UNBUCKETED_DEMAND_DATE=05/10/2017
Component:
Sugg Due Date:04/26/2017 00:00:00
Weeks Start Date of the plan is 05/08/2017. And the unbucketed demand date of the assembly is 05/10 and Non-working days are Saturday and Sunday. So, Sugg Due date of the assembly is 05/12/2017(Bucketed).
05/12/2017(Bucketed) - 10 working days = 4/28 (Sugg start day)
4/26 | 4/27 | 4/28 | 4/29 | 4/30 | 5/1 | 5/2 | 5/3 | 5/4 | 5/5 | 5/6 | 5/7 | 5/8 | 5/9 | 5/10 | 5/11 | 5/12 | 5/13 |
Sugg Start Date | Non-Working day | Non-Working day | Non-Working day | Non-Working day | Weeks Start Date of the plan | Demand Date(Unbucketd) | Sugg Due Date(Bucketed) | Non-Working day |
But sugg due date of the component is 4/26.
Expected Behavior
Sugg Start Date of the Assembly and the Sugg Due Date of component matches.
Steps to Reproduce
- Create sales order for the item which has component.
- Run Data Collection.
- Run unconstrained plan.
Cause
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
Symptoms |
Cause |
Solution |
References |