Procedure:For the selected country, define the hierarchical structure of geography types to establish:
How geographies can be related.
The types of geographies you can define for that country.
The geography types available for geography or tax validation.
With the Country geography type implicitly at the top of the structure, the subsequent levels are numbered with 1 as the next level after Country.
Caution: After you first define a country structure, you cannot later insert levels. You can only add geography types below the current lowest level, and delete geography types without defined geographies. This setup is usually a one-time procedure, so make sure that you define a complete and accurate country structure the first time.
You must add a geography type as a level in the country structure before you can define a geography for that geography type in a country. For example, before defining the state of California, the State geography type must be added to the United States country structure.
The country you want to define a structure for must be in the FND_TERRITORIES table.
Procedure:This table describes some terms in the pages used for this procedure.
Selected Terminology
| Term | Description |
|---|---|
| Geography Exists at Level | Indicates if at least one geography is defined for the geography type at this level. For example, if the geography type is State, and California is already added as a geography for State, then a geography exists at this level. At this point, you cannot make changes to this level, including deletion. |
If the country structure is completely undefined, then optionally copy the structure from another country.
The application provides you with a set of available master reference geography types. If needed, you can create a unique geography type before adding it to this or any other country structure.
Attention: To ensure that Oracle E-Business Suite applications leveraging Geography Hierarchy can allow users to enter or search a range of postal code values, use the seeded Postal Code geography type. Do not create a new type, for example called Zip Code.
Add geography types as needed. Each geography type is added right below the current lowest level.
You can delete geography types only if geographies do not exist at that level. If the geography type is not the lowest level in the country structure, then you delete not only that level but all levels below it.
Note: If you delete a geography type, then all associated validation mappings and usage for this level are also deleted. See: Managing Validations.
