Results for “bim_sumv_event_rev”

18 results




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

Overview

BIM_SUMV_EVENT_REV is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the BIM product family, Marketing Intelligence, which is documented as obsolete in current ETRM releases. The view is defined with a WITH READ ONLY clause, meaning it exposes query-only access and cannot be used as the target of DML operations. Its declared status is VALID.

The view functions as a reporting and integration layer that joins a summary fact table to a dimension view, presenting event-level revenue and cost metrics in a fully denormalized form. Rather than forcing report authors and integration developers to perform the join between the summary table and the dimensional hierarchy themselves, BIM_SUMV_EVENT_REV resolves the relationship once and exposes descriptive attributes such as event name and event type directly alongside the numeric measures. The presence of FORECASTED_REVENUE among its columns explains why the view is returned when users search for that term: it is one of the primary forecasting measures surfaced for event revenue analysis.

Underlying Base Objects

The view is defined over two documented base objects, joined on a single key relationship.

  • BIM_EVENT_REVCOST_SUMM (referenced as a SYNONYM) — the summary table that supplies the fact-side data. It is aliased BER in the view definition and contributes the event identifiers, period attributes, and all revenue, cost, and lead-count measures.
  • BIM_DIMV_EVENT_HIER (VIEW) — the event hierarchy dimension view, aliased BEH. It supplies the descriptive attributes: event name, event offering name, and event type code.
  • FND_GLOBAL (PACKAGE) — documented as a referenced base object, consistent with standard EBS multi-org and session-context resolution used throughout the Reporting layer.

The join is performed as an equi-join between BER.EVENT_OFFERING_ID and BEH.EVENT_OFFER_ID. Because the fact table is keyed at the event-offering grain, the dimensional attributes are resolved at that same grain, producing one row per event offering per period.

Key Columns

Common Use Cases and Queries

The view supports forecast-versus-actual comparisons, event profitability reporting, and period-over-period revenue trending. A typical query projects forecasted revenue against actual cost by event:

  • SELECT event_name, period_name, forecasted_revenue, actual_cost FROM apps.bim_sumv_event_rev WHERE period_name = :period;
  • SELECT event_type, SUM(forecasted_revenue) FROM apps.bim_sumv_event_rev GROUP BY event_type;
  • SELECT event_offering_name, forecasted_revenue, forecasted_cost, (forecasted_revenue - forecasted_cost) margin FROM apps.bim_sumv_event_rev ORDER BY margin DESC;

Because the underlying product is obsolete, new development should confirm object availability against the target instance before relying on this view in production reporting or interfaces.