Search Results igs_or_inst_con_int




Overview
Explore in AI Chat

Overview

IGS_OR_INST_CON_INT is a student system interface table in the Oracle E-Business Suite IGS (Student System) module, which Oracle classified as obsolete in later EBS releases. As the name indicates, the table holds interface-level institution contact details — the staging area used to capture contact records associated with an institution before they are validated, processed, and promoted into the production student system tables. The _INT suffix follows the standard Oracle interface-table convention, signaling that rows are transient staging data rather than permanent transactional records.

The ETRM metadata records a heuristic Data Vault classification of "standalone," meaning the mined foreign-key structure shows no enforced relationships to other tables. In Data Vault modeling terms, this suggests the object behaves more like a satellite or a self-contained staging entity than a hub or link; however, since no FK relationships were mined, that classification should be treated as a modeling suggestion rather than a definitive structural fact.

The table is documented as not implemented in the source database, which means it exists only in the ETRM documentation for release 12.1.1 and does not appear in the shipped schema of 12.1.1 or 12.2.2. Its presence in the metadata therefore reflects the historical Student System data model rather than an active object.

Key Information Stored

Per the documented physical schema (owner IGS, 41 columns), the most significant columns are:

  • INTERFACE_CONTACTS_ID — the surrogate primary key, unique across the table and defined by the IGS_OR_INST_CON_INT_PK unique index. This is the sole documented business-key candidate.
  • INTERFACE_ID — correlates the row to a parent interface batch or header, allowing contact records to be grouped and reprocessed together.
  • CONTACT_PARTY_ID — the party identifier for the institution contact, typically pointing to a person or organization party in TCA.
  • TITLE — the contact's honorific or job title used in correspondence.
  • MAIL_STOP — the internal mail stop or routing code for the contact.
  • REFERENCE — an external or legacy reference code for the contact.
  • EMAIL — the contact's electronic mail address.
  • ACTIVE — a flag indicating whether the contact record is currently active.
  • STATUS — the processing status of the interface row (e.g., pending, validated, errored).
  • ERROR_CODE and ERROR_TEXT — diagnostics populated when interface validation fails.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the standard concurrent program audit columns recording which request and program loaded or updated the row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the mandatory Oracle WHO columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard flexfield descriptive column set.

Common Use Cases and Queries

The principal use case is monitoring and debugging institution contact interface loads. A typical query retrieves failed rows for a specific concurrent request:

  • SELECT interface_contacts_id, interface_id, contact_party_id, email, error_code, error_text FROM igs_or_inst_con_int WHERE status = 'ERROR' AND request_id = :req_id;
  • Grouping by interface_id to count contacts per batch and assess completeness before promotion.
  • Joining to the concurrent request tables (FND_CONCURRENT_REQUESTS) on REQUEST_ID to identify the submitting program and completion timestamps.
  • Auditing rows by PROGRAM_APPLICATION_ID and PROGRAM_ID to determine which loader populated the staging set.

Reporting typically focuses on exception handling — counting rows with non-null ERROR_CODE, tracing CONTACT_PARTY_ID back to TCA for identity resolution, and verifying that ACTIVE and STATUS values are consistent before the data is transferred to production contact tables.

Related Objects

The metadata documents a standalone classification with no mined foreign keys, so relationships below are drawn from the interface-table pattern and the INTERFACE_ID/INTERFACE_CONTACTS_ID keys:

  • IGS_OR_INST_CON_INT_PK — the unique index enforcing the primary key on INTERFACE_CONTACTS_ID.
  • IGS_OR_INST_INT — the matching institution interface table, related through INTERFACE_ID.
  • IGS_OR_INST_CON — the production institution contact table that staged rows are promoted into.
  • HZ_PARTIES — the TCA party table referenced by CONTACT_PARTY_ID.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for load diagnostics.
  • FND_APPLICATION and FND_CONCURRENT_PROGRAMS — resolved from PROGRAM_APPLICATION_ID and PROGRAM_ID.