Search Results igs_ss_inq_info_req

Overview

The table IGS_SS_INQ_INFO_REQ is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. As explicitly stated in the ETRM documentation, its purpose is to hold Self Service Staging Information requested records. This table was part of the architecture designed to manage data for student self-service inquiries, likely acting as a staging or transactional area for information requests before final processing or integration with core student records. Crucially, the metadata labels both the product module and this specific table as "Obsolete." This indicates the table and its associated functionality are deprecated and no longer part of the active, supported data model in EBS releases 12.1.1 and 12.2.2. The provided note, "Not implemented in this database," further confirms its non-active status in standard implementations.

Key Information Stored

Based on the provided ETRM metadata, the primary data element stored is the unique identifier for each information request record. The central column is INQ_INFO_REQ_ID, which serves as the table's primary key. This column ensures each staged information request is uniquely identifiable within the IGS_SS_INQ_INFO_REQ table. The documented foreign key relationship reveals another critical column: INQ_INQ_ID. This field stores a foreign key that links each staged information request record back to its parent inquiry record in the related IGS_SS_INQUIRY table, establishing the core relationship between a general inquiry and its specific information requests.

Common Use Cases and Queries

Given the table's obsolete status and note of non-implementation, active operational or reporting use cases in EBS 12.1.1/12.2.2 are non-existent. Its use would have been historical, confined to earlier versions of the Student System. In those contexts, it would have supported the self-service inquiry workflow. A typical query would have joined this staging table to the main inquiry table to retrieve all information requests associated with a specific inquiry. A sample historical query pattern might have been:

• SELECT inq_info.* FROM igs_ss_inq_info_req inq_info WHERE inq_info.inq_inq_id = :p_inquiry_id;

Any contemporary reporting or data extraction should disregard this object, as it holds no implemented data in the current system.

Related Objects

The ETRM documentation specifies a single, direct foreign key relationship for the IGS_SS_INQ_INFO_REQ table. This relationship is fundamental to its obsolete data model.

• IGS_SS_INQUIRY: This is the primary related table. The relationship is defined by the foreign key column IGS_SS_INQ_INFO_REQ.INQ_INQ_ID referencing the IGS_SS_INQUIRY table. This links each staged information request record to a master inquiry record. The IGS_SS_INQUIRY table itself may also be obsolete, given the context.

The primary key constraint IGS_SS_INQ_INFO_REQ_PK on the INQ_INFO_REQ_ID column is the other key documented object related to this table's structure.