Search Results igs_ad_spltal_int




Overview
Explore in AI Chat

Overview

The IGS_AD_SPLTAL_INT table is an interface (staging) table within the IGS — Student System product family in Oracle EBS 12.1.1 and 12.2.2. It holds applicant special talents details collected during the admissions cycle, acting as a temporary landing area for talent-related records before they are validated and transferred into the base admissions tables. In the Oracle E-Business Suite higher-education data model, the "_INT" suffix consistently denotes an open interface table: rows are populated by external sources, concurrent programs validate and process them, and error columns capture rejections for correction and resubmission.

Column names such as REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, LAST_UPDATE_LOGIN, and INTERFACE_RUN_ID confirm the standard EBS interface pattern, where each row is stamped with the concurrent request and program that loaded it. Because the table carries no documented parent relationships beyond its link to the applicant interface, the heuristic Data Vault classification mined from the foreign-key structure is standalone. In modeling terms, this suggests treating IGS_AD_SPLTAL_INT primarily as a satellite-like staging object, with INTERFACE_SPLTAL_ID serving as the degenerate hub key and the attributes describing talent characteristics and processing status. It is a transient object rather than a persistent analytical entity.

Key Information Stored

The documented physical schema for 12.1.1 contains 19 columns. The most significant are:

  • INTERFACE_SPLTAL_ID — surrogate primary key and the sole unique business-key candidate, enforced by the unique index IGS_AD_SPLTAL_INT_ALL_U1 and the constraint IGS_AD_SPLTAL_INT_PK.
  • INTERFACE_APPL_ID — foreign key to IGS_AD_APL_INT, tying each talent record to its parent applicant interface row.
  • SPECIAL_TALENT_TYPE_ID — identifies the category or type of special talent being declared.
  • PERSON_ID — the person (applicant) to whom the talent detail belongs.
  • ADMISSION_APPL_NUMBER and ADMISSION_APPLICATION_TYPE — the admissions application reference and its type, supporting matching during import.
  • STATUS — processing state of the interface row (for example, whether it is pending, validated, or errored).
  • ERROR_CODE and ERROR_TEXT — machine-readable and human-readable diagnostics populated when validation fails.
  • INTERFACE_RUN_ID — identifies the specific interface run that loaded the row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last modified the record and when.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request and program that processed the row.

Common Use Cases and Queries

Typical usage centers on loading, validating, and reconciling applicant talent data. A common pattern retrieves all outstanding error rows for correction:

  • SELECT interface_spltal_id, interface_appl_id, special_talent_type_id, error_code, error_text FROM igs.igs_ad_spltal_int WHERE status = 'ERROR';
  • Joining to the parent applicant interface to reconstruct complete applicant context: SELECT s.*, a.* FROM igs.igs_ad_spltal_int s, igs.igs_ad_apl_int a WHERE s.interface_appl_id = a.interface_appl_id;
  • Filtering by loading run to audit throughput: SELECT interface_run_id, COUNT(*) FROM igs.igs_ad_spltal_int GROUP BY interface_run_id;
  • Reporting talent distributions by type once successfully transferred: counting rows per special_talent_type_id.

Interface tables should be truncated or purged after successful processing, so reporting on them reflects only the current or most recent load cycle.

Related Objects

The primary documented relationship is the foreign key from IGS_AD_SPLTAL_INT.INTERFACE_APPL_ID to IGS_AD_APL_INT, the applicant interface table, which supplies the applicant-level context for each talent record. Both are populated and processed by IGS admissions interface concurrent programs, and validated rows are subsequently written to the permanent applicant special talents tables within the IGS schema. The dependencies to be aware of when querying or purging this table are the parent IGS_AD_APL_INT row and the associated concurrent request and program records referenced through REQUEST_ID and PROGRAM_ID.