Results for “hz_geographies”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The HZ_GEOGRAPHIES table, owned by the AR schema, stores data representing physical geographies within Oracle E-Business Suite. It is a foundational reference object in the Receivables (AR) module and the broader Trading Community Architecture (TCA) data model, providing the named geographic hierarchy that supports address validation, tax jurisdiction determination, territory assignment, and party location management. Each row represents a distinct geographical entity such as a country, state, province, county, city, or postal boundary, identified by a surrogate key and described through a series of numbered geography elements that define its position within a user-configured hierarchy.

Because the table holds mostly descriptive and classification attributes keyed by a surrogate identifier, and its principal outbound reference points to FND_TERRITORIES via GEOGRAPHY_CODE, the heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In modeling terms, HZ_GEOGRAPHIES behaves less like an independent hub and more like a descriptive satellite that enriches territory and location reference data with detailed geographic hierarchy and boundary metadata.

Key Information Stored

The table is documented with 69 columns in the 12.2.2 physical schema. The most significant are:

• GEOGRAPHY_ID — the surrogate primary key, enforced by the unique index HZ_GEOGRAPHIES_U1. This is the internal identifier used by all foreign key references from dependent tables.
• GEOGRAPHY_CODE — the business identifier that links to FND_TERRITORIES. This is the foreign key column connecting geography records to the territory definitions.
• GEOGRAPHY_NAME — the descriptive display name of the geography.
• GEOGRAPHY_TYPE — classifies the record (for example, country, state, city, or postal code), driving how the record participates in address validation and hierarchy resolution.
• GEOGRAPHY_USE — indicates the intended usage context of the geography record.
• START_DATE / END_DATE — effective dating that controls when a geography definition is valid and active.
• MULTIPLE_PARENT_FLAG — indicates whether the geography may belong to more than one parent in the hierarchy, affecting hierarchy traversal.
• COUNTRY_CODE — the country to which the geography belongs.
• GEOGRAPHY_ELEMENT1 through GEOGRAPHY_ELEMENT10 — a set of ten configurable hierarchy levels holding descriptive names, while the accompanying GEOGRAPHY_ELEMENTn_ID and GEOGRAPHY_ELEMENTn_CODE columns hold the corresponding identifiers and codes for each level.
• TIMEZONE_CODE — the time zone associated with the geography.
• GEOMETRY — spatial boundary data supporting map and geographic information system integration.
• Standard audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and the WHO/request context columns (APPLICATION_ID, PROGRAM_ID, REQUEST_ID) plus ATTRIBUTE1–ATTRIBUTE20 for extensibility.

Common Use Cases and Queries

HZ_GEOGRAPHIES is queried primarily for address validation, territory setup, and geographic hierarchy reporting. Typical patterns include:

• Retrieving a geography by its surrogate key: SELECT geography_name, geography_type FROM hz_geographies WHERE geography_id = :id;
• Joining to territory definitions to resolve codes: SELECT g.geography_name, t.territory_short_name FROM hz_geographies g, fnd_territories t WHERE g.geography_code = t.territory_code;
• Filtering by type and effective dates to list currently valid cities or states: WHERE geography_type = 'CITY' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
• Building hierarchy reports by inspecting GEOGRAPHY_ELEMENT1–10 and their ID and code counterparts to reconstruct parent-child paths.
• Reporting by COUNTRY_CODE or TIMEZONE_CODE for regional analytics.

Related Objects

• FND_TERRITORIES — joined on HZ_GEOGRAPHIES.GEOGRAPHY_CODE = FND_TERRITORIES.TERRITORY_CODE; the primary documented foreign key relationship.
• HZ_LOCATIONS — references geography identifiers to validate and standardize party site addresses.
• HZ_PARTY_SITES — consumes geography records when resolving the geographic components of a party site address.
• HZ_GEOGRAPHY_IDENTIFIERS — stores alternate identifiers and cross-references for geography records.
• JTF_TERRITORIES / territory assignment objects — leverage geography and territory relationships for sales and service territory modeling.