OTM Is Setting Wrong Appointment Time When Schedule Appointment Action Is Used
(Doc ID 2443695.1)
Last updated on SEPTEMBER 19, 2023
Applies to:
Oracle Transportation Management Cloud Service - Version 18 and laterOracle Transportation Management - Version 6.4.3 and later
Information in this document applies to any platform.
Symptoms
The Shipment's Schedule Appointment action updates the Shipment Stop with the end time of the appointment, while it should be the start time of the appointment.
Example:
-----------
Agent (SHIPMENT APPOINTMENT TRACKER) is active
Property (glog.appointment.shipmentstop.updateAppointmentTime) is set to false
Shipment ID: 02533 > Actions > Operational Planning > Dock Scheduling > Schedule Appointment > Select the Drop off Stop > Select the time slot and save.
Selected Time Slot:
Start Time
2018-07-08 22:00:00 UTC
End Time
2018-07-08 22:30:00 UTC
The Delivery Appointment on the Shipment Stop is 2018-07-08 22:30 UTC, its expected to be 2018-07-08 22:00:00 UTC.
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 |
| Cause |
| Solution |
| References |