Results for “pkg_description”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AD_INQ_PROG_PKG_ITEMS_V is an APPS-owned database view within the Oracle E-Business Suite IGS (Student System) product family. It exposes enquiry programme package item information by joining two underlying IGS tables, providing a denormalised, read-only presentation of package item records together with their descriptive text. The view is documented in ETRM as having a status of VALID at the database level, while the ETRM documentation content explicitly carries the notation "Obsolete." This dual state is significant: the object remains compiled and queryable in the EBS 12.1.1 / 12.2.2 database schemas, but Oracle has flagged the functional documentation as superseded.

The view's role in reporting and integration is that of a convenience or compatibility layer. Rather than requiring report developers and interfaces to join IGS_AD_I_PRG_PKG_ITM and IGS_IN_ENQ_PKG_ITEM manually, the view encapsulates that join and surfaces a stable column list including a PKG_DESCRIPTION attribute. Because the metadata marks the object obsolete, new development should treat it as a legacy artefact and seek the current replacement object; existing custom reports, Discoverer workbooks, BI Publisher data templates, and interfaces that reference it should be inventoried before any upgrade or patching activity.

Underlying Base Objects

Per the documented view text, IGS_AD_INQ_PROG_PKG_ITEMS_V is defined over exactly two base tables:

• IGS_AD_I_PRG_PKG_ITM (aliased IPP) — the primary enquiry programme package item table. It supplies the ROWID pseudo-column, the surrogate key INQ_PROG_PKG_ITEM_ID, the parent key INQ_PROG_CODE_ID, the foreign key ENQUIRY_PACKAGE_ITEM, the CLOSED_IND flag, and the standard WHO audit columns.
• IGS_IN_ENQ_PKG_ITEM (aliased IP) — the enquiry package item reference table, joined on the ENQUIRY_PACKAGE_ITEM column. It is the source of the descriptive text surfaced through the DESCRIPTION column.

The join is an equality join on IPP.ENQUIRY_PACKAGE_ITEM = IP.ENQUIRY_PACKAGE_ITEM. No outer-join syntax is present, so any enquiry package item that lacks a corresponding row in IGS_IN_ENQ_PKG_ITEM is excluded from the result set. Depending on the cardinality of ENQUIRY_PACKAGE_ITEM in the second table, the join may multiply rows; consumers should validate uniqueness assumptions before aggregating.

Key Columns

• ROW_ID — the ROWID of the IGS_AD_I_PRG_PKG_ITM row, exposed as ROWID for direct row addressing.
• INQ_PROG_PKG_ITEM_ID — unique identifier of the enquiry programme package item record.
• INQ_PROG_CODE_ID — foreign key linking the item to its enquiry programme code.
• ENQUIRY_PACKAGE_ITEM — the item code used as the join key between the two base tables.
• PKG_DESCRIPTION — the package item description. The view text selects IP.DESCRIPTION; the documented column list labels the output PKG_DESCRIPTION. This is the column most commonly searched for by report authors.
• CLOSED_IND — indicates whether the package item is closed; use it to filter active versus inactive items.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns, useful for change tracking and data lineage reporting.

Common Use Cases and Queries

Typical scenarios include reporting on open enquiry package items, exposing descriptions to downstream interfaces, and reconciling programme package definitions against enquiry package items.

SELECT inq_prog_pkg_item_id,
       inq_prog_code_id,
       enquiry_package_item,
       pkg_description,
       closed_ind
FROM   apps.igs_ad_inq_prog_pkg_items_v
WHERE  closed_ind = 'N'
ORDER  BY inq_prog_code_id, enquiry_package_item;

Audit-oriented queries take advantage of the WHO columns:

SELECT enquiry_package_item,
       pkg_description,
       last_updated_by,
       last_update_date
FROM   apps.igs_ad_inq_prog_pkg_items_v
WHERE  last_update_date >= TRUNC(SYSDATE) - 30;

Because the object is documented as obsolete, any new enquiry package item reporting should be validated against the current IGS data model before reuse, and existing dependents of this view should be reviewed during upgrade or patch cycles.