Search Results msd_scenarios

Overview

The MSD.MSD_DP_PARAMETERS table is a core configuration and metadata repository within the Oracle Demand Planning (MSD) schema of Oracle E-Business Suite, present in releases 12.1.1 and 12.2.2. It stores the input and output parameters that define how a Demand Plan is executed, populated, and consumed by the Oracle Express analytic engine. Input parameters govern which historical and forecast data is read from the planning server, while output parameters define the scenarios and calculations that Oracle Express generates and writes back to the planning server.

Because the table holds descriptive attributes that qualify a parent Demand Plan rather than the transactional facts themselves, it is best characterized as satellite-leaning in a Data Vault modeling sense. It behaves as a satellite anchored to the Demand Plan hub (MSD_DEMAND_PLANS via DEMAND_PLAN_ID), capturing the granular, historized parameter definitions attached to each plan. In the 12.2.2 documented schema the table contains 45 columns and is stored in the APPS_TS_TX_DATA tablespace with a 10% PCTFREE. Rows are uniquely identified by the MSD_DP_PARAMETERS_PK primary key on PARAMETER_ID.

Key Information Stored

The most significant columns fall into identification, classification, and behavioral-control groups:

• PARAMETER_ID — The surrogate primary key, generated from the MSD_DP_PARAMETERS_S sequence. It uniquely identifies each parameter row.
• DEMAND_PLAN_ID — Foreign key to MSD_DEMAND_PLANS, tying the parameter to its owning Demand Plan.
• PARAMETER_TYPE — Classifies the parameter based on the MSD_DATA_ELEMENT lookup (Booking History, Shipment History, Opportunity History, Input/Output Scenario, Manufacturing Forecast, Sales Forecast, Supply Plan).
• PARAMETER_NAME — Required for scenario, manufacturing, and sales forecast parameters.
• START_DATE and END_DATE — Define the historical window read for the parameter; when null, values default to the scenario Horizon Start/End dates from MSD_SCENARIOS.
• INPUT_SCENARIO_ID / OUTPUT_SCENARIO_ID — Link the parameter to source or destination scenarios.
• INPUT_DEMAND_PLAN_ID — References an alternate plan used as input.
• FORECAST_BASED_ON, FORECAST_USED, QUANTITY_USED, AMOUNT_USED — Specify the demand measures driving the calculation.
• PERIOD_TYPE, FACT_TYPE, VIEW_NAME — Control aggregation and data-shaping behavior.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID — Standard EBS audit and concurrent-program tracking columns.
• ZD_EDITION_NAME — The editioning column supporting online patching (Edition-Based Redefinition) in 12.2.x.

Two indexes support access: the unique index MSD_DP_PARAMETERS_U1 on (PARAMETER_ID, ZD_EDITION_NAME), which serves as the business-key candidate, and the non-unique index MSD_DP_PARAMETERS_N1 on DEMAND_PLAN_ID.

Common Use Cases and Queries

Consultants and developers query this table to audit plan configuration, troubleshoot missing forecast inputs, and verify scenario wiring. A typical diagnostic retrieves all parameters for a given plan:

• SELECT parameter_id, parameter_type, parameter_name, start_date, end_date FROM msd.msd_dp_parameters WHERE demand_plan_id = :plan_id;
• Identifying output scenarios: filter on PARAMETER_TYPE for 'Output Scenario' and join to MSD_SCENARIOS.
• Auditing date windows: compare START_DATE/END_DATE against scenario horizons to detect misconfigured history reads.
• Tracking who last modified a parameter via LAST_UPDATED_BY and LAST_UPDATE_DATE.
• Confirming edition context in 12.2.2 using ZD_EDITION_NAME.

Related Objects

• MSD.MSD_DEMAND_PLANS — Parent table; join on DEMAND_PLAN_ID.
• MSD.MSD_SCENARIOS — Provides default Horizon Start/End dates referenced by START_DATE and END_DATE.
• MSD.MSD_DATA_ELEMENT — Lookup source for PARAMETER_TYPE values.
• MSD.MSD_DP_PARAMETERS_S — Sequence generating PARAMETER_ID.
• MSD_DP_PARAMETERS_U1 / MSD_DP_PARAMETERS_N1 — Supporting unique and non-unique indexes.
• Oracle Express (Express Server) — External consumer that reads input parameters and writes output scenarios back to the planning server.