Search Results enquiry_appl_number




Overview
Explore in AI Chat

Overview

The IGS_AD_I_PRG_PREFS table is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary function was to store the academic program preferences submitted by an individual during an inquiry or preliminary application process. This table linked a person's specific inquiry instance to their ranked choices of programs or courses of study. It is critical to note that the official ETRM documentation explicitly marks this table as "Obsolete." This status indicates that while the table may still exist in the database schema for historical data integrity or upgrade purposes, it is no longer actively used or supported by the core application logic in Oracle EBS releases 12.1.1 and 12.2.2. New implementations or customizations should not rely on this table for current business processes.

Key Information Stored

The table's structure is designed to uniquely associate a person's inquiry with their program selections. The key columns, as defined by its primary and unique keys, include:

  • INQ_PROG_PREF_ID: The system-generated primary key identifier for each program preference record.
  • PERSON_ID: References the individual who made the inquiry, typically linking to the core person table (e.g., PER_ALL_PEOPLE_F).
  • ENQUIRY_APPL_NUMBER: A number identifying the specific inquiry or application instance for that person.
  • INQ_PROG_CODE_ID: A foreign key linking to the IGS_AD_INQ_PROGS table, identifying the specific program code that was preferred.
  • PROG_PREF_ID: Likely stores a numerical ranking or identifier for the preference order (e.g., 1 for first choice, 2 for second).

Common Use Cases and Queries

Given its obsolete status, direct operational use cases are deprecated. However, the table may be referenced for historical data analysis or during data migration projects. A typical historical query might involve joining to person and program tables to retrieve a snapshot of inquiry preferences for archival reporting.

Sample Historical Query Pattern:
SELECT ppr.person_id, pap.full_name, ppr.enquiry_appl_number, ip.program_code, ppr.prog_pref_id
FROM igs.igs_ad_i_prg_prefs ppr
JOIN igs.igs_ad_inq_progs ip ON ppr.inq_prog_code_id = ip.inq_prog_code_id
JOIN apps.per_all_people_f pap ON ppr.person_id = pap.person_id AND SYSDATE BETWEEN pap.effective_start_date AND pap.effective_end_date
WHERE ppr.enquiry_appl_number = :p_app_number;

Important: Any such queries should be used with caution and only for legacy data retrieval, not for active business processes.

Related Objects

The ETRM metadata defines specific foreign key relationships for this table, which are essential for understanding its place in the obsolete schema.

  • Parent Table (Foreign Key): IGS_AD_INQ_PROGS
    • Join Column: IGS_AD_I_PRG_PREFS.INQ_PROG_CODE_ID references IGS_AD_INQ_PROGS.INQ_PROG_CODE_ID
  • Parent Table (Foreign Key): IGS_AD_I_PRFL (implied by the foreign key on PERSON_ID and ENQUIRY_APPL_NUMBER)
    • Join Columns: IGS_AD_I_PRG_PREFS.PERSON_ID and IGS_AD_I_PRG_PREFS.ENQUIRY_APPL_NUMBER reference the corresponding columns in the inquiry profile table.
  • Child Table (Foreign Key): IGS_AD_I_PRG_PRF_UST
    • Join Column: IGS_AD_I_PRG_PRF_UST.INQ_PROG_PREF_ID references IGS_AD_I_PRG_PREFS.INQ_PROG_PREF_ID