Incorrect Distance Calculation by OTM When PcMiler Distance Query Fails and Distance UOM Default is Changed from Miles
(Doc ID 1345540.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle Transportation Management - Version: 6.2.0 to 6.2.3 - Release: 6.2 to 6.2Information in this document applies to any platform.
Symptoms
When the is_storage_default and is_display_storage are set to Y for UOM code ‘KM’ (for type DISTANCE), if PCMiler is unable to return a distance for any reason and lat/long are not used on locations, the expectation is that the distance should be set to 0, however what is happening is that a very large value for the calculated miles is returned (e.g. 1609346998.3906531 MI)
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. |