My Oracle Support Banner

Cannot Meet Request Date Or Latest Acceptable Date For Item AS050##Y120180X (Doc ID 2719284.1)

Last updated on OCTOBER 13, 2020

Applies to:

Oracle Global Order Promising - Version 12.2.6.3 and later
Information in this document applies to any platform.

Goal

The planning horizon is 91 days while ATP Rule infinite time fence = 126
This caused scheduling to behave strangely in our testing

e.g. Lead time setting for item is 30+ days and we get schedule date based on Infinite time fence = 126 and that date is past the end of the plan horizon of 91 days
When lead time was reduced to < 30 days, then we got the expected date based on item lead time.

Then we found that setting profile value "MSC: Maximum Increments in Forward Scheduling" to the 91 days of the planning horizon fixed the issue.
Also tested reducing value to 30 and the issue still does not appear.
After removing the profile value the issue is back.
It is pretty odd that MSC: Use Enhanced Forward ATP when lead time <30 days if "MSC: Maximum Increments in Forward Scheduling" is not set - but > 30 days we get bad date far into future

We need to understand that so we can set the right value for the profiles that control forawrd scheduling in ATP

 


 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.