Search Results forecasted_cost_b

Overview

BIM_FCTV_EVENTS is a reporting view within the Oracle E-Business Suite BIM (Marketing Intelligence) module. Its documented purpose is to support concurrent programs that load the summary tables used by Marketing Intelligence analytics. The view consolidates event offer data with associated actual metrics to present enrollment, attendance, cost, and revenue figures in both transaction and functional currency. The object is documented as "Not implemented in this database" in the source metadata, meaning it may not be deployed in every environment; it is instantiated only where the Marketing Intelligence summary loading programs are configured.

The view is particularly relevant to searches involving the TRANSACTION_CURRENCY_CODE column, because it exposes that column directly from the underlying actual metrics view and uses it as the source currency for currency conversion of cost and revenue amounts.

Underlying Base Objects

The view text is defined over three documented sources:

• AMS_P_EVENT_OFFERS_V (alias AME) — supplies event offer identifiers, event header linkage, start and end dates, and enrollment/attendance counts.
• AMS_P_ACT_METRICS_V (alias AMA1) — supplies transaction metrics related to costs and forecasted/actual values.
• AMS_P_ACT_METRICS_V (alias AMA2) — a second instance of the same metrics view, supplying revenue-side forecasted values.

The join is an outer join between the event offers and the first metrics instance (AME.EVENT_OFFER_ID = AMA1.ACT_METRIC_USED_BY_ID(+) with a further outer condition on ARC_ACT_METRIC_USED_BY), ensuring events are retained even where metrics are absent. The metadata lists no other documented base objects, and owner information is not recorded.

Key Columns

• EVENT_OFFER_ID and EVENT_HEADER_ID — surrogate identifiers, prefixed with 'EVEO' and 'EVEH' respectively via string concatenation.
• EVENT_START_DATE / EVENT_END_DATE — the offer's active window.
• NUMBER_ENROLLED, NUMBER_SPOTS_AVAILABLE, NUMBER_ATTENDED, NUMBER_CANCELLED — event participation counts sourced from the offers view.
• TRANSACTION_CURRENCY_CODE — the currency in which the underlying transaction metrics were recorded; this is the source currency fed into the conversion API.
• FUNCTIONAL_CURRENCY_CODE — derived from the profile option CRMBIS:CURRENCY_CODE.
• FORECASTED_COST_T / FORECASTED_COST_B, EVENT_ACTUAL_COST_T / EVENT_ACTUAL_COST_B, FORECASTED_REVENUE_T / FORECASTED_REVENUE_B — transaction (_T) and base (_B) currency amounts, where base values are produced through GL_CURRENCY_API.CONVERT_AMOUNT_SQL.
• CAMPAIGN_ACTUAL_COST_T / CAMPAIGN_ACTUAL_COST_B — campaign-level actual costs returned by BIM_CAMPAIGN_ACTUAL_COST_PKG.GET_CAMPAIGN_ACTUAL_COST.

Common Use Cases and Queries

The primary use case is data extraction and validation for Marketing Intelligence summary loads, plus ad hoc analysis of event performance across currencies. A representative query isolates cost figures alongside their currency context:

• SELECT event_offer_id, event_start_date, transaction_currency_code, functional_currency_code, forecasted_cost_t, forecasted_cost_b FROM bim_fctv_events WHERE event_start_date >= :start_date;
• SELECT event_offer_id, number_enrolled, number_attended, number_cancelled FROM bim_fctv_events ORDER BY event_start_date DESC;
• SELECT event_offer_id, forecasted_revenue_t, forecasted_revenue_b FROM bim_fctv_events WHERE transaction_currency_code <> functional_currency_code;

Because base amounts are already converted using the GL conversion type from CRMBIS:GL_CONVERSION_TYPE, queries filtering on TRANSACTION_CURRENCY_CODE are the appropriate way to segment transaction-currency versus functional-currency reporting without re-invoking conversion logic.