Shipment Built with an Expired Rate because the Rate is Set as a Constraint on the Order Release. (Doc ID 1293059.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 6.0.3 and later   [Release: 6 and later ]
Information in this document applies to any platform.

Symptoms


On OTM Rate Records that are Expired and Inactive are being used when an Order Release has the Rate Record set in the Constraints Tab.

EXPECTED BEHAVIOR
-----------------------
Expect an inactive and expired rate to not be used.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1 - Log onto an OTM 6.0 system.

2 - Create a Rate Offering:
ID: 1234

3 - Create a Rate Record:
ID: 1234
Effective date: 6th Jan 2011
Expiration date: 20th Jan 2011
Not set to be active.
From Location :LJS_ORACLE_LONDON
To Location: LJS_ORACLE_BRISTOL
100 USD per Shipment.

4 - Create Order Release:
ID: 1234
Early Pickup Date: 25th Jan 2011
Late Delivery Date: 31st Jan 2011
Constraints tab: Sell Rate Offering and Record: 1234

5 - Click Actions > Operational Planning > Create Sell Shipment > Direct > OK.

6 - A Shipment is created.

The financials tab of the Shipment show that the Rate Offering is 1234 and the Rate Record is 1234 yes the Rate Record is not active and is expired.

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