Search Results kit_part_name

Overview

APPS.AMS_P_DELIV_KIT_ITEMS_V is a public Oracle E-Business Suite view owned by the APPS schema, classified in ETRM with a status of VALID. It is part of the Oracle Marketing (AMS) product family and exposes the relationship between collateral kits and the individual collateral deliverables that belong to those kits. In operational terms, a kit represents a grouped marketing deliverable, and the view flattens the kit-to-item association into a reporting-friendly structure so that each row describes one collateral item belonging to one kit, along with the kit's identity and the item's identity.

The view is documented by Oracle as "a public view which may be useful for custom reporting or other data requirements." It is therefore not an internal, private implementation object but an intentionally exposed interface suitable for customer-built reports, extracts, and integration queries. Its FND Design Data reference is AMS.AMS_P_DELIV_KIT_ITEMS_V, and the object is marked valid in both the 12.1.1 and 12.2.2 documentation sets. Because the view carries the standard WHO columns and an OBJECT_VERSION_NUMBER, it also supports change tracking and optimistic locking patterns in downstream customizations.

Underlying Base Objects

The documented view metadata for 12.2.2 identifies two referenced base objects:

• AMS_DELIVERABLES_VL (VIEW) — the multi-language deliverable definition view that supplies kit and collateral item naming and descriptive information.
• AMS_DELIV_KIT_ITEMS (SYNONYM) — the synonym over the delivery kit items entity that stores the kit-to-item membership records, including the unique kit item identifier and the associated kit and deliverable identifiers.

AMS_P_DELIV_KIT_ITEMS_V is thus a join-driven view: it resolves the raw kit item rows from AMS_DELIV_KIT_ITEMS against the deliverable master data in AMS_DELIVERABLES_VL to present both surrogate IDs and human-readable names in a single result set. The naming convention follows the AMS pattern in which _P_ denotes a public view intended for external consumption, distinguishing it from private implementation views. Report authors should treat AMS_P_DELIV_KIT_ITEMS_V as the supported access path rather than querying the underlying synonym or base tables directly.

Key Columns

The columns exposed by the view fall into four functional groups.

• Identity and locking: ROW_ID (ROWID), DELIVERABLE_KIT_ITEM_ID, and OBJECT_VERSION_NUMBER. DELIVERABLE_KIT_ITEM_ID is the unique identifier for the kit item row and is the natural join key back to the base entity.
• Kit context: DELIVERABLE_KIT_ID and KIT_NAME. The kit name is VARCHAR2(240) and provides the display value for the parent kit; the kit ID supports joins to kit-level objects.
• Collateral item context: DELIVERABLE_KIT_PART_ID and KIT_PART_NAME. This is the column family most relevant to a search on "kit_part_name": KIT_PART_NAME stores the name of the collateral item that belongs to the kit, and DELIVERABLE_KIT_PART_ID stores its identifier. QUANTITY is also present, documented as retained for upgrade purposes.
• WHO and descriptive flexfield columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, plus ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE13 (each VARCHAR2(150)), which carry the descriptive flexfield structure and segment values configured for kit items.

Common Use Cases and Queries

Typical uses include listing the components of a kit, reporting kit composition for collateral planning, driving pick lists or LOVs in custom forms, and reconciling kit contents during data migrations or upgrades. A representative query retrieving kit item detail by name is:

• SELECT kit_name, kit_part_name, deliverable_kit_id, deliverable_kit_part_id, quantity FROM apps.ams_p_deliv_kit_items_v WHERE kit_part_name = :p_kit_part_name;
• SELECT deliverable_kit_id, kit_name, COUNT(*) item_count FROM apps.ams_p_deliv_kit_items_v GROUP BY deliverable_kit_id, kit_name ORDER BY kit_name;
• SELECT attribute_category, attribute1, attribute2 FROM apps.ams_p_deliv_kit_items_v WHERE deliverable_kit_item_id = :p_id;

Note that the documented column list does not include an explicit ORGANIZATION_ID or ORG_ID, so the view is not partitioned by inventory organization. Queries should rely on the standard APPS synonym and MO or responsibility-level security inherited from the AMS application, and should filter on KIT_PART_NAME and KIT_NAME using the VARCHAR2(240) semantics to avoid implicit conversion issues.