My Oracle Support Banner

Using DEADHEAD Distance to Rate Shipment Instead of LOADED Distance When Order has Zero Weight (Doc ID 882880.1)

Last updated on JULY 09, 2014

Applies to:

Oracle Transportation Management - Version: 6.0 to 6.0.3
This problem can occur on any platform.

Symptoms

-- Problem Statement:

When an order has zero weight, but non-zero volume, the miles are entirely being categorized as DeadHead. This causes only the DeadHead Rate Cost to be used. This happens even for a regular two-stop shipment where there is no deadhead.

-- Steps To Reproduce:
1. Create an Order with Zero Weight and Non-Zero Volume
2. Plan the order onto a shipment
3. Notice the following in the logs:

RateEngineDetails RECharge.evaluate(): Testing: (SHIPMENT.LOADEDDISTANCE <0 MI> between 0.1
MI..5.4 MI) batch - 2
RateEngineDetails RECharge.evaluate(): Testing: (SHIPMENT.DEADHEAD_DISTANCE <62.08 MI>
between 0.1 MI..5.4 MI) batch - 2

Note: LOADEDDISTANCE is 0 and DEADHEAD_DISTANCE is positive.

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.