Results for “special_interest_type_id”

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

Overview

The IGS_SS_AD_SPLINT_STG table is a staging object within the Oracle E-Business Suite IGS (Student System) product family. In ETRM 12.1.1 and 12.2.2 it is classified as obsolete and is documented as not implemented in the reference database, though its definition remains catalogued for historical and upgrade-verification purposes. Its stated purpose is to hold special-interest selections captured during a self-service admission application, prior to that data being validated, transformed, and promoted into the permanent student records structures. In an EBS deployment the table therefore acts as a transient landing area for web-collected admission attributes rather than an operational master table.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is best modelled as a link. It records an association between an admission application and a coded special-interest type, rather than serving as a descriptive satellite for either of those entities or as a self-contained hub. This classification is a modelling suggestion based on the two documented foreign key relationships; it should not be treated as a physical install-time designation.

Key Information Stored

The documented physical schema comprises eight columns owned by IGS. The most significant are:

• SS_SPLINT_ID — the surrogate primary key, enforced through the unique index IGS_SS_AD_SPLINT_STG_PK. It uniquely identifies each staged special-interest row.
• SS_ADM_APPL_ID — the foreign key to IGS_SS_ADM_APPL_STG, linking the interest entry to its parent staged admission application.
• SPECIAL_INTEREST_TYPE_ID — the foreign key to IGS_AD_CODE_CLASSES, supplying the coded special-interest category selected by the applicant.
• CREATED_BY / CREATION_DATE — standard WHO audit columns capturing the inserting user and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns capturing the last modifying user, timestamp, and login session.

The only documented unique index is the primary key on SS_SPLINT_ID; no separate composite business-key candidate is documented, meaning uniqueness of application-plus-interest-type is not enforced at the database level in the catalogued definition.

Common Use Cases and Queries

Because the table is obsolete and not implemented, practical queries are largely confined to historical data inspection, upgrade remediation, and data-migration validation on legacy systems that still carry the staging data. A typical join retrieves each interest together with its application context:

• Joining to IGS_SS_ADM_APPL_STG on SS_ADM_APPL_ID to enumerate interests for a given application.
• Joining to IGS_AD_CODE_CLASSES on SPECIAL_INTEREST_TYPE_ID to resolve coded values into readable descriptors.
• Audit-oriented filtering on CREATION_DATE or LAST_UPDATE_DATE to isolate rows staged within a processing window.
• Reconciliation counts grouped by SS_ADM_APPL_ID to detect applications with multiple or zero special-interest rows.

A representative pattern is: select from IGS_SS_AD_SPLINT_STG joined to IGS_SS_ADM_APPL_STG on the application identifier, then to IGS_AD_CODE_CLASSES on the interest type, filtering by creation date range for a reporting extract.

Related Objects

The following objects are the most significant in relation to this table, based on the documented foreign key relationships:

• IGS_SS_ADM_APPL_STG — referenced via SS_ADM_APPL_ID; the parent staging table for the self-service admission application.
• IGS_AD_CODE_CLASSES — referenced via SPECIAL_INTEREST_TYPE_ID; provides valid coded values for special-interest types.
• IGS_SS_AD_SPLINT_STG_PK — the unique index that defines the primary key on SS_SPLINT_ID.
• The downstream admission processing and person/student record interfaces that consume staged application data, including any concurrent programs promoting staged rows into permanent IGS tables.

Because the object is obsolete and not implemented, dependent objects are limited, and any integration should confirm availability before reference.