Search Results hz_imp_addresses_int




Overview
Explore in AI Chat

Overview

HZ_IMP_ADDRESSES_INT is the TCA (Trading Community Architecture) open interface table used by Oracle Receivables to import address and party site information into the base tables HZ_LOCATIONS and HZ_PARTY_SITES. It resides in the AR schema and is a standard interface staging object within the E-Business Suite 12.1.1 and 12.2.2 data model. The table carries records loaded from external sources — legacy systems, third-party data conversions, or bulk maintenance processes — which are then validated and processed by the TCA address import concurrent program into the production location and party site entities.

From a Data Vault modeling perspective, the FK relationship to HZ_IMP_BATCH_SUMMARY suggests a satellite-leaning classification. This is a heuristic observation derived from the mined foreign key structure: the table hangs off a batch parent (HZ_IMP_BATCH_SUMMARY via BATCH_ID) rather than acting as an independent hub or a pure link between two business keys. In practice it functions as a transient staging entity, holding one row per address/site record scoped by its batch and origin-system reference.

Key Information Stored

The table contains 81 documented columns in the 12.2.2 schema. The most significant columns are grouped as follows.

No surrogate single-column primary key is documented on this interface table. Instead, the unique index HZ_IMP_ADDRESSES_INT_U1 spans BATCH_ID, SITE_ORIG_SYSTEM, SITE_ORIG_SYSTEM_REFERENCE, and PARTY_ID, constituting the documented business-key candidate. This composite key ensures one staged address/site row per batch, per originating system reference, per party.

Common Use Cases and Queries

The primary use case is bulk loading and reconciliation of customer address data during conversions or integrations. Typical operational queries include monitoring the status of a batch and diagnosing failed rows. For example, to check pending versus errored rows in a batch:

  • SELECT INTERFACE_STATUS, COUNT(*) FROM AR.HZ_IMP_ADDRESSES_INT WHERE BATCH_ID = :batch GROUP BY INTERFACE_STATUS;
  • SELECT BATCH_ID, SITE_ORIG_SYSTEM_REFERENCE, PARTY_ID, ERROR_ID FROM AR.HZ_IMP_ADDRESSES_INT WHERE INTERFACE_STATUS = 'ERROR';
  • SELECT a.PARTY_SITE_NUMBER, a.ADDRESS1, a.CITY, a.STATE, a.POSTAL_CODE FROM AR.HZ_IMP_ADDRESSES_INT a JOIN AR.HZ_IMP_BATCH_SUMMARY b ON a.BATCH_ID = b.BATCH_ID WHERE a.BATCH_ID = :batch;

Reporting scenarios include pre-import data quality validation (checking the STD columns against source values), duplicate detection within a batch using DUP_WITHIN_INT_FLAG, and audit of who loaded or last modified staged records via REQUEST_ID and PROGRAM_ID.

Related Objects

  • HZ_IMP_BATCH_SUMMARY — the batch parent; joined on HZ_IMP_ADDRESSES_INT.BATCH_ID = HZ_IMP_BATCH_SUMMARY.BATCH_ID. This is the only documented foreign key relationship.
  • HZ_LOCATIONS — one of the two target base tables populated after successful processing.
  • HZ_PARTY_SITES — the second target base table linking parties to locations.
  • HZ_PARTIES — parent party entity resolved via PARTY_ID and the origin-system references.
  • HZ_IMP_BATCH_SUMMARY (as master) — also governs concurrent program control and batch-level reporting.
  • TCA address import concurrent program — the processing engine that reads this table and writes HZ_LOCATIONS and HZ_PARTY_SITES.

This object should be treated as transient staging data; records are typically purged once imported, and it is not intended for long-term analytical retention.