Search Results msd_data_element




Overview
Explore in AI Chat

Overview

APPS.MSD_DP_SCENARIOS_V is a reporting and integration view in Oracle EBS Advanced Supply Chain Planning / Demand Planning (MSD schema). It exposes Demand Planning scenario definitions in a denormalized, human-readable form by joining the base scenario table to its parent demand plan and to three FND lookup translations. In Oracle EBS 12.1.1 and 12.2.2 the view is owned by APPS and is intended for concurrent program output, BI Publisher reports, and interfaces that must present scenario metadata without re-implementing the lookup decoding logic.

The view resolves coded values into their display meanings: output period type, forecast date used, and forecast based on. This makes it the preferred source for any extract that must show a scenario's business attributes rather than raw lookup codes. Rows are ordered by demand plan and scenario name, which supports deterministic reporting output.

Underlying Base Objects

The documented base objects are:

Join logic: MDP.DEMAND_PLAN_ID = MDS.DEMAND_PLAN_ID is an inner join (every scenario must belong to a plan). FLV1 is also an inner join on LOOKUP_TYPE = 'MSD_PERIOD_TYPE', so a scenario whose period type has no lookup entry will be excluded. FLV2 and FLV3 are outer joins (indicated by the (+) operator) on LOOKUP_TYPE = 'MSD_DATE_USED' and LOOKUP_TYPE = 'MSD_DATA_ELEMENT' respectively, so missing lookup rows yield NULL meanings rather than dropping the scenario.

Key Columns

Common Use Cases and Queries

Typical uses include building scenario listings for Demand Planning administration reports, feeding downstream extracts, and validating that MSD_DATA_ELEMENT and MSD_DATE_USED lookups are populated before running forecast processes.

Active scenarios for one plan:

  • SELECT scenario_name, output_period_type, meaning, forecast_based_on, forecast_date_used
  • FROM apps.msd_dp_scenarios_v
  • WHERE demand_plan_id = :p_plan_id AND enable_flag = 'Y';

Scenarios whose forecast data element meaning is null (missing lookup):

  • SELECT demand_plan_name, scenario_name, forecast_based_on
  • FROM apps.msd_dp_scenarios_v
  • WHERE forecast_based_on IS NOT NULL AND flv3_meaning IS NULL;

Because the view is read-only and sourced from synonyms, it must be accessed through the APPS schema in custom code; do not query the base synonyms directly if consistent lookup decoding is required.