Search Results igs_ps_in_pkg_itm_pk




Overview

The IGS_PS_IN_PKG_ITM table is a core data entity within the Oracle E-Business Suite Student System (IGS) module. It functions as a junction table, defining the specific correspondence items that constitute an enquiry package for a given academic program (course). An enquiry package is a collection of documents or information items sent to prospective students. This table links a program version to one or more predefined correspondence items, which can be either system-generated or manually created. 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 for historical data integrity, its use in new development or business processes is deprecated, and it may be targeted for removal in future releases.

Key Information Stored

The table's structure is defined by a composite primary key, which uniquely identifies each record by linking a specific program version to a single enquiry item. The key columns are:

  • COURSE_CD: Stores the code identifying the academic program.
  • VERSION_NUMBER: Stores the version number of the specific program iteration.
  • ENQUIRY_PACKAGE_ITEM: Stores the identifier for a specific correspondence item (e.g., a brochure, application form, fee sheet) that is part of the package.

Together, these columns establish that a particular item is included in the enquiry package for a specific version of a program. The table does not store the content of the items themselves, but rather acts as a mapping table.

Common Use Cases and Queries

Given its obsolete status, primary use cases revolve around data migration, historical reporting, and supporting legacy integrations. A common analytical query would be to list all enquiry package items associated with a specific program to understand historical communication practices. For example:

SELECT epi.enquiry_package_item FROM igs_ps_in_pkg_itm pkg JOIN igs_ps_ver_all pv ON pkg.course_cd = pv.course_cd AND pkg.version_number = pv.version_number WHERE pv.course_cd = 'BSC_COMP_SCI';

Another typical pattern is verifying the existence of a mapping before performing a data purge or archive operation on related parent tables (IGS_PS_VER_ALL, IGS_IN_ENQ_PKG_ITEM) to maintain referential integrity.

Related Objects

The table's design centers on its foreign key relationships, which are essential for understanding its place in the data model and for constructing accurate joins in queries.

  • IGS_PS_VER_ALL (Program Version): This is the primary parent table. The IGS_PS_IN_PKG_ITM.COURSE_CD and VERSION_NUMBER columns reference the IGS_PS_VER_ALL table, ensuring that every package item mapping is for a valid, existing program version.
  • IGS_IN_ENQ_PKG_ITEM (Enquiry Package Item Definition): This is the secondary parent table. The IGS_PS_IN_PKG_ITM.ENQUIRY_PACKAGE_ITEM column references the IGS_IN_ENQ_PKG_ITEM table, ensuring that every mapped item is a defined and valid correspondence type within the system.

The table IGS_PS_IN_PKG_ITM itself has a primary key constraint named IGS_PS_IN_PKG_ITM_PK, which enforces the uniqueness of the combination of these three foreign key columns.