Search Results deliv_kit




Overview

IGR_I_ITYP_PKGS_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and defined in the application tier, typically associated with the Oracle iSetup / Information Type (IGR) and Oracle Marketing / Deliverables (AMS) functional areas. In the 12.1.1 and 12.2.2 releases, the view exposes a denormalised, join-ready representation of the relationship between deliverable kits, their component package items, and the Information Type definitions that classify them. Rather than forcing report developers and integration interfaces to reconstruct the multi-table hierarchy of IGR_I_PKG_ITEM, AMS_P_DELIV_KIT_ITEMS_V, and AMS_P_DELIVERABLES_V, the view presents a single flat result set that pairs each kit component with both its parent kit and its associated Information Type.

The presence of the search term deliv_kit in the underlying definition — through the AMS_P_DELIV_KIT_ITEMS_V alias KITEMS and the DELIVERABLE_KIT_ITEM_ID, DELIVERABLE_KIT_ID, and DELIVERABLE_KIT_PART_ID columns — confirms that this view is a primary access point for querying deliverable kit composition. It is therefore used in reporting and data-conversion scenarios where information types are packaged and delivered as kits.

Underlying Base Objects

The ETRM metadata documents the following referenced objects, all accessed through the APPS synonym layer:

  • IGR_I_PKG_ITEM — referenced twice, as aliases INFOTYPE and PKGITM. INSTANTIATES the Information Type and the package item (component) side of the relationship.
  • AMS_P_DELIV_KIT_ITEMS_V — alias KITEMS, supplying the kit header and kit component identifiers, kit names, part names, and audit columns.
  • AMS_P_DELIVERABLES_V — referenced twice as DELIV and DELIV_KIT, supplying descriptions and KIT_FLAG values for both the component and the parent kit.

Join predicates link INFOTYPE.PACKAGE_ITEM_ID to KITEMS.DELIVERABLE_KIT_ID and DELIV_KIT.DELIVERABLE_ID, and link PKGITM.PACKAGE_ITEM_ID to KITEMS.DELIVERABLE_KIT_PART_ID and DELIV.DELIVERABLE_ID. No base tables are documented beyond these view references, so the view functions as a stable abstraction over the AMS deliverables model.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling kit composition, validating that every deliverable kit part resolves to a valid Information Type, and feeding downstream reports that list kit contents.

SELECT information_type, package_item, package_item_desc
FROM   apps.igr_i_ityp_pkgs_v
WHERE  deliverable_kit_item_id = :kit_item_id;
SELECT package_item, package_item_desc, information_type
FROM   apps.igr_i_ityp_pkgs_v
WHERE  package_item_kit_flag = 'Y'
ORDER  BY information_type, package_item;

Because the view is a pure SELECT join with no filtering predicate, it returns all valid kit-to-information-type combinations; application-specific WHERE clauses should always be applied to limit result volume.