Search Results dummy1_fr




Overview
Explore in AI Chat

Overview

APPS.BIM_SGMT_ACT_MV is a materialized view object registered in the Oracle E-Business Suite Applications schema (APPS) and classified under the FND design data repository as FND.BIM_SGMT_ACT_MV. It resides in the APPS_TS_SUMMARY tablespace, the standard container for pre-aggregated summary data, with a PCT Free setting of 10. The object carries a VALID status in the ETRM 12.1.1 dictionary and is exposed as a TABLE-type object, consistent with how Oracle EBS publishes materialized views for query and reporting consumption.

The BIM prefix associates this object with the Oracle Marketing / Business Intelligence Marketing (Campaign and Segment Analytics) functional area. Its column set — activities counts, responses, leads, opportunity amounts, and booked amounts, each paired with a companion currency or converted (_C) column — indicates that the view stores period-based marketing performance results broken down by segment and category. The heuristic Data Vault classification derived from the foreign key structure is standalone, meaning the object holds no outbound foreign key dependencies on other hub or link structures within the modeling scope; it functions as a self-contained reporting aggregate rather than a normalized hub or link. When mapped to a Data Vault perspective, this object is best treated as a satellite-like summary table keyed by a composite business key rather than a true hub.

Key Information Stored

The table contains 26 documented numeric columns. The most significant grouping is as follows:

  • TIME_ID and PERIOD_TYPE_ID — define the time dimension and grain (day, week, period, quarter) at which the aggregate is stored.
  • SEGMENT_ID — the primary segmentation key; also the subject of the documented foreign key relationship to APPS.CSF_TDS_SEGMENTS.
  • CATEGORY_ID and CATEGORY_ID_C — the marketing category identifier and its converted/primary counterpart used in the unique index.
  • ACTIVITIES_COUNT / ACTIVITIES_COUNT_C, RESPONSES / RESPONSES_C, LEADS / LEADS_C — funnel metrics capturing activity volume, response volume, and qualified leads, each stored in both an original and converted form.
  • NEW_OPPORTUNITY_AMT and its _C, _S, and _S_C variants, together with BOOKED_AMT and its _C, _S, and _S_C variants — revenue-side measures, with the _S suffix denoting a secondary (possibly standardized) currency view and _C denoting converted values.
  • ALL_CNT — a general count measure used in roll-ups.
  • DUMMY1_FR through DUMMY6_FR — placeholder reserved columns that participate in the unique index construction rather than in business reporting.

There is no single-column surrogate primary key. The documented uniqueness is enforced by the function-based unique index I_SNAP$_BIM_SGMT_ACT_MV, which combines SYS_OP_MAP_NONNULL transformations of SEGMENT_ID, DUMMY1_FR–DUMMY5_FR, CATEGORY_ID_C, and DUMMY6_FR. This composite is the business-key candidate for the object; the SYS_OP_MAP_NONNULL wrapper allows NULL-safe participation in the unique constraint.

Common Use Cases and Queries

The view is typically consumed by marketing analytics dashboards and segment performance reports. A standard extraction follows the structure published in the ETRM query text:

SELECT TIME_ID, PERIOD_TYPE_ID, SEGMENT_ID, CATEGORY_ID,
       ACTIVITIES_COUNT, RESPONSES, LEADS,
       NEW_OPPORTUNITY_AMT, BOOKED_AMT, ALL_CNT
FROM   APPS.BIM_SGMT_ACT_MV
WHERE  TIME_ID = :p_time_id
AND    SEGMENT_ID = :p_segment_id;

Typical reporting scenarios include comparing response-to-lead conversion across segments, tracking booked amount by category over rolling periods, and reconciling marketing-sourced opportunity amounts against financial bookings. Aggregation queries grouped by PERIOD_TYPE_ID and CATEGORY_ID support period-over-period trend analysis. Because the object sits in APPS_TS_SUMMARY, refresh scheduling is expected to be periodic rather than real time, so reports should account for refresh lag.

Related Objects

  • APPS.CSF_TDS_SEGMENTS — referenced via BIM_SGMT_ACT_MV.SEGMENT_ID; supplies segment master attributes.
  • APPS.BIM_SGMT_ACT_MV — the base materialized view object itself, which is self-referenced in the dependency listing.
  • The function-based index I_SNAP$_BIM_SGMT_ACT_MV — the unique access path supporting constraint enforcement and deduplicated lookups.

The documented dependency metadata records no additional outbound references from this object, and inbound referencing objects are limited to the entity itself. Any further joins to time, category, or currency dimension views should be validated against the customer's specific ETRM dictionary, as they are not asserted in the source metadata.