Unable To Assign Rate As A Result Of Rate Record Expiration Date
(Doc ID 453681.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Transportation Management - Version 5.5.03.01 and later
Information in this document applies to any platform.
-- Problem Statement:
On 5.5 CU3 RU1:
The Assign Rate action is failing to rate because the shipment start time is near midnight of the expiration date of the rate record.
The effective/expiration dates are stored and treated as UTC. During the comparison, the shipment starttime is converted to UTC, which places it on the other side of midnight, causing the comparison to fail .
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