Search Results igs_ss_inq_prog_uset_pk

Overview

The table IGS_SS_INQ_PROG_USET is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. As explicitly stated in its documentation, its purpose is to hold Self Service Staging Inquiry Program Unit Sets. This table was part of a staging or intermediary data model, likely designed to support self-service inquiry functionalities related to academic programs and their associated unit sets. Crucially, the metadata indicates this table and the broader IGS - Student System module are marked as "Obsolete." Furthermore, the implementation notes specify that this table was "Not implemented in this database," meaning it exists as a definition within the data dictionary but does not contain application data in a standard deployment of EBS 12.1.1 or 12.2.2. Its role, therefore, is historical or architectural, representing a superseded design component.

Key Information Stored

Based on the provided ETRM metadata, the table's structure is defined by its primary and unique keys. The primary technical identifier is the column INQ_PROG_USET_ID, which forms the primary key IGS_SS_INQ_PROG_USET_PK. The table enforces a unique constraint (IGS_SS_INQ_PROG_USET_UK) on the combination of two columns: INQ_PROG_UNIT_SET_ID and INQ_PROG_ID. This combination logically defines a unique relationship between a specific inquiry program and a unit set within that program. The INQ_PROG_ID column is specifically documented as a foreign key, linking each record back to a parent inquiry program record in the related IGS_SS_INQ_PROG table.

Common Use Cases and Queries

Given the table's obsolete status and lack of implementation, there are no active operational use cases in a standard EBS environment. In a historical or data migration context, its intended use was to associate unit sets (collections of academic units or courses) with specific inquiry programs within the self-service framework. Sample queries would have centered on retrieving these associations. A typical pattern would involve joining to the parent inquiry program table using the documented foreign key. For example, a query to list all unit set IDs for a specific inquiry program would have been structured as: SELECT INQ_PROG_UNIT_SET_ID FROM IGS_SS_INQ_PROG_USET WHERE INQ_PROG_ID = :1;. Any reporting or integration involving this table in a live system would be highly atypical and would require verification of actual data existence.

Related Objects

The documented metadata defines a single, clear foreign key relationship for this table. The relationship data shows that IGS_SS_INQ_PROG_USET references the IGS_SS_INQ_PROG table. The join is made from the column IGS_SS_INQ_PROG_USET.INQ_PROG_ID to a corresponding column in the IGS_SS_INQ_PROG table. No other foreign keys referencing other tables are documented in the provided excerpt. The primary key column, INQ_PROG_USET_ID, could potentially be referenced by other obsolete objects, but such relationships are not specified in the given metadata. Therefore, the primary related object is the parent table IGS_SS_INQ_PROG, which is also part of the obsolete Self Service Staging component.