Results for “pkg_item_desc”

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

Overview

IGR_I_PKGITM_ASSIGN_V is a form-driven database view defined within the Oracle E-Business Suite Student System module (product code IGS). Its stated purpose, per the ETRM documentation, is to serve as the "Form view for IGR_I_PKGITM_ASSIGN table." In other words, it is a presentation-layer view constructed to feed an Oracle Forms-based user interface that manages the assignment of package items to product categories. Rather than exposing a single flat table, the view enriches the base assignment records with descriptive denormalized attributes drawn from auxiliary product and deliverable sources, so that a form block can display human-readable labels alongside surrogate identifiers.

The object belongs to the IGS - Student System (Obsolete) product line. The "Obsolete" designation signals that the module is legacy and that the view is retained principally for backward compatibility with existing forms and any dependent customizations. The ETRM metadata notes that the view is "Not implemented in this database," meaning the exact installation being documented did not contain the object, though its definition remains catalogued. Administrators should confirm actual existence in their instance before building reports against it.

Underlying Base Objects

The view text references three sources, joined on package item and category identifiers:

• IGR_I_PKGITM_ASSIGN (aliased PIA) — the primary base table recording the assignment of a package item to a product category, including the enabled flag and audit columns.
• AMS_P_DELIVERABLES_V (aliased PKGITM) — a deliverables view in the marketing/product domain, supplying the deliverable name and description for the package item.
• ENI_PROD_DEN_HRCHY_PARENTS_V (aliased DENORM) — a denormalized product category hierarchy view that provides the concatenated parentage description and the individual category description.

Although the ETRM metadata lists no documented referenced base objects, the view definition itself makes the join relationships explicit: PIA.PACKAGE_ITEM_ID equals PKGITM.DELIVERABLE_ID, and PIA.PRODUCT_CATEGORY_ID equals DENORM.CATEGORY_ID. This means the view is only as reliable as the availability and population of the AMS and ENI helper views, which reside in adjacent product schemas.

Key Columns

• ROW_ID — the ROWID of the underlying assignment table row, used by Forms for row-level locking.
• PKG_ITEM_ASSIGN_ID — primary key of the assignment record.
• PRODUCT_CATEGORY_ID / PRODUCT_CATEGORY_SET_ID — identifiers tying the assignment to a category and its set.
• CONCATENATED_PRODUCT_CAT_DESC — a denormalized full hierarchy path. The DECODE/GREATEST/SUBSTR logic caps the string at 2,000 characters, retaining the deepest 2,000 when the concatenation is longer, so the display always shows the leaf-most portion of the path.
• PRODUCT_CATEGORY_DESC — the category's own description.
• PACKAGE_ITEM_ID / PACKAGE_ITEM / PKG_ITEM_DESC — the deliverable identifier, name, and description sourced from the deliverables view.
• ENABLED_FLAG — indicates whether the assignment is active.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

The view supports form rendering and related diagnostic reporting. A typical query retrieves active assignments with readable descriptions:

• SELECT pkg_item_assign_id, package_item, product_category_desc, concatenated_product_cat_desc FROM igr_i_pkgitm_assign_v WHERE enabled_flag = 'Y';
• Validation of audit trails: SELECT pkg_item_assign_id, last_updated_by, last_update_date FROM igr_i_pkgitm_assign_v ORDER BY last_update_date DESC;
• Hierarchy inspection: SELECT package_item, concatenated_product_cat_desc FROM igr_i_pkgitm_assign_v WHERE product_category_id = :category_id;

Because the module is obsolete and the view is often unimplemented, consultants should treat it as a reference artifact and verify its presence, grants, and dependent views before relying on it in production reporting.