Search Results msd_dp_parameters_pk

Overview

MSD_DP_PARAMETERS is a Demand Planning configuration and control table owned by the MSD schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores the input and output parameters that govern the execution of a Demand Plan. The table is populated and consumed by Oracle Express (the engine behind Demand Planning), which reads all input parameters to load data from the planning server and subsequently writes back output parameters generated during the planning run. In this respect, the table functions as the runtime control surface for a demand plan: it defines which scenarios feed the plan, how forecasts are aggregated, which periods and fact types are used, and which post-calculation behaviors apply.

Although the object is a standalone configuration store, its foreign key relationship to MSD_DEMAND_PLANS classifies it heuristically as satellite-leaning in a Data Vault model. That is, each parameter row enriches and qualifies a single parent demand plan rather than serving as an independent hub or an association between two hubs.

Key Information Stored

The table contains 45 documented columns. The primary key is the surrogate identifier PARAMETER_ID, enforced by MSD_DP_PARAMETERS_PK. A unique index, MSD_DP_PARAMETERS_U1, spans PARAMETER_ID and ZD_EDITION_NAME, which serves as a business-key candidate when edition-aware versioning is in use. The most functionally significant columns include:

• DEMAND_PLAN_ID – foreign key to MSD_DEMAND_PLANS, identifying the parent plan.
• PARAMETER_NAME and PARAMETER_TYPE – classify each parameter and distinguish input from output semantics.
• START_DATE and END_DATE – validity window for the parameter definition.
• INPUT_SCENARIO_ID and OUTPUT_SCENARIO_ID – source and target scenarios for the plan run.
• INPUT_DEMAND_PLAN_ID – references a source plan when parameters are inherited or copied.
• FORECAST_DATE_USED, FORECAST_BASED_ON, FORECAST_USED – control forecast selection logic.
• QUANTITY_USED and AMOUNT_USED – determine whether the plan operates on quantities or monetary values.
• PERIOD_TYPE and NUMBER_OF_PERIOD – define planning bucket granularity and horizon.
• VIEW_NAME and FACT_TYPE – identify the data view and fact used during loading.
• EQUATION, CALCULATED_ORDER, POST_CALCULATION – drive derived and sequenced calculations.
• EXCLUDE_FROM_ROLLING_CYCLE and ROUNDING_FLAG – control rolling-cycle inclusion and rounding.
• Standard audit columns, including LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, and PROGRAM_ID.

Common Use Cases and Queries

The principal use case is auditing and comparing parameter sets across demand plans or editions. Analysts frequently query which scenario, forecast basis, or time horizon a given plan uses. A typical pattern joins the parameter table to its parent plan:

• Retrieve all input parameters for an active plan: SELECT p.PARAMETER_NAME, p.PARAMETER_TYPE, p.INPUT_SCENARIO_ID FROM MSD.MSD_DP_PARAMETERS p WHERE p.DEMAND_PLAN_ID = :plan_id AND p.PARAMETER_TYPE = 'INPUT'.
• Compare editions using the unique key: SELECT p.DEMAND_PLAN_ID, p.ZD_EDITION_NAME, p.FORECAST_BASED_ON FROM MSD.MSD_DP_PARAMETERS p WHERE p.PARAMETER_ID = :param_id ORDER BY p.ZD_EDITION_NAME.
• Identify plans excluded from the rolling cycle: SELECT DEMAND_PLAN_ID, PARAMETER_NAME FROM MSD.MSD_DP_PARAMETERS WHERE EXCLUDE_FROM_ROLLING_CYCLE = 'Y'.
• Trace parameters back to the concurrent program that populated them using REQUEST_ID and PROGRAM_ID for reconciliation.

Reporting uses include configuration baselines, change history on FORECAST_BASED_ON or PERIOD_TYPE, and verification that output scenarios were correctly written after an Express run.

Related Objects

The following objects are the most significant in the ecosystem around MSD_DP_PARAMETERS:

• MSD_DEMAND_PLANS – parent table joined on MSD_DP_PARAMETERS.DEMAND_PLAN_ID = MSD_DEMAND_PLANS.DEMAND_PLAN_ID.
• MSD_DP_PARAMETERS_PK – primary key constraint on PARAMETER_ID.
• MSD_DP_PARAMETERS_U1 – unique index supporting edition-aware lookups on PARAMETER_ID and ZD_EDITION_NAME.
• Planning scenario tables referenced by INPUT_SCENARIO_ID and OUTPUT_SCENARIO_ID.
• Oracle Express engine interfaces and concurrent programs that consume and populate the parameter rows during plan execution.

Together these objects form the control layer that connects demand plan definitions to the Express planning engine.