Rates Using A Location ID Are Not Working.
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 5.5.04
This problem can occur on any platform.
-- Problem Statement:
When a Rate Record Rate Cost is set with a rate cost basis of Destination Location ID and Ship Unit Specification ID, the rate is not used and the order fails to plan.
In the logs it can be seen that the destination ID is not being used but the length of the ship unit is being used in place of the destination location ID and therefore the rate is failed.
A Rate Record is created.
Source = Location A.
Destination = Location B.
The Rate Cost Basis is set to:
"Ship Unit Specification ID" "=" "Large box"
"AND" "Destination Location ID" "=" "B"
The cost details as also populated and the Rate Record is saved.
An order is created to go from location A to location B with the following constraints:
Transport Handling Unit to LARGE BOX and Destination Location ID to B
Buy Rate Record ID on the Constraints tab set to be the Rate Record created above.
When the order is planned the error "No Shipments Built For Order Bundle" is shown in the UI.
The log contains the following error:
"RECharge.evaluate(): Testing: ((SHIPMENT.SHIPUNITS.SPEC <LARGE BOX> = LARGE BOX) and (SHIPMENT.DEST.LOCATION <1 FT> = XXX.B)) [ExecuteThread: '26' for q]"
The code is incorrectly evaluating the Shipment Destination ID against the length of the Ship Unit.
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