Search Results msd_level_type




Overview
Explore in AI Chat

Overview

APPS.MSD_LEVELS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It exposes level definitions used by the Oracle Demand Planning and Advanced Planning modules, presenting hierarchical dimension levels in a denormalized, presentation-ready form. Rather than requiring callers to join the base level table against the FND lookup infrastructure manually, the view delivers the level records already enriched with translated meaning text for both the dimension and the level type.

This view is significant because the user-search term "msd_level_type" maps directly to the lookup type 'MSD_LEVEL_TYPE', which the view resolves into a human-readable meaning column. Each row also carries a translated meaning for the dimension through the 'MSD_DIMENSIONS' lookup type. The view therefore serves as the canonical read-only access point for level metadata consumed by planning inquiries, concurrent programs, and downstream integration extracts.

Underlying Base Objects

As documented in the ETRM 12.2.2 metadata, MSD_LEVELS_V is defined over the following base objects:

  • MSD_LEVELS (SYNONYM) — the driving table ml that holds the actual level definitions, including level identity, dimension assignment, level type code, descriptive flexfield contexts, WHO audit columns, and request/program bookkeeping columns.
  • FND_LOOKUP_VALUES_VL (VIEW) — referenced twice as flv1 and flv2, joining on lookup_code = ml.dimension_code with lookup_type = 'MSD_DIMENSIONS', and on lookup_code = ml.level_type_code with lookup_type = 'MSD_LEVEL_TYPE' respectively.

Because FND_LOOKUP_VALUES_VL is itself a view over the lookup values base tables, the VL suffix guarantees that users see only the language-appropriate, date-effective lookup rows. The join is an equi-join on lookup code, so a level row is only returned when matching lookup definitions exist for both its dimension and its level type. Critically, the view applies a filter ml.plan_type IS NULL, restricting output to global (non-plan-type-specific) level definitions.

Key Columns

  • LEVEL_ID / LEVEL_NAME / DESCRIPTION — the surrogate key, display name, and description of each level.
  • DIMENSION_CODE — the dimension to which the level belongs; flv1.meaning provides its translated description from 'MSD_DIMENSIONS'.
  • LEVEL_TYPE_CODE — the coded category of the level; flv2.meaning provides the translated description from 'MSD_LEVEL_TYPE', the object of the searched term.
  • attribute1_context through attribute5_context and system_attribute1_context / system_attribute2_context — descriptive flexfield context codes guiding attribute interpretation.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield segment values attached to each level.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program tracking columns.
  • ROWID — the physical row identifier of the MSD_LEVELS row, enabling row-level addressing.

Common Use Cases and Queries

Typical uses include populating planning hierarchies, validating level configuration, and extracting level metadata with translated lookup meanings for reporting. A representative query retrieving levels by type is shown below:

SELECT level_id, level_name, dimension_code,
       meaning AS dimension_meaning,
       level_type_code, meaning AS level_type_meaning
FROM   apps.msd_levels_v
WHERE  level_type_code = :p_level_type_code
ORDER  BY dimension_code, level_name;

SELECT level_id, level_name, description
FROM   apps.msd_levels_v
WHERE  dimension_code = 'PRODUCT';

Because the view already performs the lookup joins and enforces the plan_type filter, integration developers can query it directly without reproducing the underlying join logic.