Search Results igs_rc_i_a_pkgitm

Overview

The table IGS_RC_I_A_PKGITM is a core data object within the Oracle E-Business Suite Student System (IGS). It functions as a junction table that stores the specific details linking an applicant's enquiry or application to the predefined package items offered by the institution. Its primary role is to manage the association between an applicant's record and the constituent items of an enquiry package, enabling the tracking of which specific program, course, or offering components a prospective student has expressed interest in through their application. This table is critical for supporting the admissions and recruitment processes by maintaining a granular record of applicant choices within packaged offerings.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each record, ensuring a single package item is linked to a specific application only once. The key columns are ENQUIRY_APPL_NUMBER and PERSON_ID, which together identify the specific application, and PACKAGE_ITEM_ID, which identifies the selected item from a package. While the provided metadata does not list non-key columns, the table's purpose suggests it may also store metadata such as creation date, last update date, and potentially sequence or status information for the items within the context of the application. The essential data it holds is the relationship itself between an application entity and a package item entity.

Common Use Cases and Queries

A primary use case is generating reports on the popularity of specific package items among applicants, aiding in curriculum planning and marketing efforts. Support staff may query this table to verify or audit the complete list of items a prospective student has applied for within a package. Common SQL patterns involve joining to the related application and package item tables to retrieve descriptive information. For example, to list all package items for a specific application, a query would join IGS_RC_I_A_PKGITM to IGS_RC_I_APPL_ALL on the person and application number, and to IGS_RC_I_PKG_ITEM on the package item ID to get item details.

SELECT appl.enquiry_appl_number,
       pkgitm.package_item_code,
       pkgitm.description
FROM igs_rc_i_a_pkgitm link
JOIN igs_rc_i_appl_all appl
  ON link.person_id = appl.person_id
 AND link.enquiry_appl_number = appl.enquiry_appl_number
JOIN igs_rc_i_pkg_item pkgitm
  ON link.package_item_id = pkgitm.package_item_id
WHERE appl.person_id = :1
  AND appl.enquiry_appl_number = :2;

Related Objects

The table IGS_RC_I_A_PKGITM has defined foreign key relationships with two primary tables in the IGS module, as documented in the ETRM metadata:

• IGS_RC_I_APPL_ALL: This is the core application table. The relationship is established via the columns IGS_RC_I_A_PKGITM.PERSON_ID and IGS_RC_I_A_PKGITM.ENQUIRY_APPL_NUMBER referencing the corresponding columns in IGS_RC_I_APPL_ALL. This ensures every package item record is tied to a valid application.
• IGS_RC_I_PKG_ITEM: This table stores the master definition of available package items. The relationship is via the column IGS_RC_I_A_PKGITM.PACKAGE_ITEM_ID referencing IGS_RC_I_PKG_ITEM.PACKAGE_ITEM_ID. This links the applicant's selection to the specific catalog item.

These relationships enforce referential integrity and are essential for any query that needs to display application or package item descriptions alongside the linkage data.