Search Results igs_ad_app_intent_pk

Overview

The IGS_AD_APP_INTENT table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS), specifically designed to manage applicant intent details. Its primary role is to store and track the specific intentions declared by an individual during the admissions application process, such as their desired program of study, entry term, or study mode. This data is critical for application evaluation, program planning, and enrollment forecasting. It is important to note that the IGS Student System module is marked as "Obsolete" in the provided ETRM documentation, indicating that while the table exists in the data model for implementations on versions 12.1.1 and 12.2.2, its use and support may be deprecated in favor of newer functionality or modules.

Key Information Stored

The table's structure is centered on linking an applicant to their declared intent, which is categorized using a controlled code list. The most significant columns include APP_INTENT_ID, which serves as the unique primary key for each intent record. The PERSON_ID and ADMISSION_APPL_NUMBER columns together form a composite foreign key that uniquely identifies the parent application record in the IGS_AD_APPL_ALL table, ensuring each intent is tied to a specific applicant and application instance. The INTENT_TYPE_ID column holds a foreign key reference to the IGS_AD_CODE_CLASSES table, which contains the valid classifications and codes for the types of intent an applicant can specify (e.g., primary program intent, campus preference).

Common Use Cases and Queries

This table is primarily accessed for reporting and validation during the admissions lifecycle. Common operational use cases include generating lists of applicants by their intended program for departmental review, validating that an applicant's declared intent aligns with the applied-for admission category, and supporting communication workflows based on intent type. A typical query would join IGS_AD_APP_INTENT to the main application and person tables to create a applicant intent summary report.

SELECT appl.person_id,
       appl.admission_appl_number,
       code.meaning AS intent_type,
       app_int.creation_date
FROM igs_ad_app_intent app_int
JOIN igs_ad_appl_all appl
  ON app_int.person_id = appl.person_id
 AND app_int.admission_appl_number = appl.admission_appl_number
JOIN igs_ad_code_classes code
  ON app_int.intent_type_id = code.code_id
WHERE appl.adm_appl_status = 'SUBMITTED';

Related Objects

The IGS_AD_APP_INTENT table has defined relationships with other key tables in the Student System schema, as documented in the ETRM metadata. Its primary dependencies are:

• IGS_AD_APPL_ALL: This is the primary parent table for application data. The IGS_AD_APP_INTENT table references it via a foreign key relationship on the composite columns (PERSON_ID, ADMISSION_APPL_NUMBER). This ensures every intent record is associated with a valid application.
• IGS_AD_CODE_CLASSES: This code lookup table provides the valid values for the INTENT_TYPE_ID column. The foreign key relationship maintains data integrity by restricting the intent type to predefined classifications within the system.

The table itself is defined with a primary key (IGS_AD_APP_INTENT_PK on APP_INTENT_ID) and unique constraints (IGS_AD_APP_INTENT_U1, U2) to enforce data uniqueness.