Search Results forecast_basis_id

Overview

APPS.MSD_DP_SCENARIO_ALL_EVENTS_V is a reporting view within the Oracle E-Business Suite Demand Planning (DP) module, part of the Advanced Supply Chain Planning / ETRM (Enterprise Transaction Reporting Model) layer. The view consolidates demand plan scenario event definitions into a single, denormalized presentation structure, joining scenario-level attributes with event-level attributes for reporting, integration, and analytical extraction purposes. Its name indicates an "all events" scope: it presents the universe of events configured against demand plan scenarios, including those originating from the standard scenario events view, with the view text also anticipating a UNION with the scenario introduction events view (currently commented out in the delivered definition).

The view is especially relevant to users searching for forecast_date_used, a column exposed here to identify which forecast date rule a scenario's events rely upon when generating forecasts.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is owned by APPS and is defined over a single referenced base object:

• MSD_DP_SCENARIO_EVENTS_V — a view (not a base table) providing scenario event rows.

The SELECT list references columns such as DEMAND_PLAN_ID, SCENARIO_ID, OUTPUT_PERIOD_TYPE_ID, HORIZON_START_DATE, FORECAST_DATE_USED_ID, FORECAST_BASED_ON_ID, EVENT_ID, EVENT_TYPE_ID, and others, projecting them from the base scenario events view. The view text also contains a commented-out UNION against MSD_DP_SCN_INTRO_EVENTS_V, which, if enabled, would append introduction event rows using EVENT_PRIORITY in place of EVENT_ASSOCIATION_PRIORITY. As delivered, the active definition resolves against MSD_DP_SCENARIO_EVENTS_V only.

Key Columns

• DEMAND_PLAN_ID / DEMAND_PLAN_NAME — identifies the owning demand plan.
• SCENARIO_ID / SCENARIO_NAME / DESCRIPTION — identifies the scenario and its narrative.
• OUTPUT_PERIOD_TYPE_ID / OUTPUT_PERIOD_TYPE — the planning bucket granularity (e.g., days, weeks, periods).
• HORIZON_START_DATE / HORIZON_END_DATE — the planning horizon bounds for the scenario.
• FORECAST_DATE_USED_ID / FORECAST_DATE_USED — the specific forecast date rule applied, central to interpreting how forecast dates are derived.
• FORECAST_BASED_ON_ID / FORECAST_BASED_ON — the basis from which forecasts are generated.
• PRICE_LIST_NAME — associated price list for scenario costing or pricing.
• EVENT_ID / EVENT_NAME / EVENT_DESCRIPTION / EVENT_TYPE_ID / EVENT_TYPE — event identity and classification.
• INTRODUCTION_TYPE_ID / INTRODUCTION_TYPE — how the event is introduced into the plan.
• FORECAST_BASIS_ID / FORECAST_BASIS — the forecasting basis at event level.
• EVENT_ASSOCIATION_PRIORITY / DEFAULT_EVENT_PRIORITY — priority values governing event application.

Common Use Cases and Queries

Typical uses include auditing which forecast date rule applies to a scenario's events, reconciling event priority assignments, and driving downstream extracts into planning engines or BI repositories.

SELECT demand_plan_id,
       scenario_id,
       scenario_name,
       event_id,
       event_name,
       forecast_date_used,
       forecast_based_on,
       event_association_priority
  FROM apps.msd_dp_scenario_all_events_v
 WHERE scenario_id = :p_scenario_id
 ORDER BY event_association_priority DESC;

Filtering by forecast date usage supports validation exercises:

SELECT DISTINCT forecast_date_used_id,
       forecast_date_used
  FROM apps.msd_dp_scenario_all_events_v
 WHERE demand_plan_id = :p_plan_id;

Because the view is read-only and derives from a documented base view, queries should be restricted by DEMAND_PLAN_ID or SCENARIO_ID to avoid full scans, and it should not be used for direct DML.