Search Results igs_uc_app_cho_cnds_u1

Overview

The IGS_UC_APP_CHO_CNDS table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (iGraduate) product family. It serves a critical function in the higher education admissions process by storing non-academic conditions associated with an applicant's course choices. These conditions are typically part of an offer made through the Universities and Colleges Admissions Service (UCAS) framework. The table acts as a transactional repository, tracking conditions such as health checks, financial guarantees, or other specific requirements that must be satisfied by the applicant, distinct from academic grades, for an offer to become unconditional.

Key Information Stored

The table's structure is designed to link conditions to specific application choices while maintaining auditability. The primary columns include the unique record identifier (APP_CHOICE_COND_ID) and the foreign key to the application choice (APP_CHOICE_ID), which was the user's search term. The UCAS application number (APP_NO) and choice number (CHOICE_NO) provide direct UCAS linkage. The core business data is held in CONDITION_TYPE and CONDITION_DESC, which are free-text fields for user-entered condition details, and the SATISFIED flag, which tracks fulfillment status ('Y' or 'N'). Standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present for full audit compliance. Two unique indexes enforce data integrity: IGS_UC_APP_CHO_CNDS_U1 on APP_CHOICE_COND_ID and IGS_UC_APP_CHO_CNDS_U2 on the combination of APP_NO, CHOICE_NO, and CONDITION_TYPE.

Common Use Cases and Queries

This table is central to managing the conditional offer lifecycle. Common operational and reporting use cases include generating lists of pending conditions for applicants, updating the SATISFIED flag when a condition is met, and auditing condition history. A frequent query pattern involves joining this table to the main application choice table (likely keyed on APP_CHOICE_ID) to retrieve a comprehensive view of an applicant's offer status. For example, to find all unsatisfied conditions for a specific application number, one would use:

• SELECT CONDITION_TYPE, CONDITION_DESC FROM IGS.IGS_UC_APP_CHO_CNDS WHERE APP_NO = <application_number> AND SATISFIED = 'N';

Another critical pattern is verifying data integrity by checking for orphaned records where the APP_CHOICE_ID might not have a corresponding parent record in the related application choices table.

Related Objects

Based on the provided dependency information, the IGS_UC_APP_CHO_CNDS table does not reference other objects but is referenced by the APPS schema synonym IGS_UC_APP_CHO_CNDS. This indicates it is a foundational table with a public synonym for application access. The presence of the APP_CHOICE_ID column strongly implies a foreign key relationship with a parent table storing the main application choice records, such as IGS_UC_APP_CHOICES or a similarly named entity, although this specific relationship is not explicitly detailed in the provided metadata. The unique index on APP_NO, CHOICE_NO, and CONDITION_TYPE also suggests a logical relationship with the core UCAS application transaction tables.