Search Results msc_bis_performance_measures




Overview
Explore in AI Chat

Overview

MSC_BIS_PERFORMANCE_MEASURES is a table in the MSC schema, owned by the Advanced Supply Chain Planning product (Oracle Advanced Planning and Scheduling). It serves as the master repository for business performance measures that are collected from source applications and made available to the Oracle Business Intelligence System (BIS) reporting layer embedded within Advanced Supply Chain Planning. Each row defines a distinct performance measure — for example a metric tracked against a supply chain plan, organization, or time period — along with its dimensional context, unit of measure classification, and the source instance from which it originated.

The table functions as a definition or reference entity rather than a transactional fact store: it holds the identity and descriptive attributes of a measure, while target and actual values associated with that measure are maintained in dependent tables. From a Data Vault modeling perspective, the ETRM metadata classifies this object as hub-leaning. This heuristic suggests it is best modelled as a hub: the composite key of MEASURE_ID and SR_INSTANCE_ID represents a stable business key that anchors the measure, with descriptive and dimensional attributes potentially split into a satellite.

Key Information Stored

The primary key is defined by MSC_BIS_PERFORMANCE_MEASURE_PK, a composite of MEASURE_ID and SR_INSTANCE_ID. MEASURE_ID is the surrogate identifier for the measure, while SR_INSTANCE_ID denotes the source application instance, allowing the same logical measure to be distinguished across multiple integrated source systems.

Two unique indexes provide business-key candidates:

The most significant descriptive and structural columns include:

Common Use Cases and Queries

Typical usage centers on reporting and configuration of supply chain performance metrics. Analysts join this table to its dependent target-level table to resolve measure names and dimensional context for dashboard queries. A representative pattern:

  • Resolving measure definitions for a given source instance: SELECT measure_id, measure_short_name, measure_name, unit_of_measure_class FROM msc.msc_bis_performance_measures WHERE sr_instance_id = :p_instance;
  • Listing available performance measures for selection in a BIS report layout.
  • Joining to MSC_BIS_TARGET_LEVELS to associate measures with their targets and tolerances.
  • Auditing configuration changes via CREATION_DATE and LAST_UPDATE_DATE for compliance or troubleshooting refresh issues.

Because the table is comparatively small and definitional, queries rarely require heavy filtering beyond SR_INSTANCE_ID and MEASURE_SHORT_NAME.

Related Objects

The principal dependent object documented is MSC_BIS_TARGET_LEVELS, which references this table through a composite foreign key on MEASURE_ID and SR_INSTANCE_ID. This child table stores the target-level definitions tied to each performance measure, and joins between the two are performed on these two columns.

Additional related objects within the MSC BIS schema family include the performance measure collection and staging tables used during data refresh, as well as the dimension reference tables corresponding to ORG_DIMENSION_ID, TIME_DIMENSION_ID, and DIMENSION1_ID through DIMENSION5_ID. Concurrent programs in the Advanced Supply Chain Planning module populate and maintain this table as part of the BIS data collection cycle. Reporting views in the BIS layer select from MSC_BIS_PERFORMANCE_MEASURES to expose measure metadata to end users.