Search Results bisbv_performance_measures




Overview
Explore in AI Chat

Overview

BISBV_PERFORMANCE_MEASURES is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite "BIS" (Business Intelligence System / Applications BIS) product family. In EBS 12.1.1 and 12.2.2 it functions as a denormalized, language-aware presentation layer over the core indicator (performance measure) definition tables, exposing each performance measure together with its up to seven associated analysis dimensions on a single row. Its primary role is to serve Oracle Daily Business Intelligence (DBI) and related performance-management reporting components, providing a stable interface that report definitions, dashboards, and integration extracts can query without directly joining the BIS_INDICATORS, BIS_INDICATORS_TL, and BIS_INDICATOR_DIMENSIONS tables. Because the view resolves translated names through the current session language, it returns measure names and descriptions in the user's language while keeping the underlying identifiers available for programmatic use. The object carries a VALID status in a standard, patched environment and is delivered as part of the standard APPS seed data rather than as a custom object.

Underlying Base Objects

The view text joins three logical base objects, presented with inline aliases:

  • BIS_INDICATORS — the master measure/indicator definition table, supplying measure identity, unit-of-measure class, data-source configuration, function name, comparison source, dataset, and enablement flags.
  • BIS_INDICATORS_TL — the translated attributes table, supplying language-specific NAME and DESCRIPTION. It is joined on INDICATOR_ID with the restriction BIS_INDICATORS_TL.LANGUAGE = USERENV('LANG').
  • BIS_INDICATOR_DIMENSIONS — joined seven times (aliased DIM1 through DIM7) on INDICATOR_ID, each time filtered by a fixed SEQUENCE_NO (1 through 7) using an outer join so that measures with fewer than seven dimensions are still returned. The 1 = ...SEQUENCE_NO(+) predicate preserves outer-join semantics while pinning each alias to a specific dimension slot.

No additional base objects are documented beyond these; all cardinality is therefore one row per indicator per language, with dimension columns populated only where a corresponding dimension assignment exists.

Key Columns

Common Use Cases and Queries

Typical uses include validating measure setups, extracting measure-to-dimension mappings for a data model review, and feeding downstream dashboards. The following examples illustrate these patterns.

  • List all enabled, non-obsolete measures: SELECT MEASURE_ID, MEASURE_NAME, MEASURE_TYPE, UNIT_OF_MEASURE_CLASS FROM APPS.BISBV_PERFORMANCE_MEASURES WHERE ENABLED = 'Y' AND OBSOLETE = 'F' ORDER BY MEASURE_NAME;
  • Inspect dimension assignments: SELECT MEASURE_NAME, DIMENSION1_ID, DIMENSION2_ID, DIMENSION3_ID, DIMENSION4_ID, DIMENSION5_ID, DIMENSION6_ID, DIMENSION7_ID FROM APPS.BISBV_PERFORMANCE_MEASURES WHERE MEASURE_SHORT_NAME = :short_name;
  • Trace sourcing and comparisons: SELECT MEASURE_NAME, ACTUAL_DATA_SOURCE_TYPE, ACTUAL_DATA_SOURCE, FUNCTION_NAME, COMPARISON_SOURCE FROM APPS.BISBV_PERFORMANCE_MEASURES WHERE DATASET_ID = :dataset_id;

Because the view returns translated attributes, query it from a session whose language is set as expected; for pure metadata or administrative checks, restrict against MEASURE_SHORT_NAME rather than the translated NAME to avoid language-dependent results.