Search Results msd_dp_parameters_v




Overview
Explore in AI Chat

Overview

MSD_DP_PARAMETERS_V is a Demand Planning view in the Oracle EBS Advanced Planning / Demand Planning module (product code MSD). It exposes the parameter definitions used by a Demand Plan, covering both input parameters and output parameters. According to the ETRM metadata, the view is consumed by Oracle Express, which loads the input parameters from the planning server and uses the output parameters to complete plan execution. The view therefore acts as the integration surface between the EBS Demand Planning repository and the Oracle Express multidimensional engine, presenting plan parameters in a denormalized, human-readable form by resolving lookup codes into their translated meanings.

The view is a reporting and integration construct rather than a transactional object. It joins the base parameter table to demand plan headers, scenario headers, and nine separate references to FND_LOOKUP_VALUES_VL, which translates internal lookup codes into user-facing meanings. Note that the ETRM metadata records this view as "not implemented in this database" for the documented instance, so it may be absent or renamed in certain 12.1.1 / 12.2.2 environments depending on whether Demand Planning has been installed and configured.

Underlying Base Objects

The view is defined over five source tables:

  • MSD_DP_PARAMETERS (alias MPR) — the driving table holding one row per Demand Plan parameter.
  • MSD_DEMAND_PLANS (aliases MDP, MDP2) — supplies the plan name and is joined twice for the current plan and the input demand plan.
  • MSD_DP_SCENARIOS (aliases MDSV1, MDSV2) — supplies output and input scenario attributes, including scenario name, output period type, and horizon dates.
  • FND_LOOKUP_VALUES_VL (aliases FLV1 through FLV9) — the standard EBS lookup view, referenced nine times to translate parameter types and flags into meanings.

The primary join links MDP.DEMAND_PLAN_ID = MPR.DEMAND_PLAN_ID. Lookup joins on FLV1 and FLV2 are outer-less equality joins on lookup type and code, while the remaining lookup joins (FLV3 through FLV9) use the Oracle outer-join syntax (+), making those translations optional.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing a plan's parameter configuration, tracing input-to-output scenario mapping, and diagnosing integration failures between Demand Planning and Oracle Express.

SELECT demand_plan_name, parameter_name, parameter_type,
       meaning, period_type, start_date, end_date,
       input_scenario_id, output_scenario_id
FROM   msd_dp_parameters_v
WHERE  demand_plan_id = :p_plan_id;
SELECT p.demand_plan_name, p.parameter_name, p.meaning
FROM   msd_dp_parameters_v p
WHERE  p.exclude_from_rolling_cycle = 'Y'
ORDER  BY p.demand_plan_name, p.parameter_name;