Search Results igs_ad_splint_int




Overview
Explore in AI Chat

Overview

IGS_AD_SPLINT_INT is an interface (staging) table within the Oracle E-Business Suite IGS – Student System product family. It holds applicant special interest details, serving as the transient landing area for records that describe the special interests declared by applicants during the admissions process. In the Oracle EBS architecture, "_INT" tables are conventionally populated by external feeds, inbound flat files, or batch processes and then validated and transferred into the corresponding base application tables by a concurrent program. This table therefore acts as the ingestion buffer between an external admissions source system and the core student/admissions data model.

The ETRM documentation explicitly flags this product as Obsolete and states that the object is Not implemented in this database, meaning it exists in the shipped schema definition but is not physically created or populated in the reference environment. The documented physical schema notes an owner of IGS and 19 columns. The heuristic Data Vault classification is standalone, which suggests, from a modeling perspective, that the table is not tightly integrated into the surrounding foreign-key network and may be treated as an independent staging construct rather than a true hub, link, or satellite. Where an integration staging table is not keyed into a surrounding referential web, a satellite-style wrapper around the interface run and applicant context is a reasonable modeling choice.

Key Information Stored

The primary key is defined by IGS_AD_SPLINT_INT_PK on the column INTERFACE_SPLINT_ID, which is the surrogate identifier for each staged row. A unique index, IGS_AD_SPLINT_INT_ALL_U1, is documented on the same column, identifying it as the principal business-key candidate.

The most significant columns include:

Common Use Cases and Queries

Typical use cases involve auditing inbound admissions feeds, diagnosing rejected rows, and reconciling counts between the source file and the base tables. A common query retrieves all failing rows for a run:

SELECT INTERFACE_SPLINT_ID, INTERFACE_APPL_ID, SPECIAL_INTEREST_TYPE_ID, ERROR_CODE, ERROR_TEXT FROM IGS_AD_SPLINT_INT WHERE INTERFACE_RUN_ID = :run_id AND STATUS = 'E';

A reconciliation pattern groups rows by run and status to confirm throughput:

SELECT INTERFACE_RUN_ID, STATUS, COUNT(*) FROM IGS_AD_SPLINT_INT GROUP BY INTERFACE_RUN_ID, STATUS;

Because the table is documented as not implemented, these patterns should be treated as reference designs rather than verified production queries.

Related Objects

Given the standalone classification, no foreign keys are documented. The most plausible dependencies, based on the documented column semantics, are:

As the product is obsolete, these relationships should be confirmed against the actual instance before reliance.