Search Results igs_ss_inq_uset_u1

Overview

The IGS_SS_INQ_USET table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle Student Management) product family. As indicated in its documentation, it holds Self Service Staging Inquiry Unit Sets records. This table functions as a staging or transactional repository for data related to unit set preferences submitted by prospective or current students through self-service inquiry interfaces. The data is typically processed from this staging table into other core transactional tables within the student system. It is critical to note the documented status of this object is "Obsolete," indicating it may be part of a legacy data model or superseded by alternative structures in later implementations or patches, though it remains present and valid in the specified EBS versions.

Key Information Stored

The table stores the relationship between an inquiry and the academic unit sets associated with it. Key columns include:

• INQ_USET_ID (NUMBER): The primary key and unique identifier for each record in this table.
• INQ_INQ_ID (NUMBER): A foreign key linking the record to a specific student inquiry, likely referencing a parent inquiry table.
• UNIT_SET_PREF_ID (NUMBER): An identifier for the specific unit set preference.
• INQ_UNIT_SET_CODE_ID (NUMBER): An identifier for the academic unit set code (e.g., a major or course of study).
• STATUS (VARCHAR2): Indicates the processing or lifecycle state of the staging record (e.g., 'NEW', 'PROCESSED', 'ERROR').
• Standard Who Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): Capture audit information.
• Concurrent Program Who Columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE): Track the concurrent request that created or updated the record.

Common Use Cases and Queries

This table is primarily accessed for data validation, troubleshooting staging processes, and generating audit reports on submitted unit set preferences. A common use case involves identifying inquiries with pending unit set data that has not been processed into the main system. The following query pattern retrieves all unit set records for a specific inquiry, which is useful for support or reconciliation tasks:

SELECT inq_uset_id, unit_set_pref_id, inq_unit_set_code_id, status, creation_date
FROM igs.igs_ss_inq_uset
WHERE inq_inq_id = :inquiry_id
ORDER BY creation_date DESC;

Another typical report analyzes the volume and status of staged records over a period to monitor the health of the self-service intake process:
SELECT TRUNC(creation_date) AS creation_day, status, COUNT(*) AS record_count
FROM igs.igs_ss_inq_uset
WHERE creation_date >= SYSDATE - 30
GROUP BY TRUNC(creation_date), status
ORDER BY creation_day DESC, status;

Related Objects

Based on the provided dependency information, the IGS_SS_INQ_USET table does not reference other objects but is referenced by an APPS synonym named IGS_SS_INQ_USET. This synonym allows other modules and application code within the APPS schema to access the table without prefixing the IGS owner. The key relational columns suggest logical foreign key relationships to other IGS inquiry and unit set master tables, though these are not explicitly defined in the provided metadata. The INQ_INQ_ID column logically references a parent inquiry table (e.g., IGS_SS_INQUIRY), and the INQ_UNIT_SET_CODE_ID logically references a unit set code definition table. The unique index IGS_SS_INQ_USET_U1 on the INQ_USET_ID column enforces the primary key constraint.