Search Results ss_appint_id

Overview

The IGS_SS_AD_APPINT_STG table is a staging table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (iGrants) schema. Its primary role is to temporarily hold applicant intent details submitted as part of a self-service admission application process. As a staging table, it functions as an intermediate data store, typically used to validate, process, and subsequently migrate clean data into permanent transactional tables. This object is integral to the student administration and admissions modules, facilitating the capture of an applicant's declared academic or enrollment intentions during the application lifecycle.

Key Information Stored

The table's structure is designed to capture the core relationship between an application and an applicant's stated intent, along with standard audit information. The key columns include:

• SS_APPINT_ID (NUMBER): The primary key, serving as a unique identifier for each intent record staged.
• SS_ADM_APPL_ID (NUMBER): A foreign key that uniquely links the intent record to a specific self-service admission application stored in the related staging table.
• INTENT_TYPE_ID (NUMBER): A foreign key referencing a code table, which stores the specific type of intent declared by the applicant (e.g., full-time, part-time, a specific program intent).
• Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): These columns track the user and timestamp for the creation and last update of each record, enforcing data governance.

Common Use Cases and Queries

This table is central to operations involving the batch processing of self-service application data. Common use cases include ETL (Extract, Transform, Load) jobs that transfer data from online forms, data validation routines executed before moving records to production tables, and generating interim reports on applicant intentions during an admission cycle. A fundamental query to retrieve staged intent data, often used for validation or reporting, is:

SELECT appint.SS_APPINT_ID,
       appint.SS_ADM_APPL_ID,
       appint.INTENT_TYPE_ID,
       code.MEANING AS INTENT_TYPE
FROM IGS.IGS_SS_AD_APPINT_STG appint,
     FND_LOOKUP_VALUES code
WHERE code.LOOKUP_TYPE = 'IGS_AD_INTENT_TYPE' -- Example lookup type
  AND code.LOOKUP_CODE = appint.INTENT_TYPE_ID
  AND appint.CREATION_DATE > TRUNC(SYSDATE-1);

This pattern joins the intent type ID to a code lookup table for meaningful descriptions.

Related Objects

The IGS_SS_AD_APPINT_STG table has defined relationships with other key staging and reference tables in the IGS schema, as documented in its foreign key constraints:

• IGS_SS_ADM_APPL_STG: This is the primary parent staging table for self-service admission applications. The relationship is established via the SS_ADM_APPL_ID column in IGS_SS_AD_APPINT_STG, which references the corresponding application ID in IGS_SS_ADM_APPL_STG. This ensures every intent record is associated with a valid application.
• IGS_AD_CODE_CLASSES: This table (or a similar code table) houses the valid list of intent types. The INTENT_TYPE_ID column in the staging table references this object to maintain data integrity for the applicant's declared intent.

Furthermore, the table is referenced by the APPS synonym IGS_SS_AD_APPINT_STG, which provides a public access point for other EBS components and custom code within the application context.