Search Results igs_ad_i_uset_prefs




Overview
Explore in AI Chat

Overview

The table IGS_AD_I_USET_PREFS is a core data object within the Oracle E-Business Suite Student System (IGS) module. It is designed to store the academic unit set preferences specified by an applicant during the inquiry stage of the admissions lifecycle. Each record links a person's specific inquiry application instance to their preferred course or program unit sets. It is critical to note that the official product documentation explicitly marks this table as Obsolete. This status indicates that while the table may exist in schemas for installations upgraded from earlier versions (such as 12.1.1 or 12.2.2), its use in new development is deprecated, and its business logic has likely been superseded by other objects or data models in later application flows.

Key Information Stored

The table's structure centers on uniquely identifying an applicant's inquiry and their ordered preferences for unit sets. The primary identifier is the system-generated INQ_UNIT_SET_PREF_ID. The table enforces data integrity through multiple unique keys, highlighting the critical columns: PERSON_ID (identifying the applicant), ENQUIRY_APPL_NUMBER (identifying the specific inquiry application instance for that person), and either the INQ_UNIT_SET_CODE_ID (a foreign key to the inquiry unit set definition) or a UNIT_SET_PREF_ID (which may represent a preference ranking or identifier). The combination of PERSON_ID and ENQUIRY_APPL_NUMBER is a fundamental composite key for relating all preferences to a single inquiry application, directly addressing the user's search context for 'enquiry_appl_number'.

Common Use Cases and Queries

Given its obsolete status, direct operational use in current processes is discouraged. Historically, its purpose was to support reporting and decision-making on inquiry-stage applicant interests. Common queries would involve retrieving all unit set preferences for a specific inquiry application or analyzing popular unit sets across inquiries. A sample reporting query pattern would be:

  • SELECT person_id, enquiry_appl_number, inq_unit_set_code_id FROM igs.igs_ad_i_uset_prefs WHERE person_id = :p_person_id AND enquiry_appl_number = :p_enquiry_appl_number ORDER BY unit_set_pref_id;

This would list the ordered preferences for a given applicant's inquiry. Data from this table might also have been used to populate initial application preferences or for historical trend analysis in legacy reports.

Related Objects

The table's integrity is maintained through defined foreign key relationships. The INQ_UNIT_SET_CODE_ID column references IGS_AD_INQ_UNIT_SETS, which is the master table defining the available unit sets for inquiries. Furthermore, the composite of PERSON_ID and ENQUIRY_APPL_NUMBER likely references a parent inquiry header table (such as IGS_AD_PERSON_INQ_INST or similar), which stores the core details of the inquiry application itself. Developers or analysts investigating this obsolete table must examine these related objects to understand the full, historical data model and to identify any current tables that may have assumed its functionality.