MSC: Consume Forecast Within Demand Time Fence Not Working As Expected
(Doc ID 2475575.1)
Last updated on JULY 26, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.5 and later
Information in this document applies to any platform.
PTF and DTF checked
Spread forecast checked
projects-task demand priority pegging
120 days / 18 wks / 7 periods
Include Past Due Forecast - 31
We are testing the functionality of the profile option MSC: Consume forecast within demand time fence.
We created following test case in one of our development instance: -
Item --> TEST_DTF4
Demand Time fence was set to 8 for the item at the organization level.
A forecast set--> T_CON was created whose forward days--> 40 and backward days--> 20.
A forecast namely --> CON_T and the forecast demand was created as per below details :-
A.) 16-Nov 40(Quantity) PAST DUE Demand
B.) 19-Nov 60(Quantity) Between Anchor Date and DTF
C.) 21-Nov 60(Quantity) Between Anchor Date and DTF
D.) 10-Dec100(Quantity Outside Demand Time Fence
The sales order for 100 quantity was created whose scheduled ship date was set to 20-Nov-2018.
When set to No--> the planning engine should drop the past due forecast and the two
forecast entries between the anchor date and the demand time fence date and shall use
the sales order for 100 to consume the forecast entry for 100 which is outside the
demand time fence. The attached file shows the results when the profile option was set to No.
When set to Yes--> the planning engine should the sales order for 100 to consume the
forecast entry for 40 which is past due and to consume one forecast entry for 60
between the anchor date and the demand time fence date.
It shall not use the two consumed forecast entries in the gross-to-net explosion. The
other forecast between the anchor date and the demand time fence date shall not be
consumed and should not used in the gross-to-net explosion. The forecast entry outside the
demand time fence should not be consumed but used in the gross-to-net explosion.
But we are not achieving the expected results when profile is set to Yes. Kindly help us to guide why the profile option is not working as expected when set to Yes.
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