1. HCM Data Loading Business Objects
  2. Guidelines for Loading Geography Hierarchy

Guidelines for Loading Geography Hierarchy

This topic describes the considerations for loading geography hierarchy using HCM Data Loader (HDL).

Geography Hierarchy Data

User Key

The user key for geography hierarchy is Name.

Name

You can activate a geography hierarchy by providing a valid geography hierarchy node as per its current structure.

Start Date and StartOnActivationFlag

You must provide a unique StartDate. If the StartOnActivationFlag is Y, then don't provide a StartDate. If it's N, then you can set a future StartDate.

StatusCode

You can set only one geography hierarchy as current by setting the StatusCode as ORA_ACTIVE and the StartDate to the most recent past date.

Note: You can't delete a current geography hierarchy. Node names are validated against the TCA geography reference data.

Geography Hierarchy Node Data

You can define the geography hierarchy structure for various countries using the geography hierarchy structure FSM. You can select a maximum of two sub-levels per country.

For example, you may configure the two sub-levels for the United States in the following ways:

  • Level1 - State, Level2 - City

  • Level1 - County, Level2 - City

Given below is the geography structure for various countries used in GeographyHierarchy.dat.

This table lists the geography structure for various countries used in GeographyHierarchy.dat

User Key

User keys for geography hierarchy node are listed below.

  • Name, CountryCode

  • Name, Level1, CountryCode

  • Name, Level2, Level1, CountryCode

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7, GeographyElement8

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7, GeographyElement8, GeographyElement9

  • Name, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7, GeographyElement8, GeographyElement9, GeographyElement10

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7, GeographyElement8

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7, GeographyElement8, GeographyElement9

  • Name, Level2, Level1, CountryCode, GeographyElement1, GeographyElement2, GeographyElement3, GeographyElement4, GeographyElement5, GeographyElement6, GeographyElement7, GeographyElement8, GeographyElement9, GeographyElement10

You can primarily use the first three of the user keys viz. Name, CountryCode, or Name, Level1, CountryCode, or Name, Level2, Level1, CountryCode.

You can use the remaining seventeen if there are two locations with the same user key combinations as in Level1, CountryCode, or Level2, Level1, CountryCode. This is because a location in TCA geographies can have up to ten levels. So, you must provide all the geography elements to identify the location uniquely.