Search Results jtf_amv_item

Overview

APPS.AMS_P_DELIVERABLES_V is a public Oracle EBS view owned by the APPS schema, registered under FND Design Data AMS.AMS_P_DELIVERABLES_V and reported with a status of VALID. It belongs to the Oracle Marketing (AMS) product family and exposes marketing deliverable information in a denormalized, reporting-friendly form. Deliverables in AMS represent the tangible or electronic items fulfilled as part of a campaign or event — collateral, kits, premiums, and similar materials — together with their categorization, ownership, status, and funding context.

Because it is documented as "a public view which may be useful for custom reporting or other data requirements," the object is intended for direct consumption by customer-written queries, extracts, and downstream integrations rather than being restricted to internal application code. This makes it a stable access point for reporting on the marketing deliverable catalog without requiring joins against the more normalized underlying entities. The view is consistent with the ETRM 12.2.2 documentation set and also applies to the 12.1.1 code line, where the same AMS deliverable model is in use.

A notable relationship exists between this deliverable view and the JTF_AMV_ITEM entity referenced in the search that led to this object. Deliverables and their related media or reference items participate in the same AMS marketing infrastructure, so queries against AMS_P_DELIVERABLES_V are frequently combined with item-level lookups when reporting on deliverable content and associations.

Underlying Base Objects

The documented view metadata lists four referenced base objects, all resolved through the APPS schema:

• AMS_DELIVERABLES_VL (VIEW) — the primary transactional source supplying deliverable identifiers, version, ownership, status, funding source, category, and flag attributes. The _VL suffix indicates a translated view, which is why the outer view carries a LANGUAGE_CODE column.
• AMS_USER_STATUSES_VL (VIEW) — provides the user-defined status name exposed as USER_STATUS and the associated USER_STATUS_ID.
• AMS_CATEGORIES_TL (SYNONYM) — the translated category table supplying category and sub-category descriptions such as DELIVERABLE_CATEGORY and DELIVERABLE_SUB_CATEGORY.
• AMS_JTF_RS_EMP_V (VIEW) — the resource/employee view used to resolve the OWNER display name from OWNER_USER_ID.

The view therefore performs the join and translation work on behalf of the caller, presenting resolved names alongside raw identifiers.

Key Columns

The view exposes a compact but complete set of attributes. Identity and audit columns include DELIVERABLE_ID (unique identifier), OBJECT_VERSION_NUMBER (locking), and the standard WHO columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. LANGUAGE_CODE indicates the language into which translatable fields are resolved, and VERSION carries the deliverable version.

Behavioral flags include ACTIVE_FLAG, PRIVATE_FLAG, KIT_FLAG (deliverable contains other deliverables), and CAN_FULFILL_ELECTRONIC_FLAG. Status information is available both as USER_STATUS_ID/USER_STATUS and as STATUS_CODE/STATUS_DATE. Ownership is expressed as OWNER_USER_ID with the resolved OWNER name. Funding context is captured by FUND_SOURCE_ID and FUND_SOURCE_TYPE, which may reference a campaign or an event. Categorization is provided by CATEGORY_TYPE_ID/DELIVERABLE_CATEGORY and CATEGORY_SUB_TYPE_ID/DELIVERABLE_SUB_CATEGORY. APPLICATION_ID identifies the owning application.

Common Use Cases and Queries

Typical uses include catalog reporting of active deliverables, ownership and status dashboards, kit composition analysis, and integration extracts feeding external marketing or fulfillment systems.

Listing active, privately flagged deliverables with resolved category, owner, and status:

SELECT deliverable_id, version, deliverable_category, deliverable_sub_category,
       owner, user_status, status_date, kit_flag, can_fulfill_electronic_flag
 FROM apps.ams_p_deliverables_v
 WHERE active_flag = 'Y';

Isolating deliverables funded by a specific campaign:

SELECT deliverable_id, deliverable_category, owner, user_status
 FROM apps.ams_p_deliverables_v
 WHERE fund_source_type = 'CAMPAIGN'
   AND fund_source_id = :campaign_id;

Identifying kits for fulfillment planning:

SELECT deliverable_id, version, owner, status_code
 FROM apps.ams_p_deliverables_v
 WHERE kit_flag = 'Y'
   AND active_flag = 'Y';

Because translation is resolved internally, callers should constrain or be aware of LANGUAGE_CODE when multi-language catalogs exist, and should always qualify the view with the APPS schema in custom code.