Search Results ams_deliv_kit_items




Overview
Explore in AI Chat

Overview

The AMS_DELIV_KIT_ITEMS table is a core data structure within the Oracle E-Business Suite Marketing (AMS) module, specifically for releases 12.1.1 and 12.2.2. It functions as the detailed repository for defining and managing marketing deliverable kits. In marketing operations, a deliverable kit is a logical grouping of multiple marketing collateral items, such as brochures, datasheets, and promotional items, that are distributed together as a single package for a campaign or event. This table stores the specific composition of these kits, defining exactly which individual collateral items (parts) are included. Its role is to maintain the integrity of kit definitions, enabling accurate planning, fulfillment, and tracking of complex marketing material distributions.

Key Information Stored

The table's primary purpose is to map relationships between a kit and its constituent parts. The key columns, as indicated by the provided metadata, are primarily foreign keys that establish these critical links. The DELIVERABLE_KIT_ITEM_ID serves as the unique primary key for each record in this intersection table. The DELIVERABLE_KIT_ID column references the parent kit deliverable, defined in the AMS_DELIVERABLES_ALL_B table. The DELIVERABLE_KIT_PART_ID column references each specific collateral item included in that kit, also stored in AMS_DELIVERABLES_ALL_B. A significant relational feature is the KIT_PART_INCLUDED_FROM_KIT_ID column, which allows for nested kit structures by referencing another kit deliverable. This enables the creation of complex kits that include sub-kits, providing flexibility in marketing material assembly.

Common Use Cases and Queries

This table is central to operations involving the assembly and analysis of marketing kits. A primary use case is generating a pick list or bill of materials for kit fulfillment, ensuring all correct collateral items are gathered. For reporting, it is used to analyze kit usage across campaigns or to audit kit compositions. Common SQL queries involve joining to the deliverables table to resolve IDs into meaningful item names and descriptions. For example, to list all items within a specific kit:

  • SELECT d2.DELIVERABLE_NAME AS Kit_Name, d1.DELIVERABLE_NAME AS Included_Item FROM AMS_DELIV_KIT_ITEMS kit JOIN AMS_DELIVERABLES_ALL_B d1 ON kit.DELIVERABLE_KIT_PART_ID = d1.DELIVERABLE_ID JOIN AMS_DELIVERABLES_ALL_B d2 ON kit.DELIVERABLE_KIT_ID = d2.DELIVERABLE_ID WHERE kit.DELIVERABLE_KIT_ID = :KIT_ID;

Another critical query pattern identifies nested kit relationships by checking for records where KIT_PART_INCLUDED_FROM_KIT_ID is not null.

Related Objects

The AMS_DELIV_KIT_ITEMS table has a tightly coupled relationship with the AMS_DELIVERABLES_ALL_B table, which is the master table for all marketing deliverables. As documented, all three foreign keys in AMS_DELIV_KIT_ITEMS (DELIVERABLE_KIT_ID, DELIVERABLE_KIT_PART_ID, KIT_PART_INCLUDED_FROM_KIT_ID) reference this single parent table. This design centralizes deliverable definitions. The table is also intrinsically linked to the broader Campaign Management and Marketing Execution functionalities within the AMS module. User interfaces for defining kits, such as forms or OA Framework pages, will ultimately persist data through this table. Reporting views and operational APIs for material fulfillment will heavily query this table to resolve kit contents.