Search Results hz_address_usages




Overview
Explore in AI Chat

Overview

HZ_ADDRESS_USAGES is a reference and configuration table owned by the AR (Receivables) schema in Oracle E-Business Suite, holding the address usage definitions available per country. In EBS 12.1.1 and 12.2.2, address usages control how a party site or location address is classified and validated — for example, identifying whether an address may be used for billing, shipping, or statements. Because the table governs which usages are permitted for a given country, it is a foundational configuration object for the Oracle Trading Community Architecture (TCA) party and location model.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. HZ_ADDRESS_USAGES functions primarily as a hub-like reference entity, defined by the surrogate key USAGE_ID and holding descriptive and status attributes. Its business-key relationships are enforced through unique indexes rather than expanded link tables, which is consistent with a hub-and-satellite design where the entity's descriptive columns remain attached to the parent hub.

Key Information Stored

The documented physical schema for this table contains 12 columns in the AR schema. The most significant of these are:

  • USAGE_ID — the surrogate primary key defined by HZ_ADDRESS_USAGES_PK, uniquely identifying each address usage record.
  • MAP_ID — a key column that, together with USAGE_CODE, forms a business-key candidate unique index (HZ_ADDRESS_USAGES_U2). It associates the usage with its country or mapping context.
  • USAGE_CODE — the code identifying the specific usage type, paired with MAP_ID in the business-key unique index.
  • STATUS_FLAG — indicates whether the usage is active or inactive for configuration and validation purposes.
  • OBJECT_VERSION_NUMBER — supports optimistic locking and concurrency control during updates.
  • CREATED_BY, CREATION_DATE — standard audit columns recording who created the record and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification and the login session responsible.
  • CREATED_BY_MODULE — identifies the module or process that created the record.
  • APPLICATION_ID — references the owning application, supporting multi-application partitioning of configuration data.

The surrogate key USAGE_ID is distinct from the business-key candidate (MAP_ID, USAGE_CODE), which is enforced by the unique index HZ_ADDRESS_USAGES_U2.

Common Use Cases and Queries

Typical use cases include validating whether a given address usage is permitted for a country, reporting on active usage configurations, and diagnosing party site address validation errors. A common query lists the usages available for a specific mapping context:

  • Joining to HZ_ADDRESS_USAGE_DTLS to obtain the detailed descriptions or translations behind each usage code.
  • Filtering by STATUS_FLAG to retrieve only active, currently valid address usages for a country.
  • Reporting on configuration and audit trails using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.
  • Querying by USAGE_CODE and MAP_ID to confirm that a requested business-key combination exists and is enabled.

A representative pattern selects USAGE_ID, USAGE_CODE, and STATUS_FLAG from HZ_ADDRESS_USAGES joined to HZ_ADDRESS_USAGE_DTLS on USAGE_ID, typically constrained by the relevant country mapping and requiring STATUS_FLAG to indicate an active usage.

Related Objects

The principal related object is HZ_ADDRESS_USAGE_DTLS, which references HZ_ADDRESS_USAGES through the foreign key column USAGE_ID. This child table carries the descriptive detail records associated with each usage, making the join on USAGE_ID essential for reporting and validation logic. Beyond this documented relationship, HZ_ADDRESS_USAGES integrates with the broader TCA party and address infrastructure, including location, party site, and country mapping objects that consume the MAP_ID and USAGE_CODE business keys. When investigating address classification or usage validation behavior, the primary relationship to follow is the parent-to-child link from HZ_ADDRESS_USAGES to HZ_ADDRESS_USAGE_DTLS on USAGE_ID, with configuration context supplied through MAP_ID and APPLICATION_ID.