Search Results igs_in_inftyp_pkg_it

Overview

The table IGS_IN_INFTYP_PKG_IT is a core data entity within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically in the IGS (Student System) product family. Its primary function is to define the association between different enquiry information types and the specific enquiry package items available for each. This mapping enables the structured configuration of enquiry data, such as linking a "fees" information type to relevant items like a course fee enquiry or a general fees enquiry. It is critical 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 associated business logic is likely deprecated, and it should not be used for new customizations or integrations.

Key Information Stored

The table's structure is defined by a composite primary key, ensuring a unique relationship between its two core columns. It does not store transactional data but rather configuration metadata that governs enquiry behavior within the Student System.

• ENQUIRY_INFORMATION_TYPE: This column stores a code or identifier for a category of enquiry information (e.g., FEES, ADMISSIONS). It is a foreign key referencing the IGS_IN_ENQ_INFO_TYPE table, which holds the master list of valid information types.
• ENQUIRY_PACKAGE_ITEM: This column stores a code or identifier for a specific enquiry item or data point within a package. It is a foreign key referencing the IGS_IN_ENQ_PKG_ITEM table, which defines the available enquiry items.

The combination of these two columns forms the primary key (IGS_IN_INFTYP_PKG_IT_PK), establishing a many-to-many relationship between information types and package items.

Common Use Cases and Queries

Given its obsolete status, active development or reporting directly against this table is discouraged. However, understanding its historical purpose is valuable for maintaining or analyzing legacy configurations. Its primary use was to answer: "What specific enquiry items are available for a given type of information?" A typical analytical query would involve joining to its parent tables to retrieve descriptive names.

Sample SQL Pattern:
SELECT inf.INFORMATION_TYPE_NAME,
pkg.ITEM_NAME
FROM IGS.IGS_IN_INFTYP_PKG_IT map
JOIN IGS.IGS_IN_ENQ_INFO_TYPE inf ON inf.ENQUIRY_INFORMATION_TYPE = map.ENQUIRY_INFORMATION_TYPE
JOIN IGS.IGS_IN_ENQ_PKG_ITEM pkg ON pkg.ENQUIRY_PACKAGE_ITEM = map.ENQUIRY_PACKAGE_ITEM
WHERE inf.INFORMATION_TYPE_NAME = 'FEES';
This query would list all package items configured for the 'FEES' information type. For any operational requirement, consultants must verify the current, supported API or data model, as this table's logic may have been superseded.

Related Objects

The table's integrity is maintained through defined foreign key relationships, as documented in the ETRM. It is a child table that references two master tables.

• IGS_IN_ENQ_INFO_TYPE: Master table for Enquiry Information Types. IGS_IN_INFTYP_PKG_IT references it via the column ENQUIRY_INFORMATION_TYPE.
• IGS_IN_ENQ_PKG_ITEM: Master table for Enquiry Package Items. IGS_IN_INFTYP_PKG_IT references it via the column ENQUIRY_PACKAGE_ITEM.

These relationships enforce referential integrity, ensuring that only valid, pre-defined information types and package items can be associated within the IGS_IN_INFTYP_PKG_IT table.