Results for “oppr_amount_b”

18 results




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

Overview

The BIM_EDW_OPRNTIES_F_DLOG table is a fact-style staging object within the Oracle E-Business Suite Marketing Intelligence (BIM) module. It resides in the BIM schema and forms part of the Enterprise Data Warehouse (EDW) layer that Oracle Marketing Intelligence historically used to consolidate opportunity pipeline data for analytical reporting. The "_DLOG" suffix indicates that this is a detail log variant of the opportunity fact, distinguished from the base star-schema fact table. The physical schema documents 56 columns in release 12.1.1, but the ETRM metadata explicitly states "Not implemented in this database," meaning the object is a legacy artifact and is not instantiated in current 12.1.1 or 12.2.2 environments. It carries the Oracle Proprietary, Confidential Information designation and falls under the obsolete product classification for BIM.

Heuristic Data Vault classification mined from the foreign key structure identifies this table as standalone. Under Data Vault modeling conventions, a standalone object with a single documented outbound reference (SECURITY_GROUP_ID to FND_SECURITY_GROUPS) is best treated as a satellite or degenerate fact rather than a true hub or link, since it lacks the multi-parent integration characteristic of a link table.

Key Information Stored

The table records opportunity line-level transactional measures alongside a wide set of foreign-key surrogates and user-defined extension slots. The most significant columns are:

The presence of both OPPR_LINE_PK_KEY and OPPR_LINE_PK is consistent with a warehouse pattern where the surrogate key isolates the physical row while the operational key preserves lineage to the source transaction.

Common Use Cases and Queries

Because the object is not implemented, practical usage today is limited to archival reconstruction, migration mapping, and data-model documentation. Where a comparable staging table exists, typical analytical patterns include pipeline-by-campaign reporting and period-over-period opportunity trend analysis. A representative query shape would aggregate measures by dimension keys:

  • SELECT t.TIME_FK_KEY, SUM(t.OPPR_AMOUNT_B) FROM BIM_EDW_OPRNTIES_F_DLOG t GROUP BY t.TIME_FK_KEY.
  • Joining dimension surrogates (CMPGN_FK_KEY, OPPSTATUS_FK_KEY, CUSTOMER_FK_KEY) to their conformed dimension tables to produce pipeline-with-status breakdowns.
  • Filtering by SECURITY_GROUP_ID to enforce row-level security inherited from FND_SECURITY_GROUPS.

Teams migrating from older BIM releases should map USER_MEASURE and USER_ATTRIBUTE slots to equivalent extension columns in the current opportunity analytics model.

Related Objects

These relationships reflect the star-schema topology typical of the Marketing Intelligence EDW, notwithstanding the standalone heuristic classification applied to this particular detail-log table.