Search Results igs_or_inst_int

Overview

The table IGS.IGS_OR_INST_INT belongs to the Oracle E-Business Suite Student System (IGS) product family and is documented as describing Institution Interface Details. It serves as the staging and interface repository through which institution records are loaded, validated, and reconciled into the Oracle Student System institution master data. In Oracle EBS 12.1.1 and 12.2.2 the object is shipped with a VALID status in the IGS schema and comprises 63 documented columns in the ETRM 12.1.1 physical schema.

The table is the persistent landing structure for inbound institution data feeds. Each row represents a single institution record presented for interface processing, carrying both the incoming descriptive attributes and the processing control columns (batch identity, status, error information, and concurrent request auditing) that the interface program uses to accept or reject the record.

From a Data Vault modeling perspective, the mined relationship metadata classifies this object as standalone. Heuristically this suggests modeling IGS_OR_INST_INT as a hub-like integration entity keyed on the interface identifier, with no enforced foreign-key dependencies to surrounding hubs or links within the shipped schema. This classification is a modeling suggestion derived from the documented FK structure rather than a declared constraint.

Key Information Stored

The primary key of the table is defined by the unique index IGS_OR_INST_INT_PK on the single column INTERFACE_ID. This is the only documented business-key candidate; there are no additional unique indexes, so INTERFACE_ID is both the surrogate identifier and the sole documented uniqueness guarantee. The most significant columns fall into four groups.

• Processing control: INTERFACE_ID (primary key), BATCH_ID (groups rows belonging to one interface run), STATUS (row-level disposition), ERROR_CODE and ERROR_TEXT (validation failure detail).
• Institution identity: NEW_INSTITUTION_CD and EXST_INSTITUTION_CD (incoming versus existing institution code, supporting insert-versus-update matching), NAME, ALT_ID_TYPE and ALT_ID_VALUE (alternate identifier pairs).
• Institution attributes: INSTITUTION_STATUS, LOCAL_INSTITUTION_IND, OS_IND, GOVT_INSTITUTION_CD, INSTITUTION_TYPE, INST_CONTROL_TYPE, INST_PRIORITY_CD and EPS_CODE.
• Academic and contact detail: ADV_STUDIES_CLASSES, HONORS_CLASSES, CLASS_SIZE, PERCENT_PLAN_HIGHER_EDU, SEC_SCHOOL_LOCATION_ID, PHONE_COUNTRY, PHONE_AREA, PHONE_NUMBER and ACCOUNT_NUMBER.
• Source and audit: DATA_SOURCE_ID and DATA_SOURCE_VALUE (origin of the feed), ATTRIBUTE_CATEGORY with ATTRIBUTE1–ATTRIBUTE24 (descriptive flexfield segments), CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The dominant use case is monitoring and troubleshooting institution interface loads. Batch-level reconciliation counts accepted versus rejected records, while row-level diagnostics retrieve the failure reason for a specific institution code.

• Batch status summary: SELECT STATUS, COUNT(*) FROM IGS.IGS_OR_INST_INT WHERE BATCH_ID = :batch_id GROUP BY STATUS;
• Error retrieval: SELECT INTERFACE_ID, NEW_INSTITUTION_CD, EXST_INSTITUTION_CD, ERROR_CODE, ERROR_TEXT FROM IGS.IGS_OR_INST_INT WHERE STATUS = 'ERROR';
• Concurrent request traceability: filter on REQUEST_ID or PROGRAM_ID to attribute rows to the submitting concurrent program and its run window using PROGRAM_UPDATE_DATE.
• Duplicate detection: compare NEW_INSTITUTION_CD against EXST_INSTITUTION_CD to identify records intended as updates rather than creations.
• Reporting: join interface rows to the institution master to confirm which staged records produced permanent institution rows, and use DATA_SOURCE_ID to report on feed provenance.

Related Objects

The documented metadata assigns no enforced foreign keys, consistent with the standalone Data Vault classification. The significant related objects are therefore those that participate in the interface lifecycle for institution data in the IGS schema.

• IGS_OR_INSTITUTION_ALL — the institution master to which validated rows are applied; linkage is by institution code (NEW_INSTITUTION_CD / EXST_INSTITUTION_CD) rather than a declared FK.
• IGS_OR_INST_INT_PK — the primary key index on INTERFACE_ID, enforcing row uniqueness.
• Interface validation and import programs — concurrent programs in the IGS application that select rows by BATCH_ID and STATUS, write ERROR_CODE and ERROR_TEXT, and update STATUS.
• FND_CONCURRENT_REQUESTS — joinable on REQUEST_ID to reconcile interface rows with their submitting concurrent request.
• FND_APPLICATION / FND_PROGRAM — joinable on PROGRAM_APPLICATION_ID and PROGRAM_ID to resolve the owning program metadata.
• FND_FLEX_VALUES / descriptive flexfield definitions — resolve ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE24.