Search Results bim_event_perf_summ




Overview
Explore in AI Chat

Overview

BIM_EVENT_PERF_SUMM is a summary table within the Oracle E-Business Suite Marketing Intelligence (BIM) module, owned by the BIM schema. It stores summarized marketing campaign performance data aggregated by user-defined periods. The table is populated exclusively by the BIM_EVENT_PERF_SUMM_PKG concurrent program, which consolidates transactional event and lead activity into period-based snapshots for analytical reporting. This design pattern is typical of Oracle Marketing Intelligence, where raw event responses and lead transactions are rolled up into pre-aggregated structures to support high-performance dashboards, campaign ROI analysis, and response-rate reporting without repeatedly scanning high-volume transactional tables.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone, mined from its foreign key structure. This suggests the table functions independent of a strict hub/link/satellite topology, operating instead as a denormalized periodic snapshot that references several parent dimensions. The classification is a modeling suggestion only; the physical design is a conventional relational summary table with a 25-column structure supporting period-based slicing.

Key Information Stored

The table's business-key candidate is defined by the unique index BIM_EVENT_PERF_SUMM_U1, which spans a composite of PERIOD_NAME, PERIOD_START_DATE, PERIOD_END_DATE, EVENT_ID, EVENT_OFFERING_ID, CAMPAIGN_ID, MARKET_SEGMENT_ID, SALES_CHANNEL_CODE, INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID, BILL_TO_GEOGRAPHY_CODE, and LEAD_ID. This composite uniquely defines each summarized grain: a marketing event and offering, scoped to a campaign, market segment, sales channel, interest profile, geography, and lead, over a defined period.

Key columns include PERIOD_NAME, PERIOD_START_DATE, and PERIOD_END_DATE, which define the aggregation window. EVENT_ID and EVENT_OFFERING_ID identify the marketing event and its specific offering. CAMPAIGN_ID and MARKET_SEGMENT_ID provide campaign and segmentation context, while SALES_CHANNEL_CODE captures the channel attribution. INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, and SECONDARY_INTEREST_CODE_ID record interest-based qualification attributes, and BILL_TO_GEOGRAPHY_CODE (alongside SHIP_TO_GEOGRAPHY_CODE) provides geographic attribution. LEAD_ID ties the summary to an individual lead. The metric column of primary analytic value is INITIATED_REVENUE, representing revenue attributed to the summarized activity. Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present, as is SECURITY_GROUP_ID for multi-tenant access control.

Common Use Cases and Queries

Typical reporting scenarios include campaign performance trending, revenue attribution by period, and lead-response analysis by interest and geography. A sample query to aggregate initiated revenue by campaign and period follows:

  • SELECT campaign_id, period_name, SUM(initiated_revenue) FROM bim_event_perf_summ GROUP BY campaign_id, period_name ORDER BY period_name;
  • SELECT event_id, event_offering_id, market_segment_id, SUM(initiated_revenue) FROM bim_event_perf_summ WHERE period_start_date >= :p_start AND period_end_date <= :p_end GROUP BY event_id, event_offering_id, market_segment_id;
  • SELECT sales_channel_code, interest_type_id, SUM(initiated_revenue) FROM bim_event_perf_summ GROUP BY sales_channel_code, interest_type_id;

Because SECURITY_GROUP_ID is present, queries executed in a multi-org or multi-tenant context should restrict access via the security group, honoring the standard EBS security model. Reporting should always filter on period columns to leverage the aggregation grain and avoid mixing overlapping snapshots.

Related Objects

The table maintains foreign key relationships to several parent objects:

The BIM_EVENT_PERF_SUMM_PKG concurrent program is the sole population mechanism, and campaign, event, offering, market segment, and geography references resolve to the corresponding Marketing Intelligence and CRM dimension tables through their respective identifiers (CAMPAIGN_ID, EVENT_ID, EVENT_OFFERING_ID, MARKET_SEGMENT_ID). Reporting layers and Marketing Intelligence analytics dashboards consume this summary directly, joining to AS_LEADS_ALL for lead detail and AS_INTEREST_TYPES_B for interest labeling.