Results for “hz_imp_addressuses_int”

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

Overview

HZ_IMP_ADDRESSUSES_INT is a TCA (Trading Community Architecture) interface table owned by the AR schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It serves as the inbound staging area for party site use records, feeding the TCA base table HZ_PARTY_SITE_USES. Address uses define the purpose or context under which a party site is employed — for example, bill-to, ship-to, or statement-to designations — and are a mandatory component of customer and party site setup in Receivables, Order Management, and related modules.

Records enter HZ_IMP_ADDRESSUSES_INT through the TCA batch import infrastructure, typically by way of the Customer Interface or Bulk Import programs, or through direct SQL loads performed by integration and data-conversion teams. From this staging table, the import concurrent programs validate, derive, and transfer the data into the production TCA model. The table is transient by nature; rows accumulate only between load and the completion of the import run, after which they may be purged according to the batch retention policy.

From a Data Vault modeling perspective, the foreign-key topology classifies this table as satellite-leaning. It carries descriptive and status attributes attached to a business entity (the site use) keyed through originating-system identifiers, rather than representing an independent hub or an associative link between hubs. This classification is a heuristic modeling suggestion, not an Oracle-documented designation.

Key Information Stored

The table contains 20 documented columns. The most significant for import processing and troubleshooting are the following.

• BATCH_ID — Identifies the import batch to which the row belongs; foreign key to HZ_IMP_BATCH_SUMMARY, and the primary grouping key for monitoring and restart logic.
• PARTY_ORIG_SYSTEM / PARTY_ORIG_SYSTEM_REFERENCE — The originating system and its unique party identifier, used to resolve the target party in TCA.
• SITE_ORIG_SYSTEM / SITE_ORIG_SYSTEM_REFERENCE — The originating system and its party site identifier, resolving the specific site to which the use belongs.
• SITE_USE_TYPE — The purpose code for the site (for example, BILL_TO, SHIP_TO, or STATEMENT_TO); one of the principal business attributes validated during import.
• PRIMARY_FLAG — Indicates whether the use is the primary one of its type for the site.
• INSERT_UPDATE_FLAG — Determines whether the interface row results in an insert, an update, or both against HZ_PARTY_SITE_USES.
• INTERFACE_STATUS — The processing status of the row (for example, Pending, Success, or Error), the central column for reconciliation queries.
• ERROR_ID — Points to the message repository entry describing why a failed row was rejected.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns maintained by the interface and import programs.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — The concurrent request and program context that last touched the row, used to trace which import run processed it.
• CREATED_BY_MODULE — Identifies the module that originated the interface record.

The documented schema exposes no separate surrogate primary key column; rows are identified operationally by the combination of batch context and originating-system references, which serve as the effective business keys. The only documented foreign key is BATCH_ID to HZ_IMP_BATCH_SUMMARY.

Common Use Cases and Queries

Reconciliation of load success is the most frequent operational requirement. A typical query counts rows by status within a batch:

SELECT interface_status, COUNT(*)
FROM   hz_imp_addressuses_int
WHERE  batch_id = :p_batch_id
GROUP BY interface_status;

Error triage joins failed rows to the batch summary to expose the parent batch and any shared diagnostic context:

SELECT a.batch_id, a.site_use_type, a.error_id, b.*
FROM   hz_imp_addressuses_int a,
       hz_imp_batch_summary  b
WHERE  a.batch_id = b.batch_id
AND    a.interface_status = 'ERROR';

Conversion teams also pre-validate staged data by profiling SITE_USE_TYPE distribution and detecting duplicate primary-flag conflicts before submitting the import concurrent program. Post-import audits verify that every interface row marked successful has a corresponding HZ_PARTY_SITE_USES record, matching on originating-system references.

Related Objects

The following objects participate in the same processing flow and are most frequently joined with this table.

• HZ_IMP_BATCH_SUMMARY — Parent batch header; joined on BATCH_ID (documented foreign key).
• HZ_PARTY_SITE_USES — The TCA base table into which successful interface rows are loaded.
• HZ_IMP_PARTIES_INT — Staging table for parties referenced by the originating-system party keys.
• HZ_IMP_LOCATIONS_INT and HZ_IMP_PARTY_SITES_INT — Staging tables for locations and sites that must import successfully before site uses can resolve.
• HZ_PARTY_SITES and HZ_PARTIES — Production TCA tables resolving the site and party references.
• HZ_IMP_ERRORS_INT or its error-message repository — Typically joined through ERROR_ID for diagnostic text.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — Joined on REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to trace the processing run.

Because the table is an interface object, it should never be queried for authoritative site use data; HZ_PARTY_SITE_USES remains the system of record after import completes.