Conditional Booking Update is Resetting Status of Shipment To SECURE_RESOURCES_TENDERED Rather Than SECURE_RESOURCES_BOOKED
(Doc ID 2126682.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.3.7 to 6.4.2 [Release 6.3 to 6.4]Information in this document applies to any platform.
Symptoms
Having saved conditions defined when performing conditional booking tender, after updating the tender, the status on the shipment doesn't return to SECURE RESOURCES_BOOKED as expected but instead it is reverting to SECURE RESOURCE_TENDERED.
It is expected to have the status of the shipment reverted to SECURE RESOURCES_BOOKED
The issue can be reproduced at will with the following steps:
1. Configure Conditional Booking
2. Tender a shipment
3. Accept the tender
4. Update again the same tender
5. Notice the status of the shipment should be SECURE RESOURCES_BOOKED but instead it is SECURE RESOURCES_TENDERED
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 |