Search Results msd_dp_scenarios




Overview
Explore in AI Chat

Overview

MSD_DP_SCENARIOS is a Demand Planning table owned by the MSD schema in Oracle E-Business Suite. It defines the forecast scenarios that may be generated from a given demand plan. Each row describes a scenario specification — its output period type, horizon window, history range, and the flags that govern whether the scenario is published, enabled, or consumed — associated with a parent demand plan. A scenario defined here is a specification only; for the scenario to actually be generated by the Oracle Express engine, a corresponding instance must also exist in the Demand Plan Parameters table. The table is therefore a definitional control point sitting between demand plan setup and scenario execution.

Under a heuristic Data Vault classification derived from its foreign key topology, MSD_DP_SCENARIOS is satellite-leaning. It carries descriptive, time-variant attributes about scenarios that hang off the MSD_DEMAND_PLANS hub, rather than acting as a pure hub or a many-to-many link. This classification is a modeling suggestion only, inferred from the single inbound foreign key to MSD_DEMAND_PLANS, and should be validated against actual usage and update patterns before being relied upon for data vault design.

Key Information Stored

The table's surrogate primary key is SCENARIO_ID, enforced through the MSD_DP_SCENARIOS_PK constraint. A second unique index, MSD_DP_SCENARIOS_U1, is defined on (SCENARIO_ID, ZD_EDITION_NAME), which reflects the edition-aware multi-tenant storage model in Oracle Demand Planning. The foreign key DEMAND_PLAN_ID to MSD_DEMAND_PLANS establishes the business association linking each scenario to its owning plan.

Common Use Cases and Queries

Typical reporting and administration use involves enumerating scenarios for a plan, filtering active or published scenarios, and auditing horizon and history settings. A representative query joins back to the parent plan:

  • List all scenarios for a specific plan: SELECT s.SCENARIO_ID, s.SCENARIO_NAME, s.STATUS FROM MSD_DP_SCENARIOS s WHERE s.DEMAND_PLAN_ID = :plan_id.
  • Retrieve enabled, publishable scenarios: filter on ENABLE_FLAG = 'Y' AND PUBLISH_FLAG = 'Y'.
  • Audit horizon coverage: select HORIZON_START_DATE, HORIZON_END_DATE, OUTPUT_PERIOD_TYPE ordered by start date.
  • Identify scenarios that reference supply plans via SUPPLY_PLAN_ID or SUPPLY_PLAN_NAME for reconciliation reporting.
  • Trace concurrency control using REQUEST_ID, PROGRAM_ID, and LAST_UPDATE_DATE to determine which concurrent program last modified a scenario.

Related Objects

The most significant related objects are those connected through the documented foreign key and the Demand Planning schema family.

  • MSD_DEMAND_PLANS — parent table; joined via MSD_DP_SCENARIOS.DEMAND_PLAN_ID = MSD_DEMAND_PLANS.DEMAND_PLAN_ID. This is the sole documented foreign key.
  • Demand Plan Parameters table — required companion instance enabling actual scenario generation by Oracle Express.
  • MSD_DP_SCENARIOS_PK / MSD_DP_SCENARIOS_U1 — the primary key and unique index constraints enforcing identity and edition uniqueness.

Because the metadata documents only one outbound foreign key, additional dependent views, concurrent programs, and server-side APIs should be confirmed against the specific EBS release (12.1.1 or 12.2.2) before being treated as authoritative dependencies.