Search Results inq_unit_set_pref_id




Overview
Explore in AI Chat

Overview

The IGS_AD_I_USET_PREFS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Admissions (IGS) module. It functions as the definitive repository for storing an applicant's academic program preferences during the inquiry stage of the admissions lifecycle. The table captures the linkage between a prospective student's inquiry application instance and their selected unit sets (often representing majors, courses, or academic plans), establishing a formal record of their preliminary study intentions before a formal application is submitted.

Key Information Stored

The table's columns are categorized into identifiers, preference data, and standard audit fields. The primary unique identifier is INQ_UNIT_SET_PREF_ID, a system-generated sequence number. The table establishes its core relationship through three key foreign key columns: PERSON_ID, ENQUIRY_APPL_NUMBER, and INQ_UNIT_SET_CODE_ID. These collectively tie a specific unit set preference to a unique person and their specific inquiry application. The UNIT_SET_PREF_ID column may store a reference to a master list of available unit sets. A set of columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) supports data import and concurrent processing. Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) complete the record for auditing.

Common Use Cases and Queries

This table is central to reporting and processes related to prospective student engagement and pipeline analysis. Common use cases include generating reports on the popularity of specific academic programs (unit sets) among inquirers, tracking an individual's evolving study interests across multiple inquiries, and ensuring data integrity during the conversion of an inquiry to a formal application. A typical query to retrieve all unit set preferences for a specific inquiry application would leverage the unique composite key. The search for "inq_unit_set_pref_id" indicates a direct lookup or validation operation using the table's primary key.

  • Retrieve Preferences for an Inquiry: SELECT * FROM igs.igs_ad_i_uset_prefs WHERE person_id = <P_ID> AND enquiry_appl_number = <EAN>;
  • Count Preferences by Unit Set: SELECT inq_unit_set_code_id, COUNT(*) FROM igs.igs_ad_i_uset_prefs GROUP BY inq_unit_set_code_id;
  • Primary Key Lookup: SELECT * FROM igs.igs_ad_i_uset_prefs WHERE inq_unit_set_pref_id = <ID>;

Related Objects

Based on the provided metadata, the table's integrity is enforced by three unique indexes. The IGS_AD_I_USET_PREFS_U1 index is on the primary key column INQ_UNIT_SET_PREF_ID. The IGS_AD_I_USET_PREFS_U2 index enforces uniqueness on the combination of PERSON_ID, ENQUIRY_APPL_NUMBER, and INQ_UNIT_SET_CODE_ID, preventing duplicate program preferences within a single inquiry. The IGS_AD_I_USET_PREFS_U3 index on PERSON_ID, ENQUIRY_APPL_NUMBER, and UNIT_SET_PREF_ID suggests an alternative unique constraint. While explicit foreign key dependencies are not listed in the excerpt, the column names strongly imply relationships to core IGS tables such as IGS_PE_PERSON (PERSON_ID), IGS_ENQUIRY_APPL (ENQUIRY_APPL_NUMBER), and IGS_AS_UNIT_SET (or similar, for INQ_UNIT_SET_CODE_ID and UNIT_SET_PREF_ID).