Search Results ams_using_object_type




Overview
Explore in AI Chat

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

Overview

APPS.AMS_ACT_DELIVERABLES_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view in the Advanced Marketing (AMS) module. It exposes deliverable-backed object associations, presenting each row as a relationship between a deliverable (the "using" object) and a master object such as a campaign, event, or activity. The view joins AMS_OBJECT_ASSOCIATIONS to AMS_P_DELIVERABLES_V and decodes four lookup columns through AMS_LOOKUPS, producing human-readable meanings alongside raw lookup codes. Its primary role is to provide a denormalized, reporting-friendly projection of deliverable associations for use in concurrent programs, OBIEE/BI Publisher reports, and integration extracts, sparing consumers from writing the repetitive lookup-decoding joins themselves.

Underlying Base Objects

Per the documented view metadata (ETRM 12.2.2), the view is owned by APPS and defined over three referenced objects: AMS_LOOKUPS (VIEW), AMS_OBJECT_ASSOCIATIONS (SYNONYM), and AMS_P_DELIVERABLES_V (VIEW). AMS_OBJECT_ASSOCIATIONS is the driving table, supplying the association identifier, usage type, master and using object references, quantity, fulfillment attributes, and version number. AMS_P_DELIVERABLES_V supplies the deliverable name and its category and sub-category identifiers and descriptions. AMS_LOOKUPS is joined four times in an outer-join fashion to resolve the coded values. Note that AMS_OBJECT_ASSOCIATIONS is exposed as a synonym, and AMS_LOOKUPS is itself a view; neither is a physical table in this definition, so downstream consumers should treat these as logical dependencies.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting all deliverables attached to a given campaign or event, auditing usage-type distribution, and exporting deliverable requirements with due dates. The decoded MEANING columns are especially useful because the raw lookup codes reside in AMS_OBJECT_USAGE_TYPE and related lookup types.

Sample 1 — List deliverables and decoded usage types for a master object:

SELECT object_association_id, deliverable_name,
       meaning, quantity_needed, quantity_needed_by_date
FROM   apps.ams_act_deliverables_v
WHERE  master_object_id = :p_master_id
ORDER  BY quantity_needed_by_date;

Sample 2 — Summarize by usage type:

SELECT usage_type, meaning, COUNT(*) deliverable_count
FROM   apps.ams_act_deliverables_v
GROUP  BY usage_type, meaning
ORDER  BY usage_type;

Because the view is built on views and a synonym and applies the outer joins via the legacy (+) syntax, users should apply NVL to the LKUP*.MEANING columns where missing lookups are possible, and note that performance depends on the underlying AMS_OBJECT_ASSOCIATIONS indexing. As with all APPS views, query access is governed by the standard AMS responsibility grants.