Search Results igs_uc_offer_conds




Overview
Explore in AI Chat

Overview

The IGS_UC_OFFER_CONDS table is a core master data table within the Oracle E-Business Suite Student System (IGS), specifically for versions 12.1.1 and 12.2.2. It functions as the central repository for the generic condition library, which is integral to managing admissions offers. The table provides the definitive list of conditions that can be attached to an offer of admission to a prospective student, such as academic, financial, or documentary requirements. Its primary role is to establish a unique, standardized catalog of condition types that can be consistently referenced across the admissions lifecycle, ensuring data integrity and enabling automated offer management processes.

Key Information Stored

The table is uniquely identified by a composite primary key consisting of CONDITION_CATEGORY and CONDITION_NAME. These two columns together form the definitive code for an offer condition. While the provided metadata does not list all columns, the primary key structure and foreign key relationships imply that the table stores descriptive and control attributes for each condition code. This typically includes a display description, status flags (e.g., active/inactive), and potentially a condition type classification. The table's design ensures that a condition is uniquely defined within a specific category, allowing for logical grouping (e.g., "Academic Conditions," "Language Conditions").

Common Use Cases and Queries

This table is primarily accessed in scenarios involving the setup, assignment, and reporting of admission offer conditions. Common use cases include the maintenance of the condition library by administrative staff, the automatic or manual assignment of conditions to applicant choices, and the generation of compliance reports. A frequent reporting requirement is to list all active conditions within a specific category. A typical query pattern involves joining this master table to transactional tables to analyze condition prevalence.

  • Listing all unique condition categories: SELECT DISTINCT condition_category FROM igs_uc_offer_conds;
  • Finding all conditions assigned to a specific applicant choice (joining with IGS_UC_APP_CHOICES): SELECT oc.condition_category, oc.condition_name FROM igs_uc_offer_conds oc, igs_uc_app_choices ac WHERE ac.condition_category = oc.condition_category AND ac.condition_code = oc.condition_name AND ac.person_id = :1;
  • Identifying unused conditions in the library: SELECT condition_category, condition_name FROM igs_uc_offer_conds oc WHERE NOT EXISTS (SELECT 1 FROM igs_uc_app_choices ac WHERE ac.condition_category = oc.condition_category AND ac.condition_code = oc.condition_name);

Related Objects

The IGS_UC_OFFER_CONDS table has defined foreign key relationships with several key transactional and setup tables in the Student System, underscoring its role as a master data source.

  • IGS_UC_APP_CHOICES: This table stores individual course choices for applicants. The columns CONDITION_CATEGORY and CONDITION_CODE reference IGS_UC_OFFER_CONDS to record the specific offer condition attached to that choice.
  • IGS_UC_COND_DETAILS: This table likely holds additional, detailed attributes or rules for a condition. Its columns CONDITION_CATEGORY and CONDITION_NAME reference the master definition in IGS_UC_OFFER_CONDS.
  • IGS_AD_DFLT_OUDTLS: This setup table defines default outcome details. The columns UCAS_COND_CATEGORY and UCAS_COND_NAME reference IGS_UC_OFFER_CONDS, allowing administrators to predefine standard conditions for certain offer types or courses.