Search Results msd_levels_v




Overview
Explore in AI Chat

Overview

MSD_LEVELS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSD (Demand Planning) product family within the Advanced Planning and Demand Planning modules. The view exposes the definition of planning levels used by the demand planning engine, together with the owning dimension assigned to each level and the classification of the level type. It presents this information in a denormalized, human-readable form suitable for reporting, data extraction, and integration with external planning or business intelligence tools.

The view is documented as VALID in ETRM metadata for both EBS 12.1.1 and 12.2.2. Because MSD_LEVELS_V resolves lookup codes to their descriptive meanings, report developers and integration architects can query it directly without repeatedly joining to lookup tables or decoding internal codes. This makes it a convenient access point for understanding the dimensional model on which demand planning hierarchies are constructed.

Underlying Base Objects

The view is defined over two documented base objects: the synonym MSD_LEVELS (which resolves to the MSD_LEVELS table) and the view FND_LOOKUP_VALUES_VL. The SQL joins MSD_LEVELS to FND_LOOKUP_VALUES_VL twice, aliased as FLV1 and FLV2.

  • FLV1 is constrained by LOOKUP_TYPE = 'MSD_DIMENSIONS' and matches DIMENSION_CODE on the level record. It supplies the descriptive meaning for the owning dimension.
  • FLV2 is constrained by LOOKUP_TYPE = 'MSD_LEVEL_TYPE' and matches LEVEL_TYPE_CODE. It supplies the descriptive meaning for the level type.
  • MSD_LEVELS is the primary source for level identifiers, names, descriptions, attributes, and WHO columns.

Because the join is expressed as an inner join via the WHERE clause, a level record is only returned when valid lookup values exist for both its dimension code and its level type code. The view therefore inherits the standard _VL (view with translation) behavior of FND_LOOKUP_VALUES_VL for language-sensitive lookup meanings.

Key Columns

Common Use Cases and Queries

Typical usage includes validating level configurations before running demand planning collections, populating reference data in external planning models, and building ad hoc reports of dimensions and their levels. A simple listing of all levels is:

SELECT level_id, level_name, owning_dimension, level_type FROM apps.msd_levels_v WHERE level_type = 'Demand Plan';

To group levels by owning dimension for analytical counts:

SELECT owning_dimension, COUNT(*) FROM apps.msd_levels_v GROUP BY owning_dimension ORDER BY owning_dimension;

To extract audit and program context for integration or troubleshooting:

SELECT level_id, level_name, last_update_date, last_updated_by, program_id FROM apps.msd_levels_v WHERE last_update_date > SYSDATE - 7;

As the view performs inner joins to lookup values, queries should anticipate that levels lacking a valid MSD_DIMENSIONS or MSD_LEVEL_TYPE lookup entry will not appear; reconciling such gaps is best done against the base MSD_LEVELS table. All access should be granted through the APPS schema or an appropriate synonym and read-only privilege.