Search Results msd_dp_scenario_events_v




Overview
Explore in AI Chat

Overview

The MSD_DP_SCENARIO_EVENTS_V view is an APPS-owned database view within the MSD (Demand Planning) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents the complete set of demand planning events that are associated with a Demand Plan scenario, with one deliberate exclusion: New Product Introduction (NPI) events are not surfaced by this view. The event categories represented are Promotion, Cannibalization, Product Phase Out, and Miscellaneous events.

The view exists to give report authors, discoverer workbooks, concurrent programs, and integration interfaces a single denormalized access point that combines scenario-level header attributes, event master attributes, and the scenario-to-event association details. Rather than requiring callers to join the scenario view, the event master view, and the association table independently, the view performs that join internally and exposes a flat row-per-association result set. This makes it well suited to demand planning review reports, event calendars, and downstream extracts feeding forecasting or promotional planning processes.

Underlying Base Objects

The view text joins three documented base objects:

  • MSD_DP_SCENARIOS_V (aliased MDSV) — supplies the Demand Plan and scenario header context, including horizon dates, period type, forecast basis, and price list.
  • MSD_EVENTS_V (aliased MEV) — supplies the event master definition, including event name, description, event type, and introduction type.
  • MSD_DP_SCENARIO_EVENTS (aliased MDSE, referenced via synonym) — the association detail object that links a specific event to a specific demand plan and scenario, and carries association-level attributes such as priority and the standard WHO/audit columns.

The join conditions are equality-based across three key pairs: MDSV.DEMAND_PLAN_ID = MDSE.DEMAND_PLAN_ID, MDSV.SCENARIO_ID = MDSE.SCENARIO_ID, and MEV.EVENT_ID = MDSE.EVENT_ID. The view therefore returns one row per scenario-event association, not one row per scenario or per event.

Key Columns

Common Use Cases and Queries

Typical uses include extracting all non-NPI events for a scenario for review, reconciling scenario event priorities against the event master defaults, and feeding event calendars into downstream planning reports.

List all events for a given demand plan and scenario:

  • SELECT event_id, event_name, event_type, event_association_priority FROM msd_dp_scenario_events_v WHERE demand_plan_id = :p_plan AND scenario_id = :p_scenario ORDER BY event_association_priority;

Identify priority overrides where scenario association differs from the event default:

  • SELECT demand_plan_name, scenario_name, event_name, event_association_priority, default_event_priority FROM msd_dp_scenario_events_v WHERE event_association_priority <> default_event_priority;

Audit which concurrent request last modified the associations:

  • SELECT scenario_name, event_name, last_update_date, last_updated_by, request_id, program_id FROM msd_dp_scenario_events_v WHERE last_update_date >= :p_since;

Report all events by type across the planning horizon:

  • SELECT event_type, event_name, demand_plan_name, scenario_name, horizon_start_date, horizon_end_date FROM msd_dp_scenario_events_v ORDER BY event_type, horizon_start_date;

Because NPI events are excluded by design, reports requiring NPI data must query the constituent base objects directly rather than this view.