Search Results ams_p_deliv_kit_items_v




Overview
Explore in AI Chat

Overview

AMS_P_DELIV_KIT_ITEMS_V is a public (non-registered) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS – Marketing product family. Its documented purpose is to return the collateral items associated with collateral kits. In OEB terminology, a "deliverable" represents a piece of collateral (a brochure, datasheet, or marketing asset), and a "deliverable kit" groups multiple deliverables into a single packaged set. This view flattens that parent/child relationship so that each row represents one kit item — a single collateral component assigned to a parent kit — together with the descriptive names of both the kit and the component.

The view is validated in both 12.1.1 and 12.2.2 and is exposed in the ETRM (Electronic Technical Reference Manual) with its full column list and view text. Because it is a public view in the APPS schema, it is intended for customer reporting and integration consumption rather than for internal product code alone. Report developers, OBIEE/BI Publisher authors, and integration developers use it as a stable, denormalized read path over the underlying kit-item entity, avoiding the need to join to the deliverables multi-language table (AMS_DELIVERABLES_VL) manually to resolve names.

Underlying Base Objects

The documented base objects referenced by the view are:

Because AMS_DELIVERABLES_VL is joined twice under aliases D1 and D2, the view performs a star-like denormalization: the kit name and the kit-part name are both surfaced without requiring the caller to issue two separate lookups. This is the key relationship to note — each kit item row depends on two distinct deliverable records.

Key Columns

  • ROW_ID — the ROWID of the underlying kit-items row; unique identifier for a kit item.
  • DELIVERABLE_KIT_ITEM_ID — primary key of the kit item.
  • DELIVERABLE_KIT_ID / KIT_NAME — the parent kit's ID and resolved name.
  • DELIVERABLE_KIT_PART_ID / KIT_PART_NAME — the component deliverable's ID and resolved name. This is the column the user searched for; it is the foreign key identifying which deliverable is used as a part within the kit.
  • QUANTITY — number of units of the component deliverable contained in the kit.
  • OBJECT_VERSION_NUMBER — optimistic locking version, important for any programmatic update path.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the flexible descriptive flexfield (DFF) segment columns, available for customer-defined data.

Common Use Cases and Queries

Typical uses include listing all components of a specific kit, confirming which deliverables are packaged within a kit for fulfillment, and extracting kit contents into a reporting or BI layer. A representative query retrieving all items for a given kit:

  • SELECT DELIVERABLE_KIT_ITEM_ID, KIT_NAME, DELIVERABLE_KIT_PART_ID, KIT_PART_NAME, QUANTITY FROM APPS.AMS_P_DELIV_KIT_ITEMS_V WHERE DELIVERABLE_KIT_ID = :p_kit_id ORDER BY KIT_PART_NAME;
  • SELECT KIT_NAME, COUNT(*) item_count, SUM(QUANTITY) total_qty FROM APPS.AMS_P_DELIV_KIT_ITEMS_V GROUP BY KIT_NAME;
  • SELECT k.DELIVERABLE_KIT_PART_ID, k.KIT_PART_NAME FROM APPS.AMS_P_DELIV_KIT_ITEMS_V k WHERE k.KIT_NAME LIKE :kit_name;

When filtering on DFF values, remember the view returns all fifteen segments plus ATTRIBUTE_CATEGORY, so segment naming must be resolved against the AMS DFF setup. Because the view reads through AMS_DELIVERABLES_VL, it returns only kit items whose kit and component deliverable records are both resolvable, and rows may reflect translation-dependent names.