Search Results primary_interest_code

Overview

BIM_SUMV_EVENT_PERF is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BIM (Marketing Intelligence) product family. Its documented status is VALID, and it is available across the 12.1.1 and 12.2.2 release lines as a read-only analytical construct. The view's stated purpose is to join the marketing event performance summary table to the relevant dimension views, producing a fully denormalized, human-readable result set suitable for ad hoc querying, marketing dashboards, and downstream integration extracts.

Conceptually, BIM_SUMV_EVENT_PERF flattens the star-schema relationship between the fact-like summary table BIM_EVENT_PERF_SUMM and the surrounding dimension views. Where the summary table stores surrogate identifiers and codes, the view resolves those identifiers into descriptive attributes such as event names, market segment names, sales channel names, and the interest code hierarchy. This makes the view particularly valuable to report authors who need descriptive output without writing multi-table joins themselves.

Underlying Base Objects

The view is defined over one summary object and four dimension views, joined on their respective surrogate keys:

• BIM_EVENT_PERF_SUMM (exposed to the view as a SYNONYM) — the driving summary table holding event performance measures, including INITIATED_REVENUE and LEAD_ID, at the grain of event offering, period, market segment, and sales channel.
• BIM_DIMV_EVENT_HIER (VIEW) — supplies EVENT_NAME, EVENT_OFFER_NAME, and EVENT_TYPE_CODE, joined on EVENT_OFFERING_ID = EVENT_OFFER_ID.
• BIM_DIMV_MARKET_SGMTS (VIEW) — supplies MARKET_SEGMENT_NAME, joined on MARKET_SEGMENT_ID.
• BIM_DIMV_SALES_CHANNELS (VIEW) — supplies SALES_CHANNEL_NAME, joined on SALES_CHANNEL_CODE.
• BIM_DIMV_PROD_LOV (VIEW) — supplies the interest type and interest code descriptions, joined on INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, and SECONDARY_INTEREST_CODE_ID.

The metadata also references FND_GLOBAL (PACKAGE), the standard EBS concurrent/global context package invoked for session attributes such as responsibility and organization context during query execution. The view is defined WITH READ ONLY, so it cannot be used as the target of DML.

Key Columns

The view exposes twenty-two columns. Identifiers and dimensions include EVENT_ID, EVENT_OFFERING_ID, CAMPAIGN_ID, PERIOD_NAME, START_DATE, END_DATE, MARKET_SEGMENT_ID, SALES_CHANNEL_CODE, INTEREST_TYPE_ID, LEAD_ID, and GEOGRAPHY_CODE. Descriptive attributes resolved from the dimension views include EVENT_NAME, EVENT_OFFERING_NAME, EVENT_TYPE, MARKET_SEGMENT_NAME, SALES_CHANNEL_NAME, and INTEREST_TYPE.

For the user's search term, the critical columns are PRIMARY_INTEREST_CODE_ID and its resolved description PRIMARY_INTEREST_CODE, both sourced through BIM_DIMV_PROD_LOV. The view also carries the secondary interest pair, SECONDARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE, allowing analysts to segment performance by both primary and secondary interest codes. The sole numeric measure surfaced is INITIATED_REVENUE, representing revenue attributed to the event offering for the identified period and segment combination.

Common Use Cases and Queries

Typical usage includes marketing performance reporting by interest code, campaign attribution, and revenue analysis by segment or channel. A representative query that isolates performance by primary interest code is:

• SELECT PERIOD_NAME, EVENT_NAME, PRIMARY_INTEREST_CODE, SUM(INITIATED_REVENUE) REVENUE FROM APPS.BIM_SUMV_EVENT_PERF WHERE PRIMARY_INTEREST_CODE = :p_interest_code GROUP BY PERIOD_NAME, EVENT_NAME, PRIMARY_INTEREST_CODE ORDER BY PERIOD_NAME;
• SELECT CAMPAIGN_ID, MARKET_SEGMENT_NAME, SALES_CHANNEL_NAME, PRIMARY_INTEREST_CODE, COUNT(DISTINCT LEAD_ID) LEADS, SUM(INITIATED_REVENUE) REVENUE FROM APPS.BIM_SUMV_EVENT_PERF WHERE PERIOD_NAME = :p_period GROUP BY CAMPAIGN_ID, MARKET_SEGMENT_NAME, SALES_CHANNEL_NAME, PRIMARY_INTEREST_CODE;
• SELECT INTEREST_TYPE, PRIMARY_INTEREST_CODE, SECONDARY_INTEREST_CODE, SUM(INITIATED_REVENUE) FROM APPS.BIM_SUMV_EVENT_PERF GROUP BY INTEREST_TYPE, PRIMARY_INTEREST_CODE, SECONDARY_INTEREST_CODE;

Because the view is READ ONLY and pre-joins all dimensions, it is well suited to BI Publisher data templates, Discoverer workbooks, and OBIEE/OTBI logical models within the Marketing Intelligence domain. Queries should always qualify the view as APPS.BIM_SUMV_EVENT_PERF or rely on a synonym in the querying schema.