Search Results package_item_id




Overview
Explore in AI Chat

Overview

The IGR_I_PKG_ITEM table is a junction table within the Oracle E-Business Suite's IGS (Student System) module, which is designated as obsolete in releases 12.1.1 and 12.2.2. Its primary architectural role is to establish a many-to-many relationship between package items and information types within the context of inquiry management. The table acts as a bridge, linking the OMO (Oracle Marketing Online) deliverables table (AMS_DELIVERABLES_ALL_B) with student inquiry type classifications (IGR_I_INQUIRY_TYPES). This design allows a single package item (e.g., a marketing brochure or email template) to be associated with multiple inquiry information types, and vice versa, facilitating targeted communication and resource management for student inquiries.

Key Information Stored

Based on the provided ETRM metadata, the table's structure is centered around its primary and foreign key columns. The core column is PACKAGE_ITEM_ID, which serves as the table's primary key. This identifier directly links each record to a specific deliverable in the AMS_DELIVERABLES_ALL_B table. While the full column list is not detailed in the excerpt, the table's description indicates it stores both "Package Item and information Type." Therefore, a second critical column would logically hold the INFO_TYPE_ID, which is referenced as the foreign key column from the IGR_I_INQUIRY_TYPES table. Each row in IGR_I_PKG_ITEM thus represents a unique association between one package item and one inquiry information type.

Common Use Cases and Queries

This table supports operational and reporting needs related to configuring and auditing inquiry response materials. A common use case is retrieving all marketing deliverables configured for a specific category of student inquiry. For example, an administrator might need to list all email templates (package items) associated with inquiries regarding graduate programs (an information type). A typical SQL query would join these three tables:

  • To list all package items for a given inquiry type name: SELECT d.deliverable_name FROM ams_deliverables_all_b d JOIN igr_i_pkg_item pki ON d.deliverable_id = pki.package_item_id JOIN igr_i_inquiry_types it ON pki.info_type_id = it.info_type_id WHERE it.type_name = 'GRADUATE_INQUIRIES';
  • To audit all associations for reporting: SELECT it.type_name, d.deliverable_name, d.deliverable_id FROM igr_i_inquiry_types it, igr_i_pkg_item pki, ams_deliverables_all_b d WHERE it.info_type_id = pki.info_type_id AND pki.package_item_id = d.deliverable_id ORDER BY 1, 2;

Related Objects

The IGR_I_PKG_ITEM table is centrally connected to two key tables via foreign key relationships, as documented in the ETRM:

  • AMS_DELIVERABLES_ALL_B: This is the master table for marketing deliverables in the OMO component. The relationship is defined as IGR_I_PKG_ITEM.PACKAGE_ITEM_ID referencing a column (typically DELIVERABLE_ID) in AMS_DELIVERABLES_ALL_B. This links the junction record to the actual content item.
  • IGR_I_INQUIRY_TYPES: This table defines the classifications or categories for student inquiries. The relationship is defined with IGR_I_INQUIRY_TYPES.INFO_TYPE_ID referencing the corresponding column in IGR_I_PKG_ITEM. This links the junction record to the inquiry classification.

It is critical to note the ETRM explicitly states this table is "Not implemented in this database" for the searched instance, indicating it is part of the data model but may not be populated or actively used in a given deployment.