Can Not Reassign a Driver to Shipment that was Replaced by Assigning the Same Driver to Another Shipment Using "Replace Last Shipment"
(Doc ID 1562367.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Fleet Management - Version 6.2.0 to 6.2.9 [Release 6.2]Information in this document applies to any platform.
Symptoms
If you assign "Driver A" to shipment 1, then assign "Driver A" to shipment 2 (with "Replace Last Shipment") it (correctly) pulls "Driver A" off from shipment 1. However, as a 2nd step in the test, if you assign "Driver A" back to shipment 1 OTM does not offer the user the option with "Replace Last Shipment" checked. Because of this, "Driver A" ends up on both shipments again because OTM is not offering the user an option to assign the Driver and unassign from the existing shipment.
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 |