Search Results hz_address_usage_dtls




Overview
Explore in AI Chat

Overview

HZ_ADDRESS_USAGE_DTLS is a Receivables (AR) module table in the Oracle E-Business Suite, owned by the AR schema and holding status VALID in both Release 12.1.1 and 12.2.2 of the ETRM documentation. The table stores the detail-level geography assignments attached to an address usage record within the Oracle Trading Community Architecture (TCA) / Customer data model. Where HZ_ADDRESS_USAGES records that a particular party site or location may be used for a given purpose (for example, a bill-to, ship-to, or remit-to usage), HZ_ADDRESS_USAGE_DTLS supplies the granular geographic qualifiers that apply to that usage, such as a country, state, province, or other registered geography type.

From a Data Vault modeling perspective, the mined relationship structure suggests a satellite-leaning classification. The table carries its own surrogate primary key and descriptive attributes, and it depends on a single parent via a foreign key to HZ_ADDRESS_USAGES. This is the classic satellite pattern: the business key context comes from the parent (the usage), while the detail rows describe qualifying attributes of that parent. Modelers should treat HZ_ADDRESS_USAGE_DTLS as a child/detail satellite of the HZ_ADDRESS_USAGES hub rather than as an independent hub or link.

Key Information Stored

The table contains 11 documented columns. The most significant are:

The distinction between the surrogate key (USAGE_DTL_ID) and the business key (USAGE_ID + GEOGRAPHY_TYPE) is important: the surrogate provides a stable internal reference, while the unique index on the business key guarantees that a given usage cannot repeat the same geography type.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all geography details for a party site's usage, validating that required geographies exist before address validation, and reconciling TCA data during data conversions or upgrades.

Example — list geography details for a specific usage:

SELECT usage_dtl_id, usage_id, geography_type
FROM   ar.hz_address_usage_dtls
WHERE  usage_id = :p_usage_id;

Example — join to the parent usage to obtain party site context:

SELECT u.usage_id, d.geography_type
FROM   ar.hz_address_usages u,
       ar.hz_address_usage_dtls d
WHERE  u.usage_id = d.usage_id
AND    u.party_site_id = :p_party_site_id;

Because the table is satellite-leaning and narrow, it is frequently used as a lookup in customer data quality reports and in the Address Validation / Geography Validation routines that confirm whether a registered usage satisfies geography requirements for tax and shipping.

Related Objects

  • HZ_ADDRESS_USAGES — the parent table; joined on HZ_ADDRESS_USAGE_DTLS.USAGE_ID = HZ_ADDRESS_USAGES.USAGE_ID.
  • HZ_ADDRESS_USAGE_DTLS_PK — primary key constraint on USAGE_DTL_ID.
  • HZ_ADDRESS_USAGE_DTLS_U1 — unique index on USAGE_DTL_ID.
  • HZ_ADDRESS_USAGE_DTLS_U2 — unique index on USAGE_ID, GEOGRAPHY_TYPE.
  • HZ_LOCATIONS and HZ_PARTY_SITES — the geographic and site context reached through HZ_ADDRESS_USAGES.
  • HZ_GEOGRAPHIES / geography reference tables — referenced indirectly through GEOGRAPHY_TYPE.
  • Public TCA APIs (for example, the Address Usage / Geography assignment APIs) that maintain rows in this table.

Together these objects form the address-usage-to-geography chain that underpins customer, tax, and shipping configuration in Oracle Receivables and the wider TCA stack.