Search Results msc_bis_target_levels_u2




Overview

MSC.MSC_BIS_TARGET_LEVELS is a configuration and metadata table within the Oracle E-Business Suite 12.1.1 / 12.2.2 MSC schema, owned by the Advanced Supply Chain Planning / Business Intelligence System (BIS) subsystem. The table stores the distinct combinations of dimension levels that are applied simultaneously to produce a performance indicator aligned to a specific reporting requirement. A representative example in the documentation describes capturing sales revenue broken down by month, by product, and by state; this triplet of parameters would be persisted as a single target level row.

Rows are collected from source applications and are keyed by TARGET_LEVEL_ID together with SR_INSTANCE_ID, which identifies the source application instance. This dual-key pattern is common across MSC tables that aggregate cross-instance BI data. From a Data Vault modeling perspective, the heuristic classification is satellite-leaning, suggesting this table is best treated as a descriptive satellite attached to a business key hub rather than as a hub or link itself.

Key Information Stored

The surrogate primary key MSC_BIS_TARGET_LEVELS_PK is composed of TARGET_LEVEL_ID and SR_INSTANCE_ID. Two unique indexes act as business-key candidates: MSC_BIS_TARGET_LEVELS_U1 (SR_INSTANCE_ID, TARGET_LEVEL_ID) and MSC_BIS_TARGET_LEVELS_U2 (TARGET_LEVEL_SHORT_NAME, SR_INSTANCE_ID). The latter is the target the user searched for under the name msc_bis_target_levels_u2, and it enforces uniqueness of the short name within a source instance.

Common Use Cases and Queries

Target levels drive KPI dashboards, threshold-alerting workflows, and cross-source reporting in Oracle Supply Chain Intelligence and Demand Planning. Analysts commonly join the table to the measures definition to enumerate available indicators.

  • List all target levels for a given source instance: SELECT TARGET_LEVEL_ID, TARGET_LEVEL_NAME FROM MSC_BIS_TARGET_LEVELS WHERE SR_INSTANCE_ID = :p_instance;
  • Retrieve the measure behind a target level: SELECT t.TARGET_LEVEL_NAME, m.MEASURE_NAME FROM MSC_BIS_TARGET_LEVELS t, MSC_BIS_PERFORMANCE_MEASURES m WHERE t.MEASURE_ID = m.MEASURE_ID;
  • Audit which target levels are consumed by configured targets: SELECT tgt.TARGET_ID, tl.TARGET_LEVEL_NAME FROM MSC_BIS_TARGETS tgt JOIN MSC_BIS_TARGET_LEVELS tl ON tgt.TARGET_LEVEL_ID = tl.TARGET_LEVEL_ID AND tgt.SR_INSTANCE_ID = tl.SR_INSTANCE_ID;
  • Detect dimension combinations reused across instances: group by DIMENSION1_LEVEL_IDDIMENSION5_LEVEL_ID and count SR_INSTANCE_ID.

Related Objects

The table sits between measure definitions and user-facing targets. The most significant related objects follow.

  • MSC.MSC_BIS_PERFORMANCE_MEASURES — referenced through MEASURE_ID; defines the metric the target level measures.
  • MSC.MSC_BIS_TARGETS — references this table via TARGET_LEVEL_ID; holds the actual targets assigned to users or responsibilities.
  • Organization hierarchy sources qualifying ORG_LEVEL_ID.
  • Time hierarchy sources qualifying TIME_LEVEL_ID.
  • Generic dimension level definitions consumed by DIMENSION1_LEVEL_ID through DIMENSION5_LEVEL_ID.
  • Workflow and notification setup tables referenced by WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS_SHORT_NAME, and DEFAULT_NOTIFY_RESP_ID.