Search Results igs_in_lvltyp_pkg_it_pk

Overview

The table IGS_IN_LVLTYP_PKG_IT is a core data entity within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically belonging to the now-obsolete IGS (Student System) module. Its primary function was to manage the association between different levels of student or institutional enquiries and the specific information packages available at each level. This table served as a configuration or mapping table, defining which enquiry package items—such as fees information, course details, or admission requirements—were relevant and accessible for a given enquiry level type, for example, a faculty-level enquiry versus an institution-wide enquiry. It is critical to note that the provided metadata explicitly states this object is "Obsolete" and was "Not implemented in this database," indicating it was part of a defined data model but may not have been deployed in active production instances.

Key Information Stored

The table's structure is defined by a composite primary key, which dictates the fundamental data it holds. The two key columns are S_ENQUIRY_LEVEL_TYPE and ENQUIRY_PACKAGE_ITEM. The S_ENQUIRY_LEVEL_TYPE column stores a code representing the classification or tier of an enquiry (e.g., 'INSTITUTION', 'FACULTY', 'DEPARTMENT'). The ENQUIRY_PACKAGE_ITEM column holds an identifier that links to a specific item of information defined in the related IGS_IN_ENQ_PKG_ITEM table. Together, each row constitutes a rule granting a specific enquiry level access to a particular package item. No other column details are provided in the excerpt, suggesting these two fields were the sole carriers of business data within this entity.

Common Use Cases and Queries

In a functional context, this table would be queried to determine the suite of information items permissible for a given enquiry context. A typical use case involved dynamically building enquiry forms or report outputs where content was filtered based on the user's enquiry level. For instance, an administrative user initiating a faculty-level enquiry would be presented only with package items tagged to the 'FACULTY' level. A common SQL pattern would involve joining to the IGS_IN_ENQ_PKG_ITEM table to retrieve the descriptive details of the allowed items. A sample query would be: SELECT pkg_item.* FROM igs_in_lvltyp_pkg_it map, igs_in_enq_pkg_item pkg_item WHERE map.enquiry_package_item = pkg_item.enquiry_package_item AND map.s_enquiry_level_type = :p_enquiry_level; This table was foundational for enforcing data visibility and presentation rules within the obsolete enquiry management subsystem.

Related Objects

Based on the documented foreign key relationships, IGS_IN_LVLTYP_PKG_IT has a direct and singular dependency on the table IGS_IN_ENQ_PKG_ITEM. The relationship is established through the ENQUIRY_PACKAGE_ITEM column, which is a foreign key in IGS_IN_LVLTYP_PKG_IT referencing the primary key of IGS_IN_ENQ_PKG_ITEM. This relationship ensures referential integrity, meaning a package item must be defined in the master IGS_IN_ENQ_PKG_ITEM table before it can be assigned to an enquiry level type. The provided metadata lists this foreign key relationship twice, which is likely a documentation artifact. There are no other documented foreign keys pointing to or from this table in the provided excerpt. The table's primary key constraint is named IGS_IN_LVLTYP_PKG_IT_PK.