Sales Orders Scheduling To Infinite Time Fence When ATP Enabled ASCP Plan Is Run With Anchor Date On Calendar Non Working Day
Last updated on FEBRUARY 15, 2017
Applies to:Oracle Global Order Promising - Version 12.2.4 and later
Information in this document applies to any platform.
In a VCP 18.104.22.168 ATP Based on Planning Data in TEST:
Sales Orders are scheduling to the infinite supply time fence (ITSF) when running the ATP plan on a non working day in the manufacturing calendar. Profile option MSC: Use enhanced forward ATP is set to Yes
9/22/2016 and 9/23/2016 are non working days on the mfg calendar.
Anchor date of the plan=9/22/2016.
Item attributes of the Finished good(Star item)Check ATP= Material Only and ATP components= Material and Resource.
Item attributes for the model check ATP= None, ATP components= Material and resource.
The star/configured item has a routing with a scheduled resource and planning time fence= 5 days.
There are other option class, options but none of them is a constraint
Now, go to 'ATP Inquiry' and put the configured model item with qty 1 and request date as sysdate or any date. Schedule ship date is always coming as ITSF... They checked the components under the star item, resource availability and there is no problem with availability
Now change the profile option MSC: Use enhanced forward ATP back to No - Same data and same test case, no change in supply for components and resource availability as this scenario was done in an instance with No order booking, no supply changes etc.. Now Schedule Ship Date is calculated correctly as per the available resource date.
Expect with profile option MSC: Use enhanced forward ATP = Yes that sales orders will schedule properly and not use ITSF when it's no necessary
Steps to Rerproduce
1. Run an ATP enabled ASCP plan with the anchor date of the plan on a non working day in the organization Mfg calendar
2. Set profile MSC: Use enhanced forward ATP = Yes
3. Configure a sales order line to create * item
4. Use ATP Inquiry and request any date and it comes back with scheduling that is the ITSF
5. Set the profile option to No
6. Query again with the same data and now the scheduling returns accurate date as expected
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms