Results for “kit_flag”

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

Overview

AMS_P_EVENT_DELIVERABLES_V is a public (APPS-owned) database view in the Oracle E-Business Suite Marketing (AMS) module. It consolidates marketing deliverables associated with event offers, including collaterals tied to marketing events, into a single queryable structure. The view joins object-association data to both the event-offer and deliverable definitions, so it exposes the complete relationship between an event offer and the deliverables assigned to it. In Oracle EBS 12.1.1 and 12.2.2 it is a read-only reporting and integration object; it carries no DML of its own and reflects the current state of the underlying AMS tables and views at query time. Marketers, integration developers, and BI/report authors use it whenever they need to answer which deliverables (and which categories of fulfillment) belong to a given event offer.

Underlying Base Objects

The view is defined over three documented referenced objects in the APPS schema:

• AMS_OBJECT_ASSOCIATIONS (synonym) — the association table that links a master object (the event offer) to a using object (the deliverable).
• AMS_EVENT_OFFERS_VL (view) — the event offer, supplying the offer name and description.
• AMS_P_DELIVERABLES_V (view) — the deliverable definition, supplying name, language, category, and the electronic/physical fulfillment flags.

The join predicates are A.MASTER_OBJECT_ID = E.EVENT_OFFER_ID and A.USING_OBJECT_ID = D.DELIVERABLE_ID. Because the view is built on other views rather than directly on base tables, its results inherit the security and filtering logic already applied by AMS_EVENT_OFFERS_VL and AMS_P_DELIVERABLES_V, and any change to those underlying definitions propagates to consumers of this view.

Key Columns

• ROW_ID — the ROWID of the association record, useful for de-duplication and direct reference.
• EVENT_OFFER_ID / EVENT_OFFER_NAME / EVENT_OFFER_DESCRIPTION — the master event offer to which the deliverable is linked.
• DELIVERABLE_ID / DELIVERABLE_NAME / DELIVERABLE_DESCRIPTION / DELIVERABLE_LANGUAGE_CODE — the assigned deliverable and its descriptive attributes.
• CAN_FULFILL_ELECTRONIC_FLAG — indicates whether the deliverable can be fulfilled electronically; directly relevant to the searched term "can_fulfill_electronic_flag."
• CAN_FULFILL_PHYSICAL_FLAG — indicates whether the deliverable can be fulfilled physically.
• DELIVERABLE_CATEGORY / DELIVERABLE_SUB_CATEGORY — classification used for filtering and grouping deliverables.
• INVENTORY_FLAG, DELV_INVENTORY_ITEM_ID, DELV_INVENTORY_ITEM_ORG_ID, KIT_FLAG — inventory-related attributes linking the deliverable to an inventory item, organization, and kit designation.

Common Use Cases and Queries

Typical scenarios include identifying all deliverables assigned to a specific event offer, determining which deliverables are electronically fulfillable, and reporting on collateral categories for campaign planning or fulfillment integration. Typical usage patterns include search screens, concurrent reports, and interface programs that need offer-to-deliverable mappings.

Electronically fulfillable deliverables for an event offer:

SELECT event_offer_name,
       deliverable_name,
       can_fulfill_electronic_flag,
       can_fulfill_physical_flag,
       deliverable_category
  FROM apps.ams_p_event_deliverables_v
 WHERE can_fulfill_electronic_flag = 'Y'
   AND event_offer_id = :p_event_offer_id;

List all deliverables by category for a given offer:

SELECT event_offer_name,
       deliverable_name,
       deliverable_category,
       deliverable_sub_category,
       language_code,
       inventory_flag
  FROM apps.ams_p_event_deliverables_v
 WHERE event_offer_id = :p_event_offer_id
 ORDER BY deliverable_category, deliverable_name;

Because the object is a view, no INSERT, UPDATE, or DELETE should be issued against it; DML belongs to the underlying AMS tables. Applications should filter with the exposed event-offer and deliverable keys, use CAN_FULFILL_ELECTRONIC_FLAG and CAN_FULFILL_PHYSICAL_FLAG for fulfillment logic, and treat inventory-related columns as read-only references. Note that in published ETRM metadata the column names on the deliverable view appear as DELIVERABLE_ID and DELIVERABLE_NAME, while inventory columns are exposed as DELV_INVENTORY_ITEM_ID and DELV_INVENTORY_ITEM_ORG_ID; always verify actual column names against the deployed 12.1.1 or 12.2.2 definitions before building dependent code.