Results for “error_id”

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

Overview

HZ_IMP_CONTACTS_INT is the TCA (Trading Community Architecture) interface table used by Oracle Receivables (AR) and the broader E-Business Suite party model to stage inbound contact and contact-relationship data before it is validated and loaded into the base TCA tables HZ_PARTIES, HZ_RELATIONSHIPS, and HZ_ORG_CONTACTS. It physically resides in the AR schema, is documented as VALID, and contains 57 columns in ETRM 12.2.2. Rows are inserted by external source systems, feeder programs, or integrated applications, then processed by the TCA contact import concurrent program.

Its role is that of a staging/satellite interface: it captures descriptive contact attributes (titles, departments, reference flags, effective dates) keyed to originating source systems so the loader can match, insert, or update the corresponding base records. The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning, meaning the table is best modeled as descriptive, change-tracking detail attached to a business key (batch plus source identifiers) rather than as an independent hub of identities.

Key Information Stored

The most significant columns fall into three groups: batch control, source identity, and contact detail.

• BATCH_ID — link to the controlling batch row in HZ_IMP_BATCH_SUMMARY; drives grouping and processing.
• CONTACT_ORIG_SYSTEM and CONTACT_ORIG_SYSTEM_REFERENCE — the originating system and its reference for the contact; combined with BATCH_ID these form the unique business key HZ_IMP_CONTACTS_INT_U1 (BATCH_ID, CONTACT_ORIG_SYSTEM, CONTACT_ORIG_SYSTEM_REFERENCE). Notice there is no surrogate primary key column documented; uniqueness is enforced entirely by this composite business-key index.
• OBJ_ORIG_SYSTEM / OBJ_ORIG_SYSTEM_REFERENCE and SUB_ORIG_SYSTEM / SUB_ORIG_SYSTEM_REFERENCE — originate the party (object) and subject parties, enabling relationship resolution.
• INSERT_UPDATE_FLAG — instructs the loader whether to insert or update an existing contact.
• CONTACT_NUMBER, TITLE, JOB_TITLE, JOB_TITLE_CODE, DEPARTMENT, DEPARTMENT_CODE — the descriptive contact attributes written to HZ_ORG_CONTACTS.
• RELATIONSHIP_TYPE, RELATIONSHIP_CODE, START_DATE, END_DATE, REL_COMMENTS — the relationship attributes written to HZ_RELATIONSHIPS.
• DECISION_MAKER_FLAG, REFERENCE_USE_FLAG — contact-role indicators.
• INTERFACE_STATUS, ERROR_ID, DQM_ACTION_FLAG, DUP_WITHIN_INT_FLAG — processing outcome and data-quality control.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, LAST_UPDATE_DATE, CREATED_BY — standard EBS concurrency and audit columns.
• Twenty ATTRIBUTE columns (ATTRIBUTE1–ATTRIBUTE20) with ATTRIBUTE_CATEGORY — the DFF segment for extensibility.

Common Use Cases and Queries

Typical uses include auditing a batch before submission, diagnosing rows that failed validation, and reconciling staged versus loaded contacts. A common pre-load check inspects queued rows against the batch:

SELECT i.batch_id, i.contact_orig_system, i.contact_orig_system_reference, i.insert_update_flag, i.interface_status FROM hz_imp_contacts_int i WHERE i.batch_id = :p_batch_id;

Error triage filters on the status/error columns, optionally joining the base table to confirm whether a valid row was applied:

SELECT i.* FROM hz_imp_contacts_int i WHERE i.interface_status = 'ERROR';

Reconciliation joins the unique business key to HZ_ORG_CONTACTS to detect staged records missing from the target. Reporting commonly counts staged versus loaded contacts per source system, grouped by batch and origin.

Related Objects

• HZ_IMP_BATCH_SUMMARY — parent batch control; joined via HZ_IMP_CONTACTS_INT.BATCH_ID = HZ_IMP_BATCH_SUMMARY.BATCH_ID.
• HZ_PARTIES — the primary party base table updated from staged party identity columns.
• HZ_RELATIONSHIPS — receives relationship-type rows from this interface.
• HZ_ORG_CONTACTS — receives the descriptive contact attributes.
• HZ_IMP_CONTACT_POINTS_INT — companion interface table staged within the same batch.
• HZ_IMP_FAILURES / HZ_IMP_ERRORS — error repository for rejected rows.
• HZ_IMP_PARTIES_INT — sibling party interface table processed in the same TCA load cycle.

All of these are accessed through Oracle Receivables and the TCA contact import process, making HZ_IMP_CONTACTS_INT the operative staging surface for contact and relationship loads.