Unable To Assign Rate As A Result Of Rate Record Expiration Date (Doc ID 453681.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 5.5.3.1
This problem can occur on any platform.

Symptoms

-- 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 .

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms