Results for “igs_ad_interface_ctl”

42 results




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

Overview

The IGS_AD_INTERFACE_CTL table resides in the IGS (Student System) schema and serves as the control and audit record for admissions data import runs. When external admissions data is loaded into Oracle E-Business Suite, whether sourced from legacy systems, third-party recruitment platforms, or flat-file transfers, this table captures the header-level identifiers that govern each import execution. It acts as the anchor point linking a source type, an import batch, and a participant matching set to a single interface run, thereby providing the transactional context required for downstream processing and reconciliation within the Student System.

From a Data Vault modeling perspective, the FK structure heuristic classifies IGS_AD_INTERFACE_CTL as a link entity. It does not function as a standalone hub or a descriptive satellite; rather, it associates multiple business entities, namely source type, match set, and import batch, through a single surrogate identifier. This classification is a modeling suggestion based on the foreign key topology rather than a documented architectural statement.

Key Information Stored

The table contains fourteen documented columns. The most significant are summarized below.

Common Use Cases and Queries

The table is typically queried to audit admissions import activity, diagnose failed runs, or reconcile imported prospect volumes against source systems. A representative query joining the control record to its parent batch and source type follows:

  • SELECT c.interface_run_id, s.source_type_name, b.batch_id, c.status, c.request_id FROM igs.igs_ad_interface_ctl c, igs.igs_pe_src_types_all s, igs.igs_ad_imp_batch_det b WHERE c.source_type_id = s.source_type_id AND c.batch_id = b.batch_id AND c.status = 'ERROR';
  • Filtering by CREATION_DATE range supports daily or weekly import volume reporting.
  • Joining REQUEST_ID to FND_CONCURRENT_REQUESTS links each run to its concurrent program output and log files.
  • Grouping by SOURCE_TYPE_ID allows analysts to compare import volumes across recruitment channels.

Related Objects

The most significant related objects are the three foreign key targets plus the concurrent request infrastructure and downstream processing tables.

  • IGS_PE_MATCH_SETS_ALL — joined on MATCH_SET_ID; defines the matching rules applied to imported participants.
  • IGS_PE_SRC_TYPES_ALL — joined on SOURCE_TYPE_ID; classifies the admissions data source.
  • IGS_AD_IMP_BATCH_DET — joined on BATCH_ID; holds batch-level import details.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID for concurrent program auditing.
  • IGS_AD_INTERFACE_CTL_PK — the primary key constraint defining the unique interface run identity.