Rate Factor Value Not Using Step "Cost Value" When Defining Rate Factor Rule with Factor/Cost Increase
(Doc ID 2293313.1)
Last updated on JUNE 26, 2019
Applies to:
Oracle Transportation Management  Version 6.0 and laterInformation in this document applies to any platform.
Symptoms
A Rate Factor Rule is configured with a single Maximum Factor Value and Cost Value. Then a Factor Increase and Cost Increase is assigned with the intention of extending these values forward.
If a Rate Factor Source value does NOT match exactly the step of the Factor Increase, then the cost is being calculated by interpolating the Cost Increase. It is expected that the Cost Increase is a Step Function and that the calculated value be exactly within the Cost Step.
As an Example:
Maximum Factor Value=1.0
Cost Value=0.0
Factor Increase=0.1
Cost Increase=0.01
The expectation is that the values start with the Maximum Factor Value (1.0) with Cost Value (0.0) and extend forward as follows
Maximum Factor Value Cost Value
1.00 0.00
1.10 0.01
1.20 0.02
1.30 0.03
1.40 0.04
...etc...
Let's say a Rate Factor with Source value of 1.12 is processed. Since this matches the Step with Maximum Factor Value of 1.20, the expected Cost Value is the row matching that Step, which is 0.02. Instead, the Value is being processed as 0.012.
Maximum Factor Value=1.0
Cost Value=0.0
Factor Increase=0.1
Cost Increase=0.01
The expectation is that the values start with the Maximum Factor Value (1.0) with Cost Value (0.0) and extend forward as follows
Maximum Factor Value Cost Value
1.00 0.00
1.10 0.01
1.20 0.02
1.30 0.03
1.40 0.04
...etc...
Let's say a Rate Factor with Source value of 1.12 is processed. Since this matches the Step with Maximum Factor Value of 1.20, the expected Cost Value is the row matching that Step, which is 0.02. Instead, the Value is being processed as 0.012.
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 