OTM Does Not Re-drive the Shipment Start Time When the Parameter (PLAN SHIPMENTS WITH CARRIER COMMITMENT = TRUE)
(Doc ID 3001214.1)
Last updated on JANUARY 30, 2024
Applies to:
Oracle Transportation Management Cloud Service - Version 23.3 and laterInformation in this document applies to any platform.
Symptoms
OTM does not re-drive the shipment start time when the parameter (PLAN SHIPMENTS WITH CARRIER COMMITMENT = TRUE) & Property (glog.business.orderActions.unassign.redriveShipmentWithOptimalStartTime=true)
Example:
Orders:
Order-8AM (Early Pickup Date = 2023-10-02 08:00:00)
Order-9AM (Early Pickup Date = 2023-10-02 09:00:00)
Shipment ID: 1092599 (Start Time = 2023-10-02 09:00:00)
Unassign this order
Order1-9AM (Early Pickup Date = 2023-10-02 09:00:00)
Shipment ID: 1092576 (Start Time = 2023-10-02 09:00:00)
OTM does not re-drive the shipment start time when (PLAN SHIPMENTS WITH CARRIER COMMITMENT = TRUE), it does re-drive and set the correct start time (2023-10-02 08:00:00) when (PLAN SHIPMENTS WITH CARRIER COMMITMENT = FALSE)
Orders:
Order-8AM (Early Pickup Date = 2023-10-02 08:00:00)
Order-9AM (Early Pickup Date = 2023-10-02 09:00:00)
Shipment ID: 1092599 (Start Time = 2023-10-02 09:00:00)
Unassign this order
Order1-9AM (Early Pickup Date = 2023-10-02 09:00:00)
Shipment ID: 1092576 (Start Time = 2023-10-02 09:00:00)
OTM does not re-drive the shipment start time when (PLAN SHIPMENTS WITH CARRIER COMMITMENT = TRUE), it does re-drive and set the correct start time (2023-10-02 08:00:00) when (PLAN SHIPMENTS WITH CARRIER COMMITMENT = FALSE)
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 |