Results for “igs_ad_spl_interests”

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

Overview

IGS_AD_SPL_INTERESTS is a table within the Oracle E-Business Suite Student System (product code IGS), a module that is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. The table stores special interests details associated with admission applications, providing a mechanism to record the specific interests declared by applicants during the admissions cycle. Its granularity is one row per declared special interest, tied to a person and an admission application.

The ETRM metadata explicitly notes "Not implemented in this database," meaning the object may not be physically present or populated in a given environment; verification against the actual instance is required before relying on it for reporting or integration work. From a Data Vault modeling perspective, the mined relationship structure classifies this object as a link: it sits between the application/person entity (IGS_AD_APPL_ALL) and the code/classification reference entity (IGS_AD_CODE_CLASSES), capturing the association between an applicant and a special interest type. This classification is a heuristic suggestion rather than an Oracle-prescribed design.

Key Information Stored

The documented physical schema lists fifteen columns. The most significant are summarized below.

• SPL_INTEREST_ID — Surrogate primary key, enforced by the IGS_AD_SPL_INTERESTS_PK constraint and the unique index IGS_AD_SPL_INTERESTS_U1. This is the technical identifier for each special interest record.
• PERSON_ID — Foreign key to IGS_AD_APPL_ALL, identifying the applicant/person to whom the interest belongs. Part of the business-key candidate.
• ADMISSION_APPL_NUMBER — Foreign key to IGS_AD_APPL_ALL, identifying the specific admission application. Also part of the business-key candidate.
• SPECIAL_INTEREST_TYPE_ID — Foreign key to IGS_AD_CODE_CLASSES, providing the coded value that classifies the special interest. Completes the business-key candidate.
• NOMINATED_COURSE_CD — The course code nominated by the applicant in connection with the declared interest.
• SEQUENCE_NUMBER — Ordering attribute used when multiple interests exist for the same application or person.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — Identifiers linking the record to the application and program context within the Student System's concurrent program framework.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, and PROGRAM_UPDATE_DATE provide standard WHO-column auditing and concurrent request traceability.

The unique index IGS_AD_SPL_INTERESTS_U2 on (ADMISSION_APPL_NUMBER, PERSON_ID, SPECIAL_INTEREST_TYPE_ID) is the documented business-key candidate, meaning a given applicant on a given application may record each special interest type only once.

Common Use Cases and Queries

Typical reporting use cases include identifying applicant interests by type for admissions funnel analysis, listing all interests associated with a specific application, and resolving special interest descriptions via IGS_AD_CODE_CLASSES. A representative query pattern joining the documented foreign keys is:

• Join IGS_AD_SPL_INTERESTS to IGS_AD_APPL_ALL on PERSON_ID and ADMISSION_APPL_NUMBER to retrieve applicant context.
• Join to IGS_AD_CODE_CLASSES on SPECIAL_INTEREST_TYPE_ID to decode the interest classification into a meaningful description.
• Filter by SPECIAL_INTEREST_TYPE_ID or aggregate counts grouped by interest type for trend reporting.
• Order by SEQUENCE_NUMBER where ordering of multiple interests is meaningful.

Because the module is obsolete, such queries are relevant to historical data migration, legacy admissions reporting, or archival extracts rather than active functional processing.

Related Objects

The documented foreign keys and surrounding admissions schema establish the principal relationships for this object.

• IGS_AD_APPL_ALL — Referenced by PERSON_ID and ADMISSION_APPL_NUMBER; the primary parent entity for admission applications.
• IGS_AD_CODE_CLASSES — Referenced by SPECIAL_INTEREST_TYPE_ID; the reference table holding code classifications for special interest types.
• IGS_AD_SPL_INTERESTS_PK — Primary key constraint defining the surrogate identifier.
• IGS_AD_SPL_INTERESTS_U1 / IGS_AD_SPL_INTERESTS_U2 — Unique indexes supporting surrogate and business-key uniqueness respectively.

Beyond these documented relationships, consumer objects in a full Student System implementation would typically include admissions inquiry and application views that surface special interest data, though such objects are outside the scope of the provided metadata. Consultants should validate actual dependencies against the target instance, given the obsolete status of the IGS module.