Results for “forecast_based_on”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSD_DP_SCENARIO_ALL_EVENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the MSD – Demand Planning product family. Its stated purpose is to consolidate all event records associated with a Demand Plan Scenario into a single, query-friendly result set. The event categories captured include Promotions, Cannibalization, Product Phase Out, New Product Introduction, and Miscellaneous Events. By exposing both the scenario-level context (demand plan, scenario name, horizon dates, forecast parameters) and the event-level detail (event name, event type, introduction type, priorities) in one structure, the view serves as the primary integration and reporting surface for downstream demand planning analytics, custom OBIEE/BIP reports, and middleware extracts that need a denormalized event picture.

Underlying Base Objects

The documented metadata identifies a single referenced base object: MSD_DP_SCENARIO_EVENTS_V (VIEW). The view text confirms this dependency directly — the active SELECT statement reads from MSD_DP_SCENARIO_EVENTS_V and projects the full column list. Notably, the implementation text preserves a commented-out UNION against MSD_DP_SCN_INTRO_EVENTS_V. This indicates the view was originally designed to combine standard scenario events with introduction events (new product introduction / phase-out) via a UNION ALL, but the introduction branch is currently disabled. The practical consequence is that the view today reflects the population of MSD_DP_SCENARIO_EVENTS_V only; any rows that exist solely in MSD_DP_SCN_INTRO_EVENTS_V will not appear. Consultants extending or troubleshooting this view should account for that commented UNION, since introduction-type columns remain in the projection.

Key Columns

The column list divides naturally into scenario/context attributes and event attributes.

• DEMAND_PLAN_ID, DEMAND_PLAN_NAME – Identifies the parent demand plan.
• SCENARIO_ID, SCENARIO_NAME, DESCRIPTION – Identify the scenario and provide its narrative description.
• OUTPUT_PERIOD_TYPE_ID, OUTPUT_PERIOD_TYPE – Define the planning bucket granularity (e.g., weekly, monthly).
• HORIZON_START_DATE, HORIZON_END_DATE – The planning horizon boundaries for the scenario.
• FORECAST_DATE_USED_ID, FORECAST_DATE_USED, FORECAST_BASED_ON_ID, FORECAST_BASED_ON – Forecast reference parameters.
• PRICE_LIST_NAME – Price list associated with the scenario.
• EVENT_ID, EVENT_NAME, EVENT_DESCRIPTION – Identify and describe the individual event.
• EVENT_TYPE_ID, EVENT_TYPE – The event_type_id is the key discriminator here; it drives which category (promotion, cannibalization, phase-out, new product introduction, miscellaneous) the event represents, with the paired lookup value surfacing the descriptive type.
• INTRODUCTION_TYPE_ID, INTRODUCTION_TYPE – Further classify introduction-related events.
• EVENT_ASSOCIATION_PRIORITY, DEFAULT_EVENT_PRIORITY – Establish precedence when multiple events affect the same item/period.

Common Use Cases and Queries

Typical applications include listing all events for a scenario, isolating events by type, and joining event data to forecast outputs for net-effect analysis. The event_type_id column is the standard filter for separating promotions from cannibalization or phase-out entries in analytical reports.

• All events for a scenario by name: SELECT event_id, event_name, event_type, event_association_priority FROM msd_dp_scenario_all_events_v WHERE scenario_name = :scenario AND demand_plan_name = :plan;
• Filter by event type (using the searched attribute): SELECT scenario_id, event_id, event_name, event_type FROM msd_dp_scenario_all_events_v WHERE event_type_id = :event_type_id;
• Horizon-bounded event inventory: SELECT demand_plan_name, scenario_name, event_name, event_type, horizon_start_date FROM msd_dp_scenario_all_events_v WHERE horizon_start_date >= :from_date ORDER BY event_association_priority DESC;
• Priority conflict check: SELECT event_id, event_name, event_association_priority, default_event_priority FROM msd_dp_scenario_all_events_v WHERE scenario_id = :scenario_id AND event_association_priority <> default_event_priority;

Because the view is a plain SELECT without bind variables, it can be consumed directly by BI Publisher data models, custom concurrent programs, and integration extracts. Queries should join back to MSD_DP_SCENARIO_EVENTS_V only when row-level timing or attributes not projected here are required; otherwise the view is self-sufficient for scenario-event reporting.