Search Results igs_ad_ent_inq_progs_u2

Overview

The IGS_AD_ENT_INQ_PROGS table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (iGraduate) product family, which typically handles student administration and admissions. This table functions as a junction or mapping table that defines the relationship between inquiry entry statuses and specific academic programs. Its primary role is to store which programs are applicable or available for selection based on an applicant's current inquiry status, thereby enforcing business rules during the admissions inquiry and application process. The table's design ensures referential integrity and supports the configuration of valid program pathways for prospective students.

Key Information Stored

The table's columns store both business data and standard audit information. The key business columns are:

• ENT_INQ_PROG_ID: A mandatory, unique numeric identifier (NUMBER 15) serving as the primary key for each record in this table.
• INQ_ENTRY_STAT_ID: A mandatory foreign key (NUMBER 15) uniquely identifying an inquiry entry status, likely referencing a status master table.
• INQ_PROG_CODE_ID: A mandatory foreign key (NUMBER 15) uniquely identifying an inquiry program code, referencing a program catalog or definition table.
• CLOSED_IND: A VARCHAR2 column acting as a flag (e.g., 'Y'/'N') to indicate if the specific program mapping for a given status is no longer active or available for new inquiries.
• Standard WHO Columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for auditing changes.

The uniqueness of the combination of INQ_ENTRY_STAT_ID and INQ_PROG_CODE_ID, enforced by the IGS_AD_ENT_INQ_PROGS_U2 index, is critical. It prevents duplicate program mappings for the same inquiry status.

Common Use Cases and Queries

This table is central to configuring and validating the admissions workflow. A primary use case is to determine all programs a prospective student can inquire about or apply to based on their current entry status. For example, an "International" inquiry status might be mapped to a different set of programs than a "Domestic" status. System administrators use this table to set up or modify these business rules. For reporting and data validation, common SQL patterns include fetching all active mappings or identifying programs linked to a specific status.

Sample Query: Retrieve all active program mappings for a specific inquiry entry status ID.

SELECT iep.ent_inq_prog_id,
       iep.inq_entry_stat_id,
       iep.inq_prog_code_id,
       pc.program_code,
       pc.program_name
FROM igs.igs_ad_ent_inq_progs iep
JOIN igs.igs_ps_prog_codes pc ON iep.inq_prog_code_id = pc.prog_code_id -- Assumed table/column
WHERE iep.inq_entry_stat_id = :p_status_id
  AND NVL(iep.closed_ind, 'N') = 'N'
ORDER BY pc.program_code;

Related Objects

While the provided dependency information states the table does not reference other objects, it is intrinsically linked to several key entities in the IGS schema. It is referenced by the APPS synonym IGS_AD_ENT_INQ_PROGS, which is the standard access point for EBS applications. The table's foreign key columns, INQ_ENTRY_STAT_ID and INQ_PROG_CODE_ID, logically depend on master tables defining inquiry entry statuses (e.g., IGS_AD_ENT_STAT) and program codes (e.g., IGS_PS_PROG_CODES), respectively. These relationships are essential for maintaining data integrity, though they may be enforced at the application level rather than through database constraints. Reports and application forms that manage inquiry-to-program workflows will directly query or update this mapping table.