Search Results igs_ad_contacts_int_u1

Overview

IGS_AD_CONTACTS_INT_ALL is an interface staging table owned by the IGS schema within the Oracle E-Business Suite Student System (IGS) product family. As its name implies, the table serves as a transient landing area for contact detail records that are awaiting validation, de-duplication, and ultimate transfer into the Oracle Trading Community Architecture (TCA) registry. It is typically populated by concurrent programs or inbound integration loads and then processed so that email addresses, phone numbers, and related contact points become permanent entries in the HZ tables (principally HZ_CONTACT_POINTS).

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. Its dominant relationships hang off a parent business entity (the contact point registered in HZ_CONTACT_POINTS), and the table stores descriptive and status-oriented attributes about those contacts rather than acting as an associative link between multiple hubs. This classification should be treated as a modeling suggestion rather than a documented EBS fact.

Key Information Stored

The table carries 26 documented columns, all oriented toward staging contact information and tracking the outcome of each load attempt. The most operationally significant columns include:

• INTERFACE_CONTACTS_ID — the surrogate primary key, enforced by unique index IGS_AD_CONTACTS_INT_U1. This is the only documented unique key and therefore the sole guaranteed business-key candidate within the interface layer.
• ORG_ID — the operating unit / organization context, essential for multi-org reporting.
• INTERFACE_ID and INTERFACE_RUN_ID — identify the specific batch or interface run that staged the record, supporting restart and error-recovery logic.
• CONTACT_POINT_TYPE, EMAIL_ADDRESS, EMAIL_FORMAT — describe the contact point classification and email-specific attributes.
• PHONE_LINE_TYPE, PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION — the full telephone contact detail set.
• PRIMARY_FLAG and STATUS — indicate whether the contact is the primary one and its processing state (for example, pending, error, or complete).
• MATCH_IND, ERROR_CODE, DUP_CONTACT_POINT_ID — de-duplication and error diagnostics. DUP_CONTACT_POINT_ID is a foreign key to HZ_CONTACT_POINTS.
• CREATED_BY / CREATION_DATE and LAST_UPDATED_BY / LAST_UPDATE_DATE — standard EBS audit columns.

Common Use Cases and Queries

The most frequent requirement is reconciling interface rows against their target TCA contact points and identifying records that failed validation. A representative query retrieves unresolved batches for a given org:

• Select records by run: SELECT interface_contacts_id, email_address, phone_number, status, error_code FROM igs.igs_ad_contacts_int_all WHERE interface_run_id = :run_id AND status = 'ERROR';
• Join to TCA to confirm promotion: SELECT a.interface_contacts_id, a.dup_contact_point_id, h.contact_point_id FROM igs.igs_ad_contacts_int_all a, hz.contact_points h WHERE a.dup_contact_point_id = h.contact_point_id;
• De-duplication checks grouping on email and phone to detect potential duplicates before transfer.

Reporting scenarios include monitoring load success rates, auditing which reference data-created contacts, and troubleshooting ERROR_CODE distributions across interface runs. Because this is a staging table, purging completed rows is a standard housekeeping practice.

Related Objects

The table participates in a small but well-defined relationship set. The documented dependencies are:

• HZ_CONTACT_POINTS — referenced through DUP_CONTACT_POINT_ID; the authoritative TCA source for each contact point this interface row is meant to create or match.
• HZ_CONTACT_POINT_TYPES — supplies the lookup values behind CONTACT_POINT_TYPE, though not exposed as a formal FK here.
• HZ_PARTIES — the party master linked through contact point associations once records are promoted.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — referenced indirectly via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for diagnosing the load program execution.
• IGS_AD_CONTACTS_INT (and related interface-processing APIs/concurrent programs) — the sibling staging structures that share the same unique key convention.

These relationships confirm the table's role as a satellite-style staging area feeding the TCA contact registry rather than an independent master.