Search Results campaign_type_name

Overview

APPS.BIM_DIMV_CAMPAIGNS is a public Oracle E-Business Suite view owned by the APPS schema and registered as FND Design Data BIM.BIM_DIMV_CAMPAIGNS. It functions as a dimensional or reporting view within the BIM (Business Intelligence Marketing or related marketing intelligence) module. As stated in the ETRM metadata, the view "shows all campaigns," making it the principal consolidated read-only surface for campaign data used in Oracle Marketing (AMS) reporting and integration scenarios.

The view is designed for custom reporting and analytics. Its status is VALID in both 12.1.1 and 12.2.2, and it is not referenced by any other database object, which confirms that it is a terminal, consumer-facing object intended to be queried directly by reports, extracts, and downstream tools rather than being a building block for other EBS objects. Because it is a view and not a table, all data is derived at query time from its documented dependencies.

Underlying Base Objects

The ETRM metadata for 12.2.2 lists no documented referenced base objects, and the excerpt also states the view is not referenced by any database object. However, the dependency section of the source documentation identifies the following objects that BIM_DIMV_CAMPAIGNS references:

• APPS.AMS_CAMPAIGNS_VL — the core campaign entity view, supplying campaign identity, names, descriptions, dates, parent/child rollups, and status.
• APPS.AMS_SOURCE_CODES_DETAILS_V — supplies campaign source code details.
• APPS.BIM_I_SOURCE_CODES — the BIM source codes interface table, contributing source-code mapping data.
• APPS.FND_LOOKUPS — resolves lookup codes such as campaign type and status into their translated display names.
• APPS.FND_GLOBAL — provides session context, notably the organization and language identifiers used for multi-org and MLS filtering.

The view therefore denormalizes campaign, source, and lookup data into a single flat structure suitable for dimensional extraction. Because FND_GLOBAL is used, results are typically restricted to the current operating unit and language context.

Key Columns

The view exposes 19 columns. The primary identifier is CAMPAIGN_ID (NUMBER). CAMPAIGN_NAME (VARCHAR2, length 240) and CAMPAIGN_DESCRIPTION provide the descriptive attributes of the campaign. The columns ID (VARCHAR2 40) and VALUE (VARCHAR2 80) appear to be generic identifier/display-value pairs used by the marketing dimensional layer.

For the searched term campaign_type_name, the view exposes two related columns: CAMPAIGN_TYPE (VARCHAR2, the internal or coded campaign type) and CAMPAIGN_TYPE_NAME (VARCHAR2, the descriptive campaign type name, typically resolved through FND_LOOKUPS). Reporting should generally prefer CAMPAIGN_TYPE_NAME for user-facing output and CAMPAIGN_TYPE for joins or filters.

Status information is provided by USER_STATUS_ID (NUMBER), STATUS_CODE (VARCHAR2), STATUS_DATE (DATE), STATUS_NAME, and STATUS_DESCRIPTION. Campaign hierarchy is captured via PARENT_CAMPAIGN_ID (NUMBER) and ROLLUP_TYPE (VARCHAR2). Lifecycle timing is captured by four date columns: FORECASTED_EXEC_START_DATE, FORECASTED_EXEC_END_DATE, ACTUAL_EXEC_START_DATE, and ACTUAL_EXEC_END_DATE. SOURCE_CODE (VARCHAR2) links to the underlying source-code definitions.

Common Use Cases and Queries

Typical scenarios include campaign performance reporting by type, hierarchy rollup analysis, forecast-versus-actual execution variance, and campaign extracts for external marketing analytics. A basic query listing campaigns by type and status would read:

SELECT CAMPAIGN_ID
     , CAMPAIGN_NAME
     , CAMPAIGN_TYPE
     , CAMPAIGN_TYPE_NAME
     , STATUS_CODE
     , STATUS_NAME
     , ACTUAL_EXEC_START_DATE
     , ACTUAL_EXEC_END_DATE
FROM APPS.BIM_DIMV_CAMPAIGNS;

To aggregate campaigns by type name within a reporting period, the CAMPAIGN_TYPE_NAME column serves as the grouping key:

SELECT CAMPAIGN_TYPE_NAME
     , COUNT(*) AS campaign_count
FROM APPS.BIM_DIMV_CAMPAIGNS
WHERE ACTUAL_EXEC_START_DATE >= :p_start_date
GROUP BY CAMPAIGN_TYPE_NAME
ORDER BY campaign_count DESC;

For hierarchy analysis, PARENT_CAMPAIGN_ID can be joined back to CAMPAIGN_ID to reconstruct parent-child relationships. Because the view draws on FND_GLOBAL, extracts should be executed within the correct operating unit session. The view's design as a shared dimensional object makes it appropriate for custom reporting without modifying AMS base tables, and it is safe to rely upon its structure across both 12.1.1 and 12.2.2 as documented.