Search Results prog_pref_id




Overview
Explore in AI Chat

Overview

The IGS_AD_I_PRG_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 module (IGS). It functions as the primary repository for storing a prospective student's (person's) academic program preferences linked to a specific inquiry application instance. An inquiry represents an initial expression of interest in the institution, and this table captures the detailed study programs the inquirer is considering. Its role is to maintain the relationship between a person, their inquiry application, and their ranked or listed program choices, forming a critical link in the admissions pre-application tracking and conversion process.

Key Information Stored

The table's columns can be categorized into functional data, unique identifiers, and standard audit information. The primary functional columns establish the core relationships: PERSON_ID identifies the prospective student, ENQUIRY_APPL_NUMBER identifies the specific inquiry application, INQ_PROG_CODE_ID links to the specific program code being preferred, and PROG_PREF_ID indicates the preference order or identifier for that program choice. The INQ_PROG_PREF_ID column serves as the unique primary key for each record. The table also includes standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and a set of columns related to import processes (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), which are typical for data loaded via concurrent programs.

Common Use Cases and Queries

A primary use case is generating reports on inquiry trends by program interest, which aids in recruitment strategy and resource planning. Support and functional consultants frequently query this table to troubleshoot data issues or verify a person's stated preferences. The column ENQUIRY_APPL_NUMBER, as indicated by the user's search, is a critical filter for isolating all program preferences for a single inquiry application. Common SQL patterns include fetching all preferences for a given inquiry or joining to person and program tables for a comprehensive view.

  • Retrieve all program preferences for a specific inquiry application number: SELECT * FROM IGS.IGS_AD_I_PRG_PREFS WHERE ENQUIRY_APPL_NUMBER = <number>;
  • List a person's program preferences across their inquiries, joined with basic program details: SELECT p.enquiry_appl_number, p.prog_pref_id, c.prog_code FROM IGS.IGS_AD_I_PRG_PREFS p, IGS_AD_INQ_PROGS c WHERE p.inq_prog_code_id = c.inq_prog_code_id AND p.person_id = <id> ORDER BY p.enquiry_appl_number, p.prog_pref_id;

Related Objects

The table maintains defined relationships with other key admissions tables, primarily through foreign key constraints. It references the IGS_AD_INQ_PROGS table via the INQ_PROG_CODE_ID column to validate the inquiry program code. It is referenced by the IGS_AD_I_PRG_PRF_UST table, likely a history or audit table, via the INQ_PROG_PREF_ID primary key. The relationship from PERSON_ID to a person table (indicated as '%' in the metadata) typically links to PER_ALL_PEOPLE_F or an IGS-specific person base table. The table's unique indexes, particularly IGS_AD_I_PRG_PREFS_U2 on (PERSON_ID, ENQUIRY_APPL_NUMBER, INQ_PROG_CODE_ID), enforce critical business rules preventing duplicate program listings within an inquiry.