OTM Shipment Stop Window Displays Stop Pickup Appointment Date/Time Same as Estimated Arrival Date/Time Instead of Actual Appointment Start Date/Time
(Doc ID 2945939.1)
Last updated on MAY 01, 2023
Applies to:
Oracle Transportation Management Cloud Service - Version 23.1 and laterInformation in this document applies to any platform.
Symptoms
After upgrading into OTM Quarterly 23.A, sometimes, Customers are facing challenge that - Shipment Stop's Pickup Appointment field showing Date/Time same as Estimated Arrival Date/Time instead Appointment Start Time.
This is specifically happening while customer is trying to schedule appointment before the Estimated Arrival date/time. However, in case, the appointment has been scheduled after the Estimated Arrival date/time - then there is no data mismatch.
Note:
In either case, Appointment Information Manager shows the correct data for actual Appointment Start Time.
Expected Outcome :
Shipment Stop's Pickup Appointment field should be displaying the actual Appointment Start date/time for the Stop.
Steps to Replicate :
2. For one of the Stops, assume, the Estimated Arrival date/time is 05-Jan-2023, 11:00:00.
3. Now, customer is trying to Schedule the Appointment for that Stop at 05-Jan-2023, 08:00:00
4. Once, appointment created, if they open the Shipment and navigate to Stops tab, then for the concerned stop, the Pickup Appointment will be displaying the date/time as 05-Jan-2023, 11:00:00. However, it was supposed to be displayed as 05-Jan-2023, 08:00:00
Changes
This observation appears for few customers (NOT for all) after OTM 23.A quarterly upgrade.
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 |