Search Results igs_in_appl_course




Overview
Explore in AI Chat

Overview

The IGS_IN_APPL_COURSE table is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. As per the official ETRM documentation, its core function was to store information about the specific courses an applicant expressed interest in as part of an enquiry application process. This table played a role in managing prospective student data prior to a formal application. Critically, the metadata explicitly labels this entity as "Obsolete" and notes it was "Not implemented in this database" for the documented version. This indicates that while the table's structure was defined, it was not actively used in production deployments of EBS 12.1.1 or 12.2.2, rendering it a historical artifact of the system's data model.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each course interest record for an enquiry. The key columns are PERSON_ID, ENQUIRY_APPL_NUMBER, VERSION_NUMBER, and COURSE_CD. This design links a course of interest directly to a specific version of an individual's enquiry application. Based on the foreign key relationships documented, the table also included columns for ATTENDANCE_MODE and ATTENDANCE_TYPE. These fields would have stored the applicant's preferred method (e.g., full-time, part-time) and type (e.g., on-campus, distance) of attendance for the specified course, referencing standardized code tables for validation.

Common Use Cases and Queries

Given its obsolete and unimplemented status, there are no active operational or reporting use cases for this table in standard EBS 12.1.1 or 12.2.2 environments. Its primary relevance would be for technical consultants or DBAs performing data model analysis or system upgrades to understand legacy structures. A sample analytical query, for historical context only, might involve joining to person and course tables to list all course interests for a given enquiry. However, any such SQL would be purely illustrative, as no data would exist in a standard system.

-- Illustrative pattern only (Table is Obsolete/Not Implemented)
SELECT iap.person_id,
       iap.enquiry_appl_number,
       iap.course_cd,
       mo.attendance_mode,
       ty.attendance_type
FROM   igs_in_appl_course iap,
       igs_en_atd_mode_all mo,
       igs_en_atd_type_all ty
WHERE  iap.attendance_mode = mo.attendance_mode
AND    iap.attendance_type = ty.attendance_type
AND    iap.person_id = :p_person_id;

Related Objects

The ETRM documentation specifies two foreign key relationships where IGS_IN_APPL_COURSE references other code tables for data integrity. These relationships are the only concretely documented links for this object.

  • IGS_EN_ATD_MODE_ALL: The ATTENDANCE_MODE column in IGS_IN_APPL_COURSE references this table to validate the applicant's preferred attendance mode (e.g., full-time).
  • IGS_EN_ATD_TYPE_ALL: The ATTENDANCE_TYPE column in IGS_IN_APPL_COURSE references this table to validate the applicant's preferred attendance type (e.g., on-campus).

As the parent entity for the enquiry application itself is not listed in the provided metadata, the primary key columns (PERSON_ID, ENQUIRY_APPL_NUMBER, VERSION_NUMBER) likely referenced a core enquiry application header table, but this relationship is not formally documented in the excerpt provided.