Search Results bsc_bis_measures_data

Overview

BSC_BIS_MEASURES_DATA is a Balanced Scorecard (BSC) and Performance Management Framework (PMF) table that stores measure actual and target values for scorecard indicators. Within Oracle E-Business Suite 12.1.1 and 12.2.2, it functions as the persistence layer behind the BSC dashboards, scorecard portlets, and PMF analytic views, capturing the numeric results that users and administrators view when a scorecard or KPI is expanded. The table sits in the BSC schema and is classified as VALID in the E-Business Technical Reference Manual (ETRM).

From a heuristic Data Vault modeling perspective, the documented metadata classifies BSC_BIS_MEASURES_DATA as standalone. This suggestion reflects the mined foreign-key structure: the table does not participate in a traditional hub-and-link topology but instead behaves as a self-contained persistence object whose grain is defined by its business-key columns plus a single reference to a color/series definition. Data Vault practitioners would treat it as a satellite-like store of measure values keyed by user, responsibility, indicator, and analysis dimensions, rather than a shared hub referenced by other entities.

Key Information Stored

The table holds 15 documented columns. The most significant are:

• USER_ID, RESPONSIBILITY_ID — identify the operating context (which user and responsibility the cached measure values belong to).
• INDICATOR — the KPI or measure being valued.
• ANALYSIS_OPTION0, ANALYSIS_OPTION1, ANALYSIS_OPTION2 — the analysis dimension coordinates that slice the measure.
• SERIES_ID — foreign key to BSC_SYS_SERIES_COLORS, linking the row to a series (color/threshold) definition.
• CACHING_KEY — a cache discriminator used to retrieve or invalidate measure data efficiently.
• ACTUAL_DATA, BUDGET_DATA — the stored actual and target/budget measure values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns.

The documented business-key candidate is the unique index BSC_BIS_MEASURES_DATA_U1, defined over (USER_ID, RESPONSIBILITY_ID, INDICATOR, ANALYSIS_OPTION0, ANALYSIS_OPTION1, ANALYSIS_OPTION2, SERIES_ID). No separate surrogate primary-key column is documented; the unique index therefore serves as the effective logical key for the row grain.

Common Use Cases and Queries

Typical scenarios include scorecard rendering, performance reporting, and cache refresh diagnostics. A representative query retrieves actual versus budget values for an indicator across a user context:

• SELECT INDICATOR, ACTUAL_DATA, BUDGET_DATA FROM BSC.BSC_BIS_MEASURES_DATA WHERE USER_ID = :p_user AND RESPONSIBILITY_ID = :p_resp AND SERIES_ID = :p_series;
• Join to BSC_SYS_SERIES_COLORS to resolve series naming and color coding for dashboard display.
• Reporting extracts that aggregate ACTUAL_DATA by INDICATOR or ANALYSIS_OPTION columns for trend analysis.
• Administrative checks that flag stale rows via LAST_UPDATE_DATE or CACHING_KEY to validate cache coherence.

Because the table is a cache-oriented store, conversions and integrations should treat it as read-mostly and refresh it through BSC/PMF application logic rather than direct DML.

Related Objects

• BSC_SYS_SERIES_COLORS — referenced through SERIES_ID, providing series/color definitions for each measure row.
• BSC_BIS_MEASURES — the measure/indicator definition tables that supply the INDICATOR metadata.
• BSC_SYS_INDICATORS or equivalent indicator master — source of indicator identity and thresholds.
• BSC_SYS_RESPONSIBILITIES and user reference tables — resolve USER_ID and RESPONSIBILITY_ID contexts.
• BSC/PMF dashboard and portlet views — consume BSC_BIS_MEASURES_DATA to render scorecard output.
• FND_USER and FND_RESPONSIBILITY — standard EBS masters joined to USER_ID and RESPONSIBILITY_ID.

The FK to BSC_SYS_SERIES_COLORS is the only documented foreign-key relationship, confirming the standalone classification.