Search Results igs_ss_inq_uset_pk

Overview

The table IGS_SS_INQ_USET is a legacy data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. As explicitly stated in its documentation, its purpose was to hold staging data for Self Service Inquiry Unit Sets. This indicates it functioned as a transient or working storage table, likely part of a batch or online process flow where student academic unit set data was prepared or staged before being formally processed or posted to core transactional tables. Critically, the documentation marks both the table and the broader Student System module as "Obsolete." Furthermore, the provided metadata includes the note "Not implemented in this database," which strongly suggests that while the table definition may exist in the data dictionary, it was not deployed or populated in standard implementations of EBS releases 12.1.1 and 12.2.2, rendering it non-functional in those environments.

Key Information Stored

Based on the provided metadata, the primary data element stored was a unique identifier for each staged inquiry unit set record. The documented structure is minimal, revealing only the primary key column and a foreign key column. The primary key column, INQ_USET_ID, uniquely identified each record within this staging table. The foreign key column, INQ_INQ_ID, linked the staged unit set data back to a parent inquiry record in the related IGS_SS_INQUIRY table. This relationship implies that multiple unit set records (in IGS_SS_INQ_USET) could be associated with a single overarching inquiry transaction.

Common Use Cases and Queries

Given the object's obsolete status and noted non-implementation, there are no active production use cases in standard EBS 12.1.1 or 12.2.2 environments. Historically, during its active lifecycle, it would have been involved in student self-service processes where inquiries about unit sets (e.g., program requirements, course enrollments) were submitted. Queries would have focused on retrieving staged data for processing. A typical historical query pattern might have been a join to the parent inquiry table to review all pending unit set data for a specific inquiry.

SELECT uset.*
FROM igs_ss_inq_uset uset,
     igs_ss_inquiry inq
WHERE uset.inq_inq_id = inq.inq_id
  AND inq.inquiry_number = '<INQUIRY_NUMBER>';

Any reporting or data extraction involving this table in a contemporary context would be exclusively for legacy data analysis or migration purposes in exceptionally old, customized instances.

Related Objects

• IGS_SS_INQUIRY (Table): This is the sole documented foreign key relationship. The column IGS_SS_INQ_USET.INQ_INQ_ID references the primary key of the IGS_SS_INQUIRY table. This establishes that staged unit set records were children of a broader self-service inquiry transaction.
• IGS_SS_INQ_USET_PK (Primary Key Constraint): The primary key constraint defined on the INQ_USET_ID column.

The metadata does not indicate any other tables, views, or APIs that depend on IGS_SS_INQ_USET, consistent with its staging and obsolete nature.