Search Results igs_ad_interface_ctl




Overview
Explore in AI Chat

Overview

The IGS_AD_INTERFACE_CTL table is a core data object within the Oracle E-Business Suite Student System (IGS), specifically designed for the admissions module. Its primary role is to function as a control and audit table, storing critical metadata for each execution of an admissions data import process. When external admissions data is loaded into the system via an interface, this table records the run details, providing a traceable record of the import session. It is important to note that, as per the provided ETRM documentation, the Student System (IGS) is marked as obsolete. Furthermore, the documentation indicates this specific table was "Not implemented in this database," suggesting it may exist in the data model but was not actively used in some deployments.

Key Information Stored

The table's structure is centered around uniquely identifying and characterizing an import run. Its primary key, INTERFACE_RUN_ID, serves as the unique identifier for each import session. The table holds foreign keys that link the import run to essential configuration and batch data. The MATCH_SET_ID column references a matching rule set (IGS_PE_MATCH_SETS_ALL) used to identify and merge duplicate person records during the import. The SOURCE_TYPE_ID column references the source system (IGS_PE_SRC_TYPES_ALL) from which the admissions data originated. Finally, the BATCH_ID column links to a specific import batch (IGS_AD_IMP_BATCH_DET), grouping individual records processed in that run. Collectively, these columns allow administrators to answer what was imported, from where, using which rules, and when.

Common Use Cases and Queries

The primary use case for this table is auditing and troubleshooting the admissions data import lifecycle. System administrators would query it to generate reports on interface execution history, investigate failed imports, or reconcile data loads. A common query pattern would involve joining to its referenced tables to get descriptive information about the run. For example, to list recent import runs with their source and match set details, one might use a query such as:

  • SELECT ctl.INTERFACE_RUN_ID, src.SOURCE_TYPE, ms.MATCH_SET_NAME, ctl.CREATION_DATE FROM IGS_AD_INTERFACE_CTL ctl JOIN IGS_PE_SRC_TYPES_ALL src ON ctl.SOURCE_TYPE_ID = src.SOURCE_TYPE_ID JOIN IGS_PE_MATCH_SETS_ALL ms ON ctl.MATCH_SET_ID = ms.MATCH_SET_ID ORDER BY ctl.CREATION_DATE DESC;

Another critical use case is purging or archiving old interface data, where this table would be a key control point for identifying runs eligible for cleanup based on their creation date or status.

Related Objects

The IGS_AD_INTERFACE_CTL table has defined relationships with several other tables in the Student System, as documented by its foreign keys. These relationships are fundamental to understanding the data flow during an import.

  • IGS_PE_MATCH_SETS_ALL: Joined via IGS_AD_INTERFACE_CTL.MATCH_SET_ID. This relationship specifies the set of matching rules applied to person records during the import session.
  • IGS_PE_SRC_TYPES_ALL: Joined via IGS_AD_INTERFACE_CTL.SOURCE_TYPE_ID. This identifies the external source system (e.g., a specific application portal or feeder system) from which the admissions data was extracted.
  • IGS_AD_IMP_BATCH_DET: Joined via IGS_AD_INTERFACE_CTL.BATCH_ID. This links the control record to the detailed batch header, which would further relate to the individual applicant records (likely in a table such as IGS_AD_INTERFACE_ALL) processed during that run.