Results for “bsc_sys_measures”

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

Overview

The table BSC.BSC_SYS_MEASURES is the core measure definition table in the Oracle E-Business Suite Balanced Scorecard (BSC) module. Balanced Scorecard is the component of Oracle EBS that supports strategy management, enabling organizations to translate strategy into operational objectives, key performance indicators (KPIs), and scorecards. Within that framework, BSC_SYS_MEASURES stores the metadata that defines each individual measure — the numeric indicators used to track actual and budgeted performance against strategic targets.

In Oracle EBS 12.1.1, the table is documented as owned by the BSC schema with twenty columns and a primary key constraint named BSC_SYS_MEASURES_PK on the MEASURE_ID column. A unique index, BSC_SYS_MEASURES_U1, also exists on MEASURE_ID, making it both the surrogate primary key and the sole documented business-key candidate. From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning: MEASURE_ID functions as a durable business key referenced by dependent tables, which suggests the table behaves like a hub surrounded by satel

lite-style descriptive attributes rather than as a transactional link.

Key Information Stored

Each row represents one measure, and the most significant columns are:

• MEASURE_ID — the surrogate primary key and unique business key that identifies a measure throughout the BSC schema.
• MEASURE_COL — the underlying column or data element name that the measure draws from.
• OPERATION — the aggregation or calculation operation applied when the measure is computed.
• TYPE — the measure type, distinguishing how the indicator is evaluated.
• MIN_ACTUAL_VALUE and MAX_ACTUAL_VALUE — the lower and upper thresholds for actual measure results, typically used for status and color coding.
• MIN_BUDGET_VALUE and MAX_BUDGET_VALUE — the corresponding thresholds for budgeted or target values.
• RANDOM_STYLE — a display or rendering style attribute for the measure.
• EDW_FLAG, EDW_FACT_ID, and EDW_MEAS_ID — flags and identifiers linking the measure to the Enterprise Data Warehouse for integrated reporting.
• S_COLOR_FORMULA — the formula governing the scorecard color assignment for the measure.
• SHORT_NAME — an abbreviated display name for the measure.
• SOURCE — the originating system or source of the measure data.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard Oracle EBS who-columns for change tracking.

Common Use Cases and Queries

Balanced Scorecard administrators and report developers query this table to enumerate defined measures, inspect their thresholds, and trace their warehouse integration. A typical metadata query retrieves measure definitions with their display and threshold attributes:

• SELECT measure_id, short_name, measure_col, operation, type FROM bsc.bsc_sys_measures;
• SELECT measure_id, min_actual_value, max_actual_value, min_budget_value, max_budget_value FROM bsc.bsc_sys_measures WHERE measure_id = :p_measure_id;

Because BSC_SYS_DATASETS_B references up to two measures per dataset row via MEASURE_ID1 and MEASURE_ID2, developers frequently join the two tables to resolve which measures belong to a dataset. Reporting scenarios include building a measure catalog for scorecard configuration, validating threshold definitions before deployment, and auditing which measures are exposed to the Enterprise Data Warehouse through EDW_FLAG and EDW_MEAS_ID.

Related Objects

The most significant dependent object is BSC_SYS_DATASETS_B, which holds foreign keys MEASURE_ID1 and MEASURE_ID2 referencing BSC_SYS_MEASURES.MEASURE_ID; a single dataset can therefore resolve to two distinct measures. Beyond that relationship, the BSC module typically includes measure value tables, scorecard and objective definition tables, and indicator assignment tables that reference MEASURE_ID to link measures to scorecard elements. The primary key and unique index on MEASURE_ID ensure that any dependent table, view, or concurrent program resolving a measure through this key returns a single, unambiguous definition row.