Rate Distance Not Calculating Distance When Using Zip+4 But Same Zip5 Zip Code
(Doc ID 1354697.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Transportation Management - Version 6.1.0 to 6.2.4 [Release 6.1 to 6.2]Information in this document applies to any platform.
Symptoms
An External Distance Engine is configured with a SAME_SOURCE_DEST_DIST value.
Two locations are created where they have the same beginning Postal Code, but different extended Postal Codes (for example, 19118 and 19118-1234).
When doing a distance lookup, OTM only compares the initial part of the Postal Code and therefore these locations actually match and OTM should be simply returning the SAME_SOURCE_DEST_DIST value. However, this call is being made to MileMaker using the same Postal Code (e.g. 19118). This causes MileMaker to return an error. The error causes OTM to then calculate the Estimate distance (if permitted).
In such a scenario, OTM should simply return the SAME_SOURCE_DEST_DIST value instead of sending the reqeust to MileMaker.
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 |