Search Results igs_ad_inq_progs_uk




Overview
Explore in AI Chat

Overview

The IGS_AD_INQ_PROGS table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary function is to store and maintain a master list of program codes associated with student inquiries, which are initial expressions of interest in academic programs. This table serves as a reference entity, providing a standardized set of valid program codes that can be linked to specific inquiry records and related configuration data. It is critical to note that the official ETRM documentation explicitly marks this table as Obsolete. This status indicates that while the table may exist in schemas for versions 12.1.1 and 12.2.2 to support historical data and potential backward compatibility, its use in new development or business processes is deprecated, and it may be targeted for removal in future releases.

Key Information Stored

The table's design centers on two key identifiers for inquiry program codes. The primary technical key is INQ_PROG_CODE_ID, a unique system-generated identifier that serves as the primary key for the table (IGS_AD_INQ_PROGS_PK). This ID column is the primary point of reference for all foreign key relationships from other tables. The business key is INQ_PROG_CODE, which holds the actual program code value and is enforced as unique via the IGS_AD_INQ_PROGS_UK constraint. While the specific metadata for additional descriptive columns (such as a program name or effective dates) is not provided in the excerpt, tables of this nature in the IGS module typically include columns for active/inactive status, description, creation date, and last update details to support full auditability and lifecycle management of the code values.

Common Use Cases and Queries

Given its obsolete status, primary use cases involve historical reporting, data migration validation, and support for legacy integrations. Common queries would focus on identifying all defined inquiry programs or resolving program codes for existing inquiry data. A typical pattern would be a join to related transactional tables to generate legacy reports.

  • Listing All Inquiry Program Codes: SELECT inq_prog_code_id, inq_prog_code FROM igs.igs_ad_inq_progs ORDER BY inq_prog_code;
  • Validating Data Integrity for Historical Records: SELECT ei.* FROM igs.igs_ad_ent_inq_progs ei WHERE NOT EXISTS (SELECT 1 FROM igs.igs_ad_inq_progs ip WHERE ip.inq_prog_code_id = ei.inq_prog_code_id); This query helps identify orphaned records in child tables that reference non-existent program codes.

Related Objects

The IGS_AD_INQ_PROGS table is referenced as a parent table by several other entities in the Student System, primarily through the foreign key column INQ_PROG_CODE_ID. These relationships link the master program code to specific inquiry instances and their associated preferences or packages. The documented foreign key relationships are as follows:

  • IGS_AD_ENT_INQ_PROGS: Links inquiry program codes to specific entrance inquiry records.
  • IGS_AD_I_PRG_PREFS: Stores program preferences associated with an inquiry, referencing the master code.
  • IGS_AD_I_PRG_PKG_ITM: References inquiry program codes within the context of program package items.
  • IGS_AD_I_PRG_U_SET: Links inquiry program codes to unit sets within the inquiry process.

When querying these related tables, the standard join condition is child_table.inq_prog_code_id = igs_ad_inq_progs.inq_prog_code_id. The obsolete status of IGS_AD_INQ_PROGS suggests that these related objects may also be deprecated or that their referencing logic has been superseded by newer data models.