Incorrect SSD when scheduling lines with Ship Set. Schedule Arrival Date Blank. Subsequent plan run result in ATP Post Plan Processing Error
(Doc ID 2746314.1)
Last updated on FEBRUARY 10, 2021
Applies to:Oracle Global Order Promising - Version 12.2.9 and later
Information in this document applies to any platform.
In a recently upgraded UAT instance, ATP results are in correct when the lines are scheduled using ship set.
The SSD returned doesn't respect the shipping calendar and also the group Scheduled Arrival Date is NULL.
The subsequent runs of plans cause failure of the ATP Post Plan Request with below error:
27. Dmd ID : 1459900345 Inst : 1021 SO Line ID : 816011902 Inv Item :
3208497 Qty : 1 Date : Cust : 36520 Cst St ID: 5145 Refsh No :
72260446 Ordr No : 15431765 ATO Line ID : Session ID : 84829670 .
----Done Printing Records ----
---------Before calling schedule---------
After calling schedule: l_return_status : E
Error in call to Call_Schedule
Exception in call to Call_Schedule
Return Status : E
Error Message : User-Defined Exception
Unexpected Error. Sync Call To ATP failed
Sync Error: Unable to continue further
The session file shows the following:
Increment Schedule: ___________________Start Offset___________________
Increment Schedule: Req Ship Date:
Increment Schedule: Req Arrival Date:
Schedule: error := User-Defined Exception
Both 'Req Ship Date' and 'Req Arrival Date' values are null
Error encountered as null values of date filed is used in further calculation
Expect that the SSD returned by scheduling follows the shipping and receiving calendars.
Group Scheduled Arrival Date needs to be populated.
The issue can be reproduced at will with the following steps:
1. Enter the application.
2. Schedule an order with multiple lines having a ship set.
3. See the above behaviour.
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