Search Results igs_ad_admde_int_all




Overview
Explore in AI Chat

Overview

IGS_AD_ADMDE_INT_ALL is a Student System (IGS) interface table in Oracle E-Business Suite, owned by the IGS schema. Its documented purpose is to hold application interface records for which an admission decision needs to be imported. In practice, it functions as a staging or inbound interface area: external sources—such as web admission portals, third-party recruitment systems, or legacy student systems—write candidate decision records here, and Oracle Student System processes (typically concurrent programs or APIs) consume the rows to create or update official admission decisions against applications.

The table carries a single documented primary key, IGS_AD_ADMDE_INT_PK, defined on the INTERFACE_MKDES_ID column, along with a unique index IGS_AD_ADMDE_INT_ALL_U1 on the same column. Because that unique key repeats the primary key, INTERFACE_MKDES_ID is the row-level surrogate identifier rather than an independent business key; the documented schema exposes no alternate unique business key. The ETRM metadata classifies the object, heuristically mined from its foreign-key structure, as standalone. In Data Vault terms this suggests modeling it as an isolated satellite-style staging entity—each row being a descriptive attribute set keyed by the interface identifier—rather than as a hub or link, since no enforcing foreign-key relationships are documented. The schema is version-stable across 12.1.1 and 12.2.2 with 29 documented columns.

Key Information Stored

Each row represents one decision to be imported for one applicant. The most significant columns fall into three groups.

Common Use Cases and Queries

Typical uses include monitoring inbound decision loads, diagnosing failed rows, and reconciling decisions against applications. A representative error-triage query is:

  • SELECT INTERFACE_MKDES_ID, ADMISSION_APPL_NUMBER, ERROR_CODE, ERROR_TEXT FROM IGS_AD_ADMDE_INT_ALL WHERE ERROR_CODE IS NOT NULL;
  • Batch throughput by run: SELECT INTERFACE_RUN_ID, BATCH_ID, COUNT(*) FROM IGS_AD_ADMDE_INT_ALL GROUP BY INTERFACE_RUN_ID, BATCH_ID;
  • Outcome distribution for a nominated course: filtering on NOMINATED_COURSE_CD, ADM_OUTCOME_STATUS and DECISION_DATE to report offers made or pending.
  • Stale-row detection: comparing CREATION_DATE against the last interface run to identify unprocessed decisions awaiting import.

Related Objects

Because the metadata documents no enforcing foreign keys, relationships are functional rather than declarative. Rows are joined to the person and application entities through PERSON_ID, ADMISSION_APPL_NUMBER and PROGRAM_APPLICATION_ID (IGS applicant/application tables, commonly accessed via the IGS admissions views), to program and course definitions via PROGRAM_ID and NOMINATED_COURSE_CD, and to decision and reason reference data via DECISION_MAKE_ID, DECISION_REASON_ID and PENDING_REASON_ID. Operational lineage ties the table to its interface run and batch parent objects through INTERFACE_RUN_ID and BATCH_ID, and to the concurrent manager through REQUEST_ID. Downstream, validated rows are consumed by the IGS admission decision import process, which posts accepted outcomes into the live decision tables and leaves rejected rows in place with ERROR_CODE and ERROR_TEXT populated for correction and resubmission.