Viewing Forecast Demand for Phantom of ATO Model in the Horizontal Plan Form is Not Offset By the Models Processing Lead Time
(Doc ID 3040664.1)
Last updated on AUGUST 13, 2024
Applies to:
Oracle Advanced Supply Chain Planning - Version 12.2.6.3 and laterInformation in this document applies to any platform.
Symptoms
Assemble-to-Order (ATO) Model forecast is loaded into system and demand for the components is exploded. When viewing the forecast demand for a Phantom item that is a child of the ATO Model, it is not offset by the ATO Model's Processing lead time.
Bill of Material
ATO Model - Qty 1 with Processing Lead Time of 1 day
|
Phantom Item - Qty 1
On 24-JUN-2024, there is a forecast for 1 of the ATO Model. The forecast is loaded and exploded, but when viewing the forecast for the Phantom Item, the forecast is on 17-JUN-2024.
The expectation is that the Phantom Item have a forecast (which it does), but the forecast for the item should be offset by the models Processing Lead Time of 1 day.
The issue can be reproduced at will with the following steps:
- Set up model bill of material similar to this:
Model Item - Qty 1 / Processing Lead Time 1
|
Phantom Item - Qty 1 - Create a forecast in weekly buckets for the model item.
- Run the Planning Data Collection.
- Run the 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 |