Results for “num_cancelled”

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

Overview

BIM_SUMV_EVENT_RSLTS is an APPS-owned reporting view within the Oracle E-Business Suite Marketing Intelligence (BIM) module. It presents summarized event response results by combining a pre-aggregated fact table with an event dimension view, exposing a denormalized result set suitable for marketing analytics, dashboards, and operational reporting. The view joins the summary table BIM_EVENT_RESP_SUMM to the dimension view BIM_DIMV_EVENT_HIER, so that each summary record is enriched with descriptive event and offering attributes such as event name, offering name, and event type code.

The view is defined WITH READ ONLY, meaning it cannot be used as a DML target; it is strictly a query object. Status is VALID in both the 12.1.1 and 12.2.2 releases, and the object name is referenced in ETRM documentation as a stable reporting artifact across those versions. Because it carries the EVENT_OFFERING_ID key, it is frequently located by users searching on that term when tracing how offering-level results are surfaced for reporting.

Underlying Base Objects

The documented base objects referenced by BIM_SUMV_EVENT_RSLTS are:

• BIM_EVENT_RESP_SUMM (referenced through a SYNONYM) — the summary fact table aliased BER, supplying event identifiers, period information, and the cumulative response counts.
• BIM_DIMV_EVENT_HIER (VIEW) — the event dimension view aliased BEH, supplying descriptive attributes: event name, event offer name, and event type code.
• FND_GLOBAL (PACKAGE) — the standard EBS concurrent/security context package invoked by the referenced dimension objects, typically for responsibility and organization context.

The defining join is BER.EVENT_OFFERING_ID = BEH.EVENT_OFFER_ID. This equates the offering identifier on the summary fact table with the offer identifier exposed by the event hierarchy dimension. Consequently, the grain of the view is one row per event offering per period, and the dimension contributes human-readable labels while the fact table contributes measures. Because BIM_EVENT_RESP_SUMM is accessed through a synonym, the underlying physical table resides in the same schema context, and the view inherits that dependency.

Key Columns

The view exposes fifteen columns, organized into identifiers, descriptive attributes, period attributes, and measures.

• EVENT_ID — identifier of the marketing event.
• EVENT_OFFERING_ID — the offering identifier; the primary join key to the dimension and the column most frequently used to link results to a specific offer.
• EVENT_NAME — descriptive name of the event from the dimension.
• EVENT_OFFERING_NAME — descriptive name of the offering (aliased from EVENT_OFFER_NAME in the dimension).
• EVENT_TYPE — classification code of the event.
• PERIOD_NAME, START_DATE, END_DATE — the reporting period label and its bounding dates.
• NUM_AVAILABLE, NUM_TARGETED, NUM_RESPONDED, NUM_ENROLLED, NUM_ATTENDED, NUM_CANCELLED — the funnel measures, from population availability through targeting, response, enrollment, attendance, and cancellation.

Common Use Cases and Queries

Typical scenarios include event funnel analysis, response-rate computation, and offering-level result comparisons across periods. A representative query filtered by offering is:

• SELECT event_offering_id, event_offering_name, period_name, num_targeted, num_responded, num_enrolled FROM apps.bim_sumv_event_rslts WHERE event_offering_id = :p_offering_id ORDER BY period_name;
• SELECT event_name, event_type, SUM(num_responded), SUM(num_enrolled) FROM apps.bim_sumv_event_rslts GROUP BY event_name, event_type;
• SELECT period_name, num_targeted, num_responded, ROUND(num_responded/NULLIF(num_targeted,0)*100,2) response_pct FROM apps.bim_sumv_event_rslts WHERE event_offering_id = :p_offering_id;

Because the view is read-only and pre-joined, it is well suited to ad hoc SQL, BI Publisher reports, and OBIEE/BI Publisher marketing dashboards. Queries should filter on EVENT_OFFERING_ID where offering-level granularity is required, since the underlying summary table may hold multiple offerings per event.