Search Results igr_is_inquiry




Overview
Explore in AI Chat

Overview

The IGR_IS_INQUIRY table is a core data object within the now-obsolete IGS (Student System) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functioned as a staging table within the Self Service architecture, specifically designed to hold inquiry records submitted by prospective students or applicants via web-based interfaces. Its primary role was to temporarily store and manage inbound inquiry data before it was processed, validated, and potentially integrated into the core student information system. The "Obsolete" status indicates this table and its associated module are part of a legacy code path, likely superseded by later Oracle Student implementations, and may not be actively implemented or extended in newer environments.

Key Information Stored

The table's structure is centered on capturing the details of an inquiry. The most critical column is INQ_INQ_ID, which serves as the table's unique primary key identifier for each inquiry record. Other significant columns include INQ_PERSON_ID, which links the inquiry to a person record in the staging area, and INQUIRY_TYPE_ID, which classifies the nature or category of the inquiry. While the full column list is not provided in the excerpt, a table of this nature would typically store data such as inquiry source, creation date, status, contact details, academic interests, and comments submitted by the inquirer.

Common Use Cases and Queries

This table was central to managing the prospective student engagement pipeline. Common operational use cases included reviewing newly submitted inquiries for follow-up by admissions staff, generating reports on inquiry volumes by type or source, and processing batches of inquiries for data validation. A typical reporting query would join to the person staging table to retrieve names and contact information. For instance, to find all inquiries of a specific type, one might use a pattern like:

  • SELECT inq.inq_inq_id, per.name, inq.creation_date FROM igr_is_inquiry inq, igr_is_per_all per WHERE inq.inq_person_id = per.person_id AND inq.inquiry_type_id = :TYPE_ID ORDER BY inq.creation_date DESC;

Given its staging purpose, data in this table was often transient, with records being purged or archived after successful processing into downstream systems.

Related Objects

The IGR_IS_INQUIRY table has documented foreign key relationships with other staging tables in the obsolete IGS module, establishing its place in the data model. The key relationships are:

  • IGR_IS_PER_ALL: The column IGR_IS_INQUIRY.INQ_PERSON_ID references a corresponding person identifier in the IGR_IS_PER_ALL table. This join is essential for retrieving the demographic details (e.g., name, address) of the individual who made the inquiry.
  • Referential Integrity for Inquiry Type: The column IGR_IS_INQUIRY.INQUIRY_TYPE_ID is defined as a foreign key, though the specific referenced table (likely a lookup for inquiry types) is not fully named in the provided metadata, indicated by the "%" symbol.

The primary key constraint IGR_IS_INQUIRY_PK1 on INQ_INQ_ID ensures the uniqueness of each inquiry record and would be referenced by any foreign keys from dependent tables, though none are listed in the provided excerpt.