Geo Hierarchy and Geo City Hierarchy Requirements Inconsistent (Doc ID 1363176.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version 6.2.0 to 6.2.4 [Release 6.2]
Information in this document applies to any platform.

Symptoms

When creating a Region with a Geo Hierarchy of CITY, the required fields are City/Province Code, the following issue is seen:

-- Issue
Country not even available for entry

-- Expected Behavior
That Country would be a valid option for entry

-- Steps
The issue can be reproduced at will with the following steps.
Log into a support instance running OTM 6.2

1. Created Rate Record of Rate_Record 1 with a Source and Destination Geo Hierarchy of City.
2. On the attributes tab input the following:

Source Geography
City - <some city>
Province Code- <city's state>
Country Code ID - <city's country code>

Destination Geography
City - <a different city>
Province Code- <city's state>
Country Code ID - <city's country code>

3. Click Finished
4. Navigated to Shipment Management > Power Data > Geography > Region
5. Clicked New and created Region_1 for my Region
6. Clicked new Region Detail
7. Here, I input CITY for Geo Hierarchy ID
8. I am now only allowed to enter a Province Code and City and I entered PA and PHILADELPHIA respectively

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms