Unable To Book Order Due To 'Scheduling Failed: ATP Processing Error' - Session File Shows NO_MATCHING_DATE_IN_CAL
(Doc ID 2833647.1)
Last updated on JUNE 21, 2023
Applies to:
Oracle Global Order Promising - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version and above, Scheduling and Sourcing
When attempting to book the order for an Non-ATPable item,
the following error occurs.
ERROR
-----------------------
Scheduling Failed: ATP Processing error'
ATP Session file shows the following lines:
Call_ATP_No_Commit: l_source_organization_id : xxxx
Call_ATP_No_Commit: l_to_organization_id :
Call_ATP_No_Commit: l_customer_id : yyyyyyyyyy
Call_ATP_No_Commit: l_customer_site_id : zzzzzzzzz
Call_ATP_No_Commit: l_from_location : ppppppp
Call_ATP_No_Commit: NO_MATCHING_DATE_IN_CAL
Call_ATP_No_Commit: l_start: 1
Call_ATP_No_Commit: j: 1
Call_ATP_No_Commit: ATP_PROCESSING_ERROR
Call_ATP_No_Commit: l_start:
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an order
Nav: Order Management (R) -> Orders -> Sales Orders
2. Try to book it.
Nav: Order Management (R) -> Orders -> Sales Orders -> Click on Book Order.
3. The above error pops up.
Changes
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 |
Changes |
Cause |
Solution |
References |