Search Results increase_in_measure

Overview

APPS.BISBV_PERFORMANCE_MEASURES is a Business Intelligence System (BIS) reporting view in Oracle E-Business Suite that presents the master catalog of performance measures (indicators) tracked within the Oracle Balanced Scorecard / Daily Business Intelligence framework. The view consolidates descriptive attributes from the indicator definition tables and optionally associates up to seven analytical dimensions with each measure. Because the "BV" segment in the name denotes a Business View, the object is intended primarily as a read-only reporting surface rather than a transaction entry point, and it is typically consumed by dashboards, scorecard regions, and custom operational reports that need a single, language-aware list of enabled indicators.

Its role in EBS reporting and integration is to abstract the join complexity between the base indicator table, its translation table, and the dimension mapping table. Rather than requiring report authors to repeat the multilingual join and the seven separate dimension lookups, BISBV_PERFORMANCE_MEASURES exposes a flattened projection in which each indicator appears once with DIMENSION1_ID through DIMENSION7_ID resolved.

Underlying Base Objects

The view is defined over three logical sets of base objects, joined with outer joins for the dimension associations:

• BIS_INDICATORS — the primary table holding each indicator's definition, including its identifier, short name, unit of measure class, data source configuration, and enabled/obsolete flags.
• BIS_INDICATORS_TL — the translation table supplying the language-specific NAME and DESCRIPTION, joined on INDICATOR_ID and restricted by LANGUAGE = USERENV('LANG') so the view returns text in the session's current language.
• BIS_INDICATOR_DIMENSIONS (aliased seven times as dim1 through dim7) — the mapping table linking indicators to analytical dimensions. Each alias is joined on INDICATOR_ID with the outer-join operator (+), and constrained to a fixed SEQUENCE_NO value (1 through 7).

This is the point of direct relevance to the "sequence_no" search: the dimension sequence number is the discriminator that allows a single mapping table to supply seven distinct dimension slots, and it is used as a join predicate rather than being projected as a column in the view.

Key Columns

• MEASURE_ID — the indicator identifier (source column INDICATOR_ID); the primary key for joining to other BIS objects.
• MEASURE_SHORT_NAME and MEASURE_NAME — the internal short name and the translated display name.
• DESCRIPTION — the translated long description of the measure.
• DIMENSION1_ID … DIMENSION7_ID — the dimension identifiers mapped by sequence number; null when no dimension occupies that slot.
• UNIT_OF_MEASURE_CLASS — the UOM class (for example currency, quantity, or percentage) governing the measure's values.
• ACTUAL_DATA_SOURCE_TYPE, ACTUAL_DATA_SOURCE, and FUNCTION_NAME — define how actual results are sourced and computed.
• COMPARISON_SOURCE, INCREASE_IN_MEASURE, and ENABLE_LINK — control target/comparison behavior and drill-down navigation.
• DATASET_ID, ENABLED, OBSOLETE, and MEASURE_TYPE — classification and lifecycle attributes; OBSOLETE is coalesced to 'F' when null.

Common Use Cases and Queries

Typical usage includes validating indicator setup, driving custom scorecard reports, and auditing dimension assignments. A simple listing of active measures:

• SELECT measure_id, measure_name, measure_type FROM apps.bisbv_performance_measures WHERE enabled = 'Y' AND obsolete = 'F';
• SELECT measure_short_name, dimension1_id, dimension2_id, dimension3_id FROM apps.bisbv_performance_measures;
• SELECT measure_name, unit_of_measure_class, function_name FROM apps.bisbv_performance_measures WHERE dataset_id = :p_dataset_id;

Because the joins to the translation and dimension tables are outer joins, indicators without translations or without any mapped dimension are still returned, which makes the view safe for exception-based reporting.