Shipment Time Become Infeasible After Tender Accepted
(Doc ID 2856818.1)
Last updated on MARCH 20, 2022
Applies to:
Oracle Transportation Management Cloud Service - Version 21.3 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
--------------
An order release is planned in 2 shipments(multi-leg), on shipment creation the feasibility code is FEASIBLE but when the 1st leg shipments tender
accepted is done(the acceptance date & time is within the earliest start time & latest start time of 1st leg shipment) the feasibility code
becomes TIME-INFEASIBLE for the 1st leg shipment. there is no change on the 2nd leg shipment.
Expected Behavior
------------------
Feasibility Code should remain FEASIBLE
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 |