Can Not Control the Number of Characters Used for the Postal Code when Performing PcMiler Distance Lookups (Doc ID 789004.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

An External Distance Engine is configured to use a specific GEO_HIERARCHY where the POSTAL_CODE is truncated. The desired effect is to have OTM only send a partial POSTAL_CODE to PcMiler for the distance lookup. It is found by researching the logs, that the configured GEO_HIERARCHY is being ignored and the entire POSTAL_CODE is being sent to PcMiler.

For example, a GEO_HIERARCHY is configured to have: ZIP2_COUNTRY (with elements of POSTAL_CODE, with 1->2 offset, and COUNTRY). This is assigned to the Geo Hierarchy ID of the External Distance Engine. Even with this configuration, the logs show the entire POSTAL_CODE is sent in this call.

The reason that this configuration is being attempted, is due to the fact that the actual POSTAL_CODE for the location is not found in PcMiler. Providing a shortened POSTAL_CODE provides a reasonable estimate to the distance.

-- Steps To Reproduce:
1. Create an External Distance Engine where the Geo Hierarchy ID includes a truncated POSTAL_CODE.
2. Create a Rate Distance object using the above External Distance Engine.
3. Run an Ask-OTM -> Distance/Time query using this Rate Distance where the POSTAL_CODE information is assigned to the locations being queried.

In reviewing the logs, the entire POSTAL_CODE is sent to PcMiler.

Changes

Cause

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