Search Results msd_levels_u2




Overview

MSD.MSD_LEVELS is a seed data table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema MSD (the Advanced Planning / Demand Planning schema foundation). It defines the levels used within a planning dimension hierarchy and records the owning dimension and the classification of each level. In that capacity, MSD_LEVELS functions as the master registry of hierarchy levels that other planning, BOM, WIP, BI/analytics, and HR-related tables reference through the LEVEL_ID foreign key.

From a Data Vault modeling perspective the table is best treated as a standalone reference hub: the metadata classifies it as standalone, with a single primary key MSD_LEVELS_PK on LEVEL_ID and no foreign keys of its own. It is referenced broadly (a characteristic of a hub-style reference entity) but does not itself depend upward on other MSD tables. This makes it useful as a conformed reference for level names, types, and dimension codes across dependent subject areas.

Key Information Stored

MSD_LEVELS contains 40 documented columns. The most important are summarized below.

Two unique indexes are documented as business-key candidates: MSD_LEVELS_U1 on (PLAN_TYPE, LEVEL_ID, ZD_EDITION_NAME) and MSD_LEVELS_U2 on (PLAN_TYPE, LEVEL_NAME, ZD_EDITION_NAME). The surrogate key is LEVEL_ID; the business key is the combination of LEVEL_NAME, PLAN_TYPE, and edition.

Common Use Cases and Queries

Typical queries resolve level names and types for reporting, validate hierarchy configuration, or join levels to dependent planning tables.

  • List all levels for a dimension: SELECT LEVEL_ID, LEVEL_NAME, LEVEL_TYPE_CODE FROM MSD.MSD_LEVELS WHERE DIMENSION_CODE = :dim;
  • Find top-level levels: filter LEVEL_TYPE_CODE to the Top Level lookup value.
  • Join to dependent tables using the shared key: SELECT ... FROM MSD.MSD_LEVELS l JOIN MSD.MSD_LEVEL_ASSOCIATIONS a ON a.LEVEL_ID = l.LEVEL_ID;
  • Audit configuration changes by querying the WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY).
  • Cross-check edition/plan context using ZD_EDITION_NAME and PLAN_TYPE, honoring the U1 and U2 uniqueness rules.

Related Objects

MSD_LEVELS is referenced by many tables through LEVEL_ID. Significant dependents include: