Search Results igs_ss_inquiry




Overview
Explore in AI Chat

Overview

The IGS_SS_INQUIRY table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS) module. It functions as a staging repository for inquiry records generated through the Self Service application interface. Historically, this table captured preliminary student interest data, serving as a precursor to formal application or enrollment processes. Critically, the official ETRM documentation explicitly marks this table as "Obsolete." This status indicates that while the table may persist in the database schema for backward compatibility, its use in current implementations of EBS 12.1.1 and 12.2.2 is deprecated, and it is likely superseded by newer data models or integrated workflows within the Self Service framework.

Key Information Stored

While the provided metadata does not list individual column definitions, the primary and foreign key relationships reveal the table's fundamental structure. The central identifier is the INQ_INQ_ID column, which serves as the table's primary key (IGS_SS_INQUIRY_PK) and uniquely identifies each inquiry record. A second critical column is INQ_PERSON_ID, which establishes a link to a person record in the IGS_SS_INQ_PERSON_ALL table. This relationship suggests the table stored core inquiry metadata, likely including creation dates, source information, and status flags, associated with a specific individual. The existence of multiple child tables indicates the inquiry record acted as a header for more detailed, related information.

Common Use Cases and Queries

Given its obsolete status, direct operational use cases for this table in active development or reporting are strongly discouraged. Its primary contemporary relevance is for historical data analysis, data migration validation, or understanding legacy system behavior. Typical queries would involve joining to its related tables to reconstruct a complete historical inquiry. A sample analytical query might resemble:

Any new integrations or reports should utilize the current, supported APIs and tables as defined by Oracle.

Related Objects

The table maintains defined relationships with several other IGS staging tables, forming a logical hierarchy for obsolete inquiry data.

  • Referenced Parent Table: The table references IGS_SS_INQ_PERSON_ALL via the foreign key on the column IGS_SS_INQUIRY.INQ_PERSON_ID.
  • Referencing Child Tables: This table is referenced as a parent by three key child tables:
    • IGS_SS_INQ_INFO_REQ via IGS_SS_INQ_INFO_REQ.INQ_INQ_ID
    • IGS_SS_INQ_PROG via IGS_SS_INQ_PROG.INQ_INQ_ID
    • IGS_SS_INQ_USET via IGS_SS_INQ_USET.INQ_INQ_ID
    These relationships suggest the child tables stored specific details about information requests, programs of interest, and user-defined attributes linked to the main inquiry header.