Search Results dp_enabled_flag




Overview
Explore in AI Chat

Overview

APPS.MSD_LEVEL_ASSOCIATIONS_V1 is a reporting view in Oracle E-Business Suite that presents Demand Planning (DP) and Sales and Operations Planning (SOP) level associations in a flattened, human-readable format. It combines records from the level association table with descriptive attributes from the level and level value tables, together with the application instance code, to expose the hierarchy of planning levels and their parent-child relationships. The view is owned by the APPS schema and is referenced by components of the Enterprise Territory and Resource Management / Demand Planning data model in EBS 12.1.1 and 12.2.2.

The view is defined as a UNION ALL of two branches: one for DP level values and level associations (where the related level records carry a null plan type) and one for SOP level values and level associations. A constant PLAN_TYPE column of 'DP' is projected in the documented branch, allowing consumers to distinguish the planning context of each row. The view therefore serves as a consolidated dictionary of the level hierarchy used by the planning engine, resolving surrogate keys to descriptive names and values.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

  • MSD_LEVEL_ASSOCIATIONS — the driving table, supplying the instance, level identifiers, surrogate level and parent-level keys, refresh and audit columns.
  • MSD_LEVELS — joined twice (aliased ML1 and ML2) to resolve the level name and dimension code for the current level and its parent level.
  • MSD_LEVEL_VALUES — joined twice (aliased MLV1 and MLV2) to resolve the current and parent level values, surrogate primary keys, and data-processing enabled flags.
  • MSC_APPS_INSTANCES — supplies the human-readable instance code for the source instance.
  • MSD_SR_UTIL — a package invoked in the select list to return the null description and null primary key when the data-processing enabled flag equals 3.

The joins are keyed on LEVEL_ID, INSTANCE, and the surrogate level primary keys, ensuring that each association row is paired with the matching level definitions and level values for both the child and the parent.

Key Columns

Common Use Cases and Queries

The view is most often queried to list the level hierarchy for a given instance or level, or to trace parent values for a specific level value. A representative query is:

  • SELECT level_name, dimension_code, level_value, parent_level_name, parent_level_value FROM apps.msd_level_associations_v1 WHERE instance_code = :instance_code ORDER BY level_name, level_value;
  • SELECT level_id, level_value, sr_level_pk, parent_level_id FROM apps.msd_level_associations_v1 WHERE level_id = :level_id; — retrieves all associations for a specific level, directly answering a search on LEVEL_ID.
  • SELECT DISTINCT level_id, level_name, dimension_code FROM apps.msd_level_associations_v1 WHERE plan_type = 'DP'; — enumerates the DP levels available for reporting or validation.

Typical applications include validating planning hierarchies before a data refresh, resolving surrogate keys to descriptive values in custom reports, and troubleshooting parent-child level mappings used by the Demand Planning engine.