Search Results igs_ss_inq_acad




Overview
Explore in AI Chat

Overview

The table IGS_SS_INQ_ACAD is a data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary function was to serve as a staging table for storing academic interest data submitted by prospective students or applicants through self-service interfaces, such as online inquiry forms. This staging mechanism is a common architectural pattern in EBS for temporarily holding transactional data from external sources before it is validated and processed into the core application tables. Crucially, the provided ETRM documentation explicitly marks this table as "Obsolete." This status indicates that while the table may physically exist in databases running versions 12.1.1 or 12.2.2, its associated functionality is no longer actively supported or used by the standard application code. It has likely been superseded by an alternative data model or process within later iterations of the Student System.

Key Information Stored

The table's structure is centered around capturing a unique academic interest record and linking it to a specific inquiry. The most critical column, as indicated by the user's search term and the primary key definition, is INQ_ACAD_ID. This column holds a unique system-generated identifier (typically a sequence number) for each staged academic interest record. Another essential column is INQ_PERSON_ID, which is a foreign key column. This field stores the identifier that links the academic interest record to a specific person/inquiry record in the related staging table, IGS_SS_INQ_PERSON_ALL. While the full column list is not detailed in the provided metadata, a table of this nature would typically also include fields for the academic program or course of interest, the intended term of entry, and creation metadata (created_by, creation_date).

Common Use Cases and Queries

Given the table's obsolete status, new development or reporting should not directly reference IGS_SS_INQ_ACAD. Historical analysis or data migration efforts might be the only valid use cases. A typical query to investigate existing data would involve joining to the main inquiry staging table. For example, to retrieve all staged academic interests for inquiries created after a specific date, one might use a pattern similar to the following:

  • SELECT inq_acad.inq_acad_id, inq_acad.inq_person_id, inq_person.creation_date FROM igs.igs_ss_inq_acad inq_acad JOIN igs.igs_ss_inq_person_all inq_person ON inq_acad.inq_person_id = inq_person.inq_person_id WHERE inq_person.creation_date > :1;

Any operational processes, such as loading inquiry data or generating prospect reports, would now utilize the current, supported tables that replaced this obsolete object.

Related Objects

The primary related object is the table IGS_SS_INQ_PERSON_ALL, which holds the core person/inquiry staging data. The foreign key relationship (IGS_SS_INQ_ACAD.INQ_PERSON_ID references IGS_SS_INQ_PERSON_ALL) enforces this dependency. The table's primary key constraint is named IGS_SS_INQ_ACAD_PK. As a staging table within the IGS schema, it was part of a larger set of self-service staging tables (likely prefixed with IGS_SS_INQ_ or IGS_SS_STG_) designed to work in concert. The obsolescence of this table suggests that its functional dependencies have been remapped to a new set of tables within the active Student System data model.