Results for “forecast_based_on_id”
30 results
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.
-
This view provides all the Events - i.e., Promotion, Cannibalization, Product Phase Out, New Product Introduction, and Miscellaneous Events that are associated with a Demand Plan Scenario.
APPS.MSD_DP_SCENARIO_ALL_EVENTS_V·↳ MSD_DP_SCENARIO_EVENTS_V·Explore MSD module →
-
This view provides all the Events - i.e., Promotion, Cannibalization, Product Phase Out, New Product Introduction, and Miscellaneous Events that are associated with a Demand Plan Scenario.
APPS.MSD_DP_SCENARIO_ALL_EVENTS_V·↳ MSD_DP_SCENARIO_EVENTS_V·Explore MSD module →
-
This view provides all the Events except for New Product Introduction Event - i.e., Promotion, Cannibalization, Product Phase Out, and Miscellaneous Events that are associated with a Demand Plan Scenario.
APPS.MSD_DP_SCENARIO_EVENTS_V·↳ MSD_DP_SCENARIOS_CS_V·↳ MSD_DP_SCENARIO_EVENTS·↳ MSD_EVENTS_V·Explore MSD module →
-
View: MSD_DP_SCENARIOS_CS_V 12.1.1
This table provides the Scenarios to be generated from a particular Demand Plan.
APPS.MSD_DP_SCENARIOS_CS_V·↳ MSD_DP_SCENARIOS·↳ MSD_DP_SCENARIOS_VL·Explore MSD module →
-
This view provides all the Events except for New Product Introduction Event - i.e., Promotion, Cannibalization, Product Phase Out, and Miscellaneous Events that are associated with a Demand Plan Scenario.
APPS.MSD_DP_SCENARIO_EVENTS_V·↳ MSD_DP_SCENARIOS_CS_V·↳ MSD_DP_SCENARIO_EVENTS·↳ MSD_EVENTS_V·Explore MSD module →
-
View: MSD_DP_SCENARIOS_V 12.2.2
This table provides the Scenarios to be generated from a particular Demand Plan.
APPS.MSD_DP_SCENARIOS_V·↳ FND_LOOKUP_VALUES_VL·↳ MSD_DEMAND_PLANS·↳ MSD_DP_SCENARIOS·Explore MSD module →
-
View: MSD_DP_SCENARIOS_V 12.1.1
This table provides the Scenarios to be generated from a particular Demand Plan.
APPS.MSD_DP_SCENARIOS_V·↳ FND_LOOKUP_VALUES_VL·↳ MSD_DEMAND_PLANS·↳ MSD_DP_SCENARIOS·Explore MSD module →
-
View: MSD_DP_SCENARIOS_CS_V 12.2.2
This table provides the Scenarios to be generated from a particular Demand Plan.
APPS.MSD_DP_SCENARIOS_CS_V·↳ MSD_DP_SCENARIOS·↳ MSD_DP_SCENARIOS_VL·Explore MSD module →
-
View: MSD_DP_OUTPUT_PRS_V 12.2.2
This view specifies the Output Parameters for a demand plan. This is a subset of the MSD_DP_PARAMETERS_V. This view has only the columns required for the output parameters for a demand plan. For the description of the columns of this API, p
Not implemented in this database·Explore MSD module →
-
View: MSD_DP_OUTPUT_PRS_V 12.1.1
This view specifies the Output Parameters for a demand plan. This is a subset of the MSD_DP_PARAMETERS_V. This view has only the columns required for the output parameters for a demand plan. For the description of the columns of this API, p
Not implemented in this database·Explore MSD module →
-
Not implemented in this database·Explore MSD module →
-
Not implemented in this database·Explore MSD module →
-
Not implemented in this database·Explore MSD module →
-
Not implemented in this database·Explore MSD module →
-
View: MSD_DP_PARAMETERS_V 12.1.1
This view stores the Parameters (both Input as well as Output) to be used by a Demand Plan. This will be used by Oracle Express to load the Data from the PS (all Input Parameters) and the Output parameters will be used by Oracle Express to
Not implemented in this database·Explore MSD module →
-
View: MSD_DP_PARAMETERS_V 12.2.2
This view stores the Parameters (both Input as well as Output) to be used by a Demand Plan. This will be used by Oracle Express to load the Data from the PS (all Input Parameters) and the Output parameters will be used by Oracle Express to
Not implemented in this database·Explore MSD module →
-
eTRM - MSD Tables and Views 12.2.2
This is the fact table that stores the UOM conversions information.
-
eTRM - MSD Tables and Views 12.1.1
This is the fact table that stores the UOM conversions information.