Search Results igs_uc_app_choices




Overview
Explore in AI Chat

Overview

The IGS_UC_APP_CHOICES table is a core data structure within the obsolete Student System (IGS) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is designed to manage the detailed relationship between university applicants and their specific course selections within the UCAS (Universities and Colleges Admissions Service) admissions framework. The table's primary role is to store an applicant's individual course choices and all associated offer details from the institution. Furthermore, it serves as a critical integration point, synchronizing data with external UCAS views named 'ivOffer' and 'ivStarC'. As a child table, it is dependent on the parent IGS_UC_APPLICANTS table, with records only being populated when the corresponding applicant record is present.

Key Information Stored

The table stores detailed transactional data for each course choice an applicant submits. Key columns include the unique system identifier APP_CHOICE_ID and the composite business key consisting of APP_NO, CHOICE_NO, and UCAS_CYCLE, which together uniquely identify a choice within an admissions cycle. Critical foreign key columns link to related data: APP_ID connects to the IGS_UC_APPLICANTS parent record, while a combination of SYSTEM_CODE, UCAS_PROGRAM_CODE, INSTITUTE_CODE, and CAMPUS links to the IGS_UC_CRSE_DETS table to define the specific course. Additional columns store the status of the choice, offer conditions (linked via CONDITION_CATEGORY and CONDITION_CODE to IGS_UC_OFFER_CONDS), and dates for key milestones in the application process for that choice.

Common Use Cases and Queries

This table is central to UCAS-related reporting and process management. Common use cases include generating lists of all choices for a specific applicant, tracking the status of offers across a course, and managing the synchronization of offer data with the external UCAS system. A fundamental query pattern involves joining to the applicant and course detail tables. For example, to retrieve all choices for a specific application number, one might use:

  • SELECT ac.* FROM igs_uc_app_choices ac, igs_uc_applicants a WHERE a.app_id = ac.app_id AND a.app_no = '<APPLICATION_NUMBER>';

Reporting often focuses on aggregating choice data by course, institute, or offer condition to analyze applicant trends and fulfillment rates.

Related Objects

The IGS_UC_APP_CHOICES table exists within a tightly coupled schema. Its primary parent is the IGS_UC_APPLICANTS table, linked via the APP_ID foreign key. It references the IGS_UC_CRSE_DETS table to obtain detailed course information and the IGS_UC_OFFER_CONDS table for condition definitions. Crucially, it acts as a parent table itself to IGS_UC_APP_CHO_CNDS, which holds further detailed condition records for a choice. As noted in the metadata, it is directly involved in data synchronization with the UCAS 'ivOffer' and 'ivStarC' views, indicating underlying database triggers or APIs facilitate this integration.