External Engine Geo-Hierarchy Component Offsets not Truncating the Postal Codes
(Doc ID 793867.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Transportation Management - Version 5.5.05 to 5.5.05.04 [Release 5.5]
Information in this document applies to any platform.
This problem can occur on any platform.
-- Problem Statement:
On 5.5.05:OTM is not trimming the country postal code based on the address component off sets that are defined on external distance engine's Geo hierarchy.
OTM should use the start and end address component off sets to trim how many character to be sent to PcMiler. For example, if the start off set=1 and end off set=5 the OTM should send only the first 5 characters form the country postal code and not the complete string.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1- Navigate to Transportation Planning and Execution > Power Data > Geography > External Distance Engine > Define a New External Distance Engine.
2- Use a Geo Hierarchy for USA with postal code component with start offset = 1 and end offset = 5.
3- For example, use location with postal code = 81657 ND.
4- OTM should send out 81657 in the query to PcMiler and not 81657 ND.
From the logs you can see: pcmscalcdistance2("<VALUE>,US","81657 ND,US",0)
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