Search Results msc_bis_performance_measure_u2

Overview

MSC.MSC_BIS_PERFORMANCE_MEASURES is a transaction data table in the MSC schema that stores business performance measures collected from source applications into the Oracle Advanced Supply Chain Planning (ASCP) / Business Intelligence System (BIS) repository. It acts as the master definition repository for performance measures used by the BIS performance measurement and target-tracking framework. Each row defines a measure, its associated organizational and time dimensions, up to five additional analytic dimensions, and the unit of measure class used to interpret values. The table resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10, and is validated at status VALID in ETRM 12.2.2.

From a Data Vault modeling perspective, the heuristic classification for this table is hub-leaning. The primary key surrogate is MEASURE_ID combined with SR_INSTANCE_ID, and the table is referenced by downstream fact-like tables (for example MSC_BIS_TARGET_LEVELS), which is consistent with a hub entity that anchors measure identity across source instances.

Key Information Stored

The table contains 23 documented columns. The most significant are:

• MEASURE_ID (NUMBER) — Measure identifier; part of the composite primary key.
• SR_INSTANCE_ID (NUMBER) — Source application instance identifier; part of the composite primary key and the discriminator between collected sources.
• MEASURE_SHORT_NAME (VARCHAR2 30) — Business key candidate via unique index MSC_BIS_PERFORMANCE_MEASURE_U2.
• MEASURE_NAME (VARCHAR2 255) — Descriptive measure name.
• DESCRIPTION (VARCHAR2 1024) — Narrative description of the performance measure.
• ORG_DIMENSION_ID, TIME_DIMENSION_ID — Organization and time dimension identifiers anchoring the measure's analytic axes.
• DIMENSION1_ID through DIMENSION5_ID — Five additional dimension identifiers for finer-grained slicing.
• UNIT_OF_MEASURE_CLASS (VARCHAR2 10) — Unit of measure classification.
• REFRESH_NUMBER (NUMBER) — Refresh number populated by the collection program.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent who columns identifying the collection job.
• Standard who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Two unique indexes are documented. MSC_BIS_PERFORMANCE_MEASURE_U1 covers SR_INSTANCE_ID and MEASURE_ID; MSC_BIS_PERFORMANCE_MEASURE_U2 covers MEASURE_SHORT_NAME and SR_INSTANCE_ID. Both are business-key candidates; U2 is the natural key lookup for a measure by name within a source instance.

Common Use Cases and Queries

Typical uses include validating collection results, resolving a measure short name to its surrogate identifier, and joining measure definitions to target levels for target-versus-actual reporting. A common pattern is a lookup by business key:

• SELECT measure_id, sr_instance_id, measure_name, unit_of_measure_class FROM msc.msc_bis_performance_measures WHERE measure_short_name = :p_short_name AND sr_instance_id = :p_instance;
• SELECT m.measure_short_name, m.measure_name, t.* FROM msc.msc_bis_performance_measures m JOIN msc.msc_bis_target_levels t ON t.measure_id = m.measure_id;
• SELECT COUNT(*), MIN(last_update_date), MAX(refresh_number) FROM msc.msc_bis_performance_measures WHERE sr_instance_id = :p_instance;

Concurrent program troubleshooting often filters on REQUEST_ID or PROGRAM_ID to identify the collection run that populated a measure definition.

Related Objects

The documented foreign key relationship is with MSC_BIS_TARGET_LEVELS, where MEASURE_ID references this table. Additional dependencies include the BIS collection concurrent programs reflected in the PROGRAM_ID and REQUEST_ID columns, the FND design data object MSC.MSC_BIS_PERFORMANCE_MEASURES, and the dimension definition tables referenced through ORG_DIMENSION_ID, TIME_DIMENSION_ID, and DIMENSION1_ID–DIMENSION5_ID. The unique index MSC_BIS_PERFORMANCE_MEASURE_U2 provides the natural-key access path used by lookups and cross-instance reconciliation queries.