Search Results master_object_type_meaning




Overview
Explore in AI Chat

Overview

APPS.AMS_CAMPAIGN_PRODUCT_VOLUMES_V is a reporting view in the Oracle Marketing (AMS) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It consolidates campaign product activity, base sales volumes, and inventory item master attributes into a single denormalized result set suitable for analytics, extract loads, and integration interfaces. The view joins marketing activity product data to base sales volume figures and item definitions, exposing both coded values and their translated meanings (for example, MASTER_OBJECT_TYPE alongside MASTER_OBJECT_TYPE_MEANING, and LEVEL_TYPE_CODE alongside LEVEL_TYPE). This dual representation of code and meaning is significant because the user's search term, "master_object_type_meaning," corresponds directly to a column in this view — MASTER_OBJECT_TYPE_MEANING — which resolves the parent object classification of the campaign product record into a user-readable form. Because the view carries no database-level referential constraints and is not referenced by any other database object, it functions strictly as a read-only reporting and integration artifact rather than a transactional component of the AMS data model.

Underlying Base Objects

The documented dependency chain for AMS_CAMPAIGN_PRODUCT_VOLUMES_V comprises three objects. AMS_ACT_PRODUCTS_V is itself a view supplying activity product attributes, including the ACTIVITY_PRODUCT_ID and object versioning columns. AMS_BASE_SALES_VOL_ALL is referenced as a synonym, providing the base sales quantity, unit of measure, list price, period, and date dimensions that give the view its volumetric reporting character. MTL_SYSTEM_ITEMS_VL is the item master view, supplying inventory item number, description, and organization context. The view therefore sits at the intersection of campaign (activity) data, sales volume history, and product master data, inheriting the security and translation behavior of each underlying object, including multi-lingual (VL) semantics from MTL_SYSTEM_ITEMS_VL and the validation logic embedded in the AMS views.

Key Columns

The primary identifier is ACTIVITY_PRODUCT_ID, with OBJECT_VERSION_NUMBER supporting optimistic concurrency in programmatic access. MASTER_OBJECT_TYPE and MASTER_OBJECT_TYPE_MEANING identify and describe the parent object type, while MASTER_OBJECT_ID points to the specific parent instance. LEVEL_TYPE_CODE and LEVEL_TYPE capture the level classification within the campaign hierarchy, and the category block — CATEGORY_ID, CATEGORY_NAME, CATEGORY_SET_ID, CATEGORY_SET_NAME — describes product categorization, with CATEGORY_NAME padded to 163 characters to accommodate concatenated hierarchy paths. Product identification relies on ORGANIZATION_ID, INVENTORY_ITEM_ID, INVENTORY_ITEM_NUMBER, and INVENTORY_ITEM_DESCRIPTION from the item master. Commercial measures include LIST_PRICE_PER_UNIT, BASE_SALES_QUANTITY, and BASE_SALES_UOM_CODE. Time-based analysis uses PERIOD_ID, PERIOD_TYPE, and ON_DATE.

Common Use Cases and Queries

Typical scenarios include campaign product performance reporting, price-versus-volume analytics, category-level rollups, and staging extracts into a data warehouse. All queries should be issued against the APPS schema with the standard EBS responsibility and MOAC (multi-org) context established.

  • Retrieve the resolved meaning of the parent object type for campaign products: SELECT ACTIVITY_PRODUCT_ID, MASTER_OBJECT_TYPE, MASTER_OBJECT_TYPE_MEANING, MASTER_OBJECT_ID FROM APPS.AMS_CAMPAIGN_PRODUCT_VOLUMES_V;
  • Analyze base sales quantity by inventory item: SELECT INVENTORY_ITEM_NUMBER, SUM(BASE_SALES_QUANTITY) FROM APPS.AMS_CAMPAIGN_PRODUCT_VOLUMES_V GROUP BY INVENTORY_ITEM_NUMBER;
  • Filter by period and level type: SELECT ACTIVITY_PRODUCT_ID, CATEGORY_NAME, LEVEL_TYPE, LIST_PRICE_PER_UNIT FROM APPS.AMS_CAMPAIGN_PRODUCT_VOLUMES_V WHERE PERIOD_TYPE = :p_type AND ON_DATE >= :p_start;

Because the view is not referenced by other database objects, it can be queried without impacting the transactional AMS tables, making it safe for ad hoc reporting and scheduled extraction processes.