Search Results igs_in_enq_info_type




Overview
Explore in AI Chat

Overview

The table IGS_IN_ENQ_INFO_TYPE is a core entity within the Oracle E-Business Suite (EBS) Student System (IGS) module. It functions as a reference table designed to categorize the various types of information requests or enquiries made by prospective or current students. These enquiry types are typically user-defined, covering areas such as travel, fees, accommodation, courses, and faculty. A critical exception is a system-defined type for 'all information'. It is important to note that the official ETRM documentation explicitly marks this table as "Obsolete." This status indicates that while the table may exist in the database schema for backward compatibility, its use in new development or customizations is discouraged, and it may be subject to removal or replacement in future releases.

Key Information Stored

The primary data stored in this table is the distinct classification of enquiry types. Based on the provided metadata, the central column is ENQUIRY_INFORMATION_TYPE, which serves as the table's primary key (PK). This column holds the unique code or identifier for each type of enquiry. While the specific data type and length are not detailed in the excerpt, it is a standard pattern for such key columns to be of type VARCHAR2. The table's description suggests it is a simple lookup entity, implying it likely contains a column for a description (e.g., ENQUIRY_INFORMATION_DESC) to provide a meaningful name for each type code, though this is not explicitly listed in the provided metadata.

Common Use Cases and Queries

In its operational context, this table was used to standardize and control the classification of student enquiries across the application. Common use cases included configuring valid enquiry types during system setup and generating reports categorizing student interactions by type. Given its obsolete status, direct queries for new functionality are not recommended. However, historical analysis or data migration scripts might reference it. A typical query pattern to retrieve all defined enquiry types would be:

  • SELECT enquiry_information_type FROM igs.igs_in_enq_info_type ORDER BY 1;

Joins to related application data would utilize the primary key, for example, to count enquiries by type before the table's deprecation.

Related Objects

The integrity of the IGS_IN_ENQ_INFO_TYPE table is enforced through its primary key and several foreign key (FK) relationships, as documented in the ETRM. The primary key constraint is named IGS_IN_ENQ_INFO_TYPE_PK. The following tables reference IGS_IN_ENQ_INFO_TYPE, establishing it as a parent lookup table in these relationships:

  • IGS_IN_APPLINFO_TYPE: References via its column ENQUIRY_INFORMATION_TYPE.
  • IGS_IN_INFTYP_PKG_IT: References via its column ENQUIRY_INFORMATION_TYPE (listed twice in the metadata, likely indicating two separate foreign key constraints from the same child table).

These relationships mean that the ENQUIRY_INFORMATION_TYPE values stored in the child tables must exist as valid codes in the IGS_IN_ENQ_INFO_TYPE table, ensuring referential integrity for enquiry type data.