Results for “interface_status”

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

Overview

HZ_IMP_CONTACTROLES_INT is a TCA (Trading Community Architecture) interface table owned by the AR schema in Oracle E-Business Suite. It serves as the staging area for contact role assignments that are loaded into the HZ_ORG_CONTACT_ROLES base table through the TCA party import and batch processing framework. In release 12.1.1 and 12.2.2, this table functions as a transient landing zone: records are inserted by external sources or feeder programs, validated and processed by concurrent import programs, and then removed or archived once the roles are successfully created in the production TCA model.

This object is best understood as a satellite-leaning entity from a Data Vault modeling perspective. It carries descriptive context about contact role associations plus processing metadata, and its only documented foreign key points to HZ_IMP_BATCH_SUMMARY via BATCH_ID. The design suggests it is a dependent, batch-scoped staging construct rather than an independent hub or an associative link.

Key Information Stored

The table contains 19 documented columns, with the following being most significant:

• BATCH_ID — The foreign key to HZ_IMP_BATCH_SUMMARY; groups interface rows into a processing batch and drives concurrent program execution.
• CONTACT_ORIG_SYSTEM / CONTACT_ORIG_SYSTEM_REFERENCE — The source system identifier and the unique key of the contact in that system, used to resolve the target contact in TCA.
• SUB_ORIG_SYSTEM / SUB_ORIG_SYSTEM_REFERENCE — The originating system and reference for the subject party (organization or person) to which the contact role applies.
• ROLE_TYPE — The role being assigned (for example, a contact role lookup value), which is the core business attribute of the interface row.
• INSERT_UPDATE_FLAG — Indicates whether the row should create a new role or update an existing one.
• INTERFACE_STATUS — Tracks processing state (new, in progress, error, complete).
• ERROR_ID — Links to the error repository when validation fails.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns for row provenance.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY_MODULE — Concurrent program and module context identifying which request and program inserted or last processed the row.

There is no documented surrogate primary key or unique index; the combination of BATCH_ID plus source system references and ROLE_TYPE functions as the practical business key candidate for deduplication.

Common Use Cases and Queries

Typical scenarios include monitoring batch load status, diagnosing import errors, and validating source data before running the TCA Contact Role import program. A common query counts interface rows by status for a given batch:

• SELECT INTERFACE_STATUS, COUNT(*) FROM HZ_IMP_CONTACTROLES_INT WHERE BATCH_ID = :batch_id GROUP BY INTERFACE_STATUS;
• SELECT i.* FROM HZ_IMP_CONTACTROLES_INT i JOIN HZ_IMP_BATCH_SUMMARY b ON i.BATCH_ID = b.BATCH_ID WHERE i.INTERFACE_STATUS = 'ERROR';
• SELECT * FROM HZ_IMP_CONTACTROLES_INT WHERE CONTACT_ORIG_SYSTEM = :src AND CONTACT_ORIG_SYSTEM_REFERENCE = :ref;

Reporting use cases include pre-load reconciliation of contact roles from an external CRM, audit trails tracing which concurrent request loaded each role, and error-rate dashboards keyed on BATCH_ID and ERROR_ID.

Related Objects

• HZ_IMP_BATCH_SUMMARY — Parent batch control table; join on HZ_IMP_CONTACTROLES_INT.BATCH_ID = HZ_IMP_BATCH_SUMMARY.BATCH_ID.
• HZ_ORG_CONTACT_ROLES — The destination TCA table to which validated rows are migrated.
• HZ_IMP_ERRORS / error repository tables — Referenced through ERROR_ID to record validation failures.
• TCA party import concurrent programs — The processing engine that consumes rows using BATCH_ID, REQUEST_ID, and PROGRAM_ID.
• HZ_IMP_CONTACTS_INT, HZ_IMP_ORGS_INT and other interface tables — Sibling staging tables sharing the same BATCH_ID batch framework.
• FND_CONCURRENT_REQUESTS — Join on REQUEST_ID to identify the concurrent program run that inserted or processed rows.