Search Results hz_address_usage_dtls_u1

Overview

The AR.HZ_ADDRESS_USAGE_DTLS table is a TCA (Trading Community Architecture) registry object that stores the required geography components for each address usage, scoped by country and address style. In Oracle EBS, the Registry and Geography modules must validate that an address or party site carries the correct geography elements before it can serve a given purpose. Because those requirements differ by purpose — for example, an address used purely for geographic/territorial assignment may require different components than one used for tax jurisdiction determination — the table acts as the configuration backbone that enumerates which geography types are mandatory for a given usage context.

The table resides in the AR schema, is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and holds VALID status. The ETRM relationship data classifies this object as satellite-leaning under a heuristic Data Vault model. That is a modeling suggestion rather than a physical characteristic: the table is a dependent, descriptive structure keyed to a parent usage entity, and it carries a composite business key (USAGE_ID, GEOGRAPHY_TYPE) that makes it read most naturally as a satellite hanging off the HZ_ADDRESS_USAGES hub/link, with USAGE_DTL_ID as a surrogate row identifier.

Key Information Stored

The primary key of the table is HZ_ADDRESS_USAGE_DTLS_PK, defined on the surrogate identifier USAGE_DTL_ID, documented as the unique address usage detail identifier. Two unique indexes provide the business-key candidates. HZ_ADDRESS_USAGE_DTLS_U1 is a unique index on USAGE_DTL_ID, satisfying the primary-key role; HZ_ADDRESS_USAGE_DTLS_U2 is a unique index on the combination of USAGE_ID and GEOGRAPHY_TYPE, which enforces the natural business rule that a single address usage may not repeat the same required geography component. The most important columns are:

• USAGE_DTL_ID (NUMBER, 15) — surrogate primary key identifying each detail row.
• USAGE_ID (NUMBER, 15) — foreign key to HZ_ADDRESS_USAGES, identifying the parent address usage.
• GEOGRAPHY_TYPE (VARCHAR2, 30) — the required geography type for that usage; the second component of the natural business key.
• OBJECT_VERSION_NUMBER (NUMBER, 15) — optimistic concurrency control value used by the TCA/BC4J layer during updates.
• APPLICATION_ID (NUMBER, 15) — TCA Who column identifying the owning application.
• CREATED_BY_MODULE (VARCHAR2, 150) — TCA Who column recording the module that created the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who audit columns.

Common Use Cases and Queries

The dominant use case is determining which geography components must be supplied for an address usage before the address is considered complete. Administrators and implementers query by usage to validate configuration when onboarding a new country, and integrations read the same rows to decide which geography segments to populate on an address or party site.

• List all required geography types for a given usage: SELECT GEOGRAPHY_TYPE FROM AR.HZ_ADDRESS_USAGE_DTLS WHERE USAGE_ID = :p_usage_id;
• Resolve the parent usage context by joining to HZ_ADDRESS_USAGES on USAGE_ID.
• Audit recent configuration changes using the Who columns, e.g. filtering on LAST_UPDATE_DATE.
• Detect duplicates or conflicts on the business key (USAGE_ID, GEOGRAPHY_TYPE) to confirm index U2 integrity.
• Drive validation logic in custom address-entry forms by checking required geography types before save.

Related Objects

The table references exactly one object: AR.HZ_ADDRESS_USAGES, via USAGE_ID → HZ_ADDRESS_USAGES. ETRM records no other outgoing dependencies, and the object is not referenced by any downstream database object. In practice, the surrounding TCA/Geography family that depends on or consumes this configuration includes:

• HZ_ADDRESS_USAGES — parent usage definition (mandatory FK target).
• HZ_GEOGRAPHY_TYPES (lookup/validation for GEOGRAPHY_TYPE).
• HZ_LOCATIONS / HZ_LOC_ASSIGNMENTS — geography assignments validated against required types.
• HZ_PARTY_SITES — party site addresses whose usage requirements are enforced.
• HZ_CODE_ASSIGNMENTS — classification of addresses by use, linked through usages.

Because HZ_ADDRESS_USAGE_DTLS is a satellite-style configuration table, changes to it ripple directly into address validation behavior across the TCA stack.