Results for “hz_imp_relships_int”

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

Overview

HZ_IMP_RELSHIPS_INT is the TCA (Trading Community Architecture) interface table used to stage relationship data for import into the EBS customer model. Owned by the AR schema, it feeds the party relationship entities that underpin HZ_PARTIES, HZ_PERSON_PROFILES, and HZ_ORG_PROFILES. It sits in the inbound side of the TCA import pipeline: external sources (legacy systems, third-party feeds, data conversions) populate this table, a batch is registered in HZ_IMP_BATCH_SUMMARY, and the TCA import concurrent programs validate and transfer the rows into the production HZ_RELATIONSHIPS structures.

From a data modeling perspective, the mined FK structure suggests a satellite-leaning classification. Its single foreign key to HZ_IMP_BATCH_SUMMARY (via BATCH_ID) anchors each row to a batch event, while the descriptive columns (relationship attributes, status flags) describe the entity being imported rather than serving as an independent hub or a link resolving two hubs. Treat this as a heuristic suggestion rather than an authoritative classification.

Key Information Stored

The table carries 45 columns. The most significant for import processing are:

• BATCH_ID — Foreign key to HZ_IMP_BATCH_SUMMARY; groups rows into a single import run and drives restart/reprocessing logic.
• SUB_ORIG_SYSTEM and SUB_ORIG_SYSTEM_REFERENCE — Identify the source system and the primary party (the "subject" of the relationship).
• OBJ_ORIG_SYSTEM and OBJ_ORIG_SYSTEM_REFERENCE — Identify the counterparty (the "object") in the same manner.
• RELATIONSHIP_TYPE and RELATIONSHIP_CODE — Define the nature of the link (for example, contact-of, employee-of), driving which HZ_RELATIONSHIPS rows are created.
• START_DATE and END_DATE — Effective dating for the relationship.
• INSERT_UPDATE_FLAG — Controls whether the row results in an insert or an update during import.
• INTERFACE_STATUS and ERROR_ID — Track validation outcome and link failures to the error log.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — The standard DFF block for extensible attributes.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Audit columns identifying the concurrent request that processed the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard who-columns for row audit.

The physical table does not expose a surrogate primary key column in the documented schema; BATCH_ID plus the orig-system/reference pairs act as the practical business-key candidates for de-duplication.

Common Use Cases and Queries

The primary use case is mass relationship loading during customer conversions and integrations. A typical post-load reconciliation query checks validation status per batch:

SELECT i.BATCH_ID, i.INTERFACE_STATUS, COUNT(*)
FROM   AR.HZ_IMP_RELSHIPS_INT i
GROUP  BY i.BATCH_ID, i.INTERFACE_STATUS;

Failed rows are isolated by joining to the error log on ERROR_ID. A batch-scoped exception query:

SELECT i.SUB_ORIG_SYSTEM_REFERENCE, i.OBJ_ORIG_SYSTEM_REFERENCE,
       i.RELATIONSHIP_CODE, i.ERROR_ID
FROM   AR.HZ_IMP_RELSHIPS_INT i
WHERE  i.BATCH_ID = :batch_id
AND    i.INTERFACE_STATUS = 'E';

Reporting scenarios include auditing the source of a relationship for a given party, verifying effective-date coverage (START_DATE/END_DATE gaps or overlaps), and confirming that DFF attributes were populated before transfer. Because the table is a staging interface, it is normally purged after successful import, so it is queried for operational monitoring rather than ongoing analysis.

Related Objects

• HZ_IMP_BATCH_SUMMARY — Parent of the documented FK; join on HZ_IMP_RELSHIPS_INT.BATCH_ID = HZ_IMP_BATCH_SUMMARY.BATCH_ID to retrieve batch metadata.
• HZ_RELATIONSHIPS — Target table populated after successful validation and transfer.
• HZ_PARTIES — Party records referenced via the orig-system/reference pairs.
• HZ_PERSON_PROFILES and HZ_ORG_PROFILES — Party profile tables named in the object description; relationships distinguish person and organization participants.
• HZ_IMP_ERRORS — Error repository resolved through ERROR_ID.
• HZ_IMP_BATCH_SUMMARY.REQUEST_ID — Links a batch to the concurrent request that ran the import program.