Results for “msd_dp_scn_intro_events_v”

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

Overview

MSD_DP_SCN_INTRO_EVENTS_V is a reporting view within the Oracle E-Business Suite Demand Planning module (product code MSD). It consolidates demand plan scenario definitions with the new product introduction events attached to each demand plan, presenting a single denormalized result set that spans planning horizon attributes, forecast configuration, introduction plan identity, and individual event details. The view is intended for read-only reporting and integration scenarios in which analysts need to correlate forecasting context with the product introduction events that influence demand. It is important to note that the ETRM documentation marks this object as Not implemented in this database, meaning it is a seeded, shipped view definition that may not be instantiated in every environment; consumers should verify its presence before depending on it in custom reports or interfaces.

Because Demand Planning is a licensed, advanced planning module, the view is generally referenced from custom reports, extracts, or downstream planning integrations rather than from standard transactional flows.

Underlying Base Objects

The view is defined over two documented views rather than base tables:

• MSD_INTRO_EVENTS_V (aliased MIEV) — the source of event-level attributes such as event identifier, name, type, modification type, introduction type, and product applicability flags.
• MSD_DP_SCENARIO_INTROS_V (aliased MDSIV) — the source of demand plan, scenario, horizon, forecast configuration, and introduction plan attributes.

The join is an inner join on INTRO_PLAN_ID, so only introduction plans that have at least one qualifying event are returned. No further base objects are documented for this view in the ETRM metadata, which means the multi-level dependency chain travels from these intermediate views back to the underlying demand planning and new product introduction tables. Oracle marks the metadata as proprietary and confidential.

Key Columns

• DEMAND_PLAN_ID / DEMAND_PLAN_NAME — identifies the parent demand plan owning the scenario.
• SCENARIO_ID / SCENARIO_NAME / DESCRIPTION — the specific planning scenario and narrative within the demand plan.
• OUTPUT_PERIOD_TYPE_ID / OUTPUT_PERIOD_TYPE — the time bucket granularity (e.g., weekly, monthly) for plan output.
• HORIZON_START_DATE / HORIZON_END_DATE — the planning horizon boundaries.
• FORECAST_DATE_USED_ID / FORECAST_DATE_USED and FORECAST_BASED_ON_ID / FORECAST_BASED_ON — metadata describing how forecasts are dated and derived.
• INTRO_PLAN_ID / INTRO_PLAN_NAME / PLAN_DESCRIPTION — the introduction plan linking the scenario to its events.
• EVENT_ID / EVENT_NAME / EVENT_DESCRIPTION — the individual new product introduction event.
• EVENT_TYPE_ID / EVENT_TYPE, MODIFICATION_TYPE_ID / MODIFICATION, INTRODUCTION_TYPE_ID / INTRODUCTION_TYPE, PERIOD_TYPE_ID / PERIOD_TYPE — classifications governing how the event affects the plan.
• NEW_PRODUCT / SPREAD_PRODUCT — flags identifying the products subject to the introduction or spread behavior.
• PRODUCT_START_TIME / PRODUCT_END_TIME — effective timing of the introduced or spread product.
• EVENT_PRIORITY — precedence used to resolve conflicts when multiple introduction events affect overlapping products or periods.

Common Use Cases and Queries

Typical uses include auditing which introduction events influence a scenario, validating event priority and timing against the planning horizon, and extracting event data into downstream planning or BI repositories.

• List all introduction events for a given demand plan and scenario.
• Filter events by introduction or modification type across multiple plans.
• Check events whose product start or end times fall outside the planning horizon.

Example queries:

• SELECT DEMAND_PLAN_NAME, SCENARIO_NAME, EVENT_NAME, EVENT_TYPE, PRODUCT_START_TIME FROM MSD_DP_SCN_INTRO_EVENTS_V WHERE DEMAND_PLAN_ID = :plan_id ORDER BY EVENT_PRIORITY;
• SELECT SCENARIO_NAME, EVENT_NAME, INTRODUCTION_TYPE, MODIFICATION FROM MSD_DP_SCN_INTRO_EVENTS_V WHERE INTRODUCTION_TYPE_ID = :type_id;
• SELECT EVENT_NAME, HORIZON_START_DATE, HORIZON_END_DATE, PRODUCT_START_TIME FROM MSD_DP_SCN_INTRO_EVENTS_V WHERE PRODUCT_START_TIME < HORIZON_START_DATE OR PRODUCT_END_TIME > HORIZON_END_DATE;

Because the object carries no documented primary key of its own and is marked as not implemented in all databases, always confirm availability and expected row cardinality in the target environment before embedding these queries into production reports.