Search Results igr_i_inquiry_types




Overview
Explore in AI Chat

Overview

The IGR_I_INQUIRY_TYPES table is a core setup table within the now-obsolete IGS (Student System) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. Its primary function is to store the master definition of inquiry types, which are classifications used to categorize and manage prospective student inquiries or leads within the student lifecycle management system. This table acts as a reference entity, providing a controlled list of valid inquiry types that can be associated with individual prospect records to streamline communication, reporting, and processing workflows. The ETRM metadata explicitly notes this table as "Not implemented in this database," indicating it may have been part of a localized or phased implementation not present in the standard vanilla instance.

Key Information Stored

While the specific column list is not detailed in the provided excerpt, the table's structure is defined by its primary and foreign keys. The central column is INQUIRY_TYPE_ID, which serves as the unique primary key identifier for each inquiry type record. The table also contains foreign key columns that link to other setup entities, ensuring data integrity. The column IMP_SOURCE_TYPE_ID links to the source type (IGS_PE_SRC_TYPES_ALL), likely defining the origin or channel of the inquiry. The column INFO_TYPE_ID links to a package item (IGR_I_PKG_ITEM), which may associate the inquiry type with specific informational materials or follow-up processes. Additional columns, typical for such setup tables, would store the inquiry type code, name, description, and active status indicators.

Common Use Cases and Queries

The primary use case is to maintain a consistent list of inquiry types for application setup and data validation. Common operational and reporting activities would involve querying this table to generate lookup lists for user interfaces or to analyze prospect data by inquiry category. A typical query would join this table to prospect transaction tables (not listed in the provided metadata) to report on inquiry volumes.

  • Basic Lookup: SELECT inquiry_type_id, inquiry_type_code, meaning FROM igr_i_inquiry_types WHERE sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate);
  • Join to Source Type: SELECT i.inquiry_type_code, s.source_type FROM igr_i_inquiry_types i, igs_pe_src_types_all s WHERE i.imp_source_type_id = s.source_type_id;

Related Objects

Based on the documented foreign key relationships, IGR_I_INQUIRY_TYPES has direct dependencies on two other setup tables. These relationships are critical for understanding its place in the data model.

  • IGS_PE_SRC_TYPES_ALL: Linked via the IMP_SOURCE_TYPE_ID column. This table defines valid source types, allowing an inquiry type to be associated with a specific recruitment or marketing source.
  • IGR_I_PKG_ITEM: Linked via the INFO_TYPE_ID column. This table likely stores package items, suggesting an inquiry type can be configured to trigger the sending of specific information packages to prospects.

As a setup table with a primary key, it is expected that other transactional tables in the IGS module (e.g., tables storing individual prospect records) would contain a foreign key column referencing IGR_I_INQUIRY_TYPES.INQUIRY_TYPE_ID, though these are not specified in the provided metadata.