Search Results inq_u_set_pkg_item_id

Overview

The IGS_AD_I_UST_PKG_ITM table is a data structure within the Oracle E-Business Suite (EBS) Student System (IGS) module. Its primary role was to manage the relationship between inquiry unit set codes and specific items within an inquiry package. This table functioned as a junction or intersection entity, linking the configuration of academic unit sets for prospective student inquiries to the broader components of an inquiry package. As explicitly noted in the official ETRM documentation, this table is marked as Obsolete. This status indicates that while the table may still physically exist in the database for historical data retention or upgrade compatibility in versions 12.1.1 and 12.2.2, its associated business logic is no longer actively maintained or used by the application's standard processes. Its presence is typically for referential integrity and to prevent data loss during system upgrades.

Key Information Stored

The table's structure is designed to store the core identifiers necessary to establish the relationship between two key entities. The most critical columns include:

• INQ_U_SET_PKG_ITEM_ID: This column serves as the table's unique primary key (PK), ensuring each record in this intersection table is uniquely identifiable.
• INQ_UNIT_SET_CODE_ID: A foreign key column that references a specific inquiry unit set code defined in the IGS_AD_INQ_UNIT_SETS table. This represents the academic program or course structure of interest to an enquirer.
• ENQUIRY_PACKAGE_ITEM: A foreign key column that references a specific item within an inquiry package stored in the IGS_IN_ENQ_PKG_ITEM table. This item could represent informational materials, application forms, or other resources bundled for prospective students.

The table also enforces a unique key constraint on the combination of INQ_UNIT_SET_CODE_ID and ENQUIRY_PACKAGE_ITEM, preventing duplicate associations from being created.

Common Use Cases and Queries

Given its obsolete status, direct operational or transactional use of this table in a live EBS environment is highly unlikely. Its primary contemporary use cases are analytical and administrative. Technical consultants and DBAs might query it for data migration validation, historical reporting, or during cleanup activities. A typical query would involve joining the table to its parent entities to understand historical data relationships.

Sample Query Pattern:
SELECT iustpi.*, ius.unit_set_code, epi.item_code
FROM igs.igs_ad_i_ust_pkg_itm iustpi
JOIN igs.igs_ad_inq_unit_sets ius ON iustpi.inq_unit_set_code_id = ius.inq_unit_set_code_id
JOIN igs.igs_in_enq_pkg_item epi ON iustpi.enquiry_package_item = epi.enquiry_package_item_id
WHERE ius.unit_set_code = '&UNIT_SET_CODE';
This query retrieves all historical package items that were once associated with a given unit set code.

Related Objects

The table's integrity is defined by its relationships with two parent tables in the IGS schema, as documented in the ETRM metadata:

• IGS_AD_INQ_UNIT_SETS: This is the primary parent table for inquiry unit set definitions. The relationship is established via the foreign key IGS_AD_I_UST_PKG_ITM.INQ_UNIT_SET_CODE_ID referencing the IGS_AD_INQ_UNIT_SETS table.
• IGS_IN_ENQ_PKG_ITEM: This is the primary parent table for inquiry package item definitions. The relationship is established via the foreign key IGS_AD_I_UST_PKG_ITM.ENQUIRY_PACKAGE_ITEM referencing the IGS_IN_ENQ_PKG_ITEM table.

These relationships confirm the table's role as a pure intersection entity between these two master data objects. There are no documented foreign keys where other tables reference IGS_AD_I_UST_PKG_ITM, which is consistent with its obsolete nature.