Search Results msd_dp_scn_events_pk

Overview

The MSD_DP_SCENARIO_EVENTS table resides in the MSD (Demand Planning) schema and forms part of the Oracle E-Business Suite Advanced Supply Chain Planning / Demand Planning data model. It is classified as a VALID table in both EBS 12.1.1 and 12.2.2. Functionally, the table stores the associations between a Demand Planning scenario and the events that are linked to that scenario, enabling planners to model the impact of discrete business events (such as promotions, price changes, or market disruptions) against a specific planning scenario and demand plan.

From a Data Vault modeling perspective, the mined foreign key structure — where EVENT_ID references MSD_EVENTS — suggests a satellite-leaning classification. In practice, the table behaves as a link-like association entity that ties three business keys (DEMAND_PLAN_ID, SCENARIO_ID, and EVENT_ID) together while carrying its own descriptive and control attributes. This classification should be treated as a heuristic modeling suggestion rather than a documented Oracle designation.

Key Information Stored

The table contains 16 documented columns in the 12.2.2 physical schema. The most significant are:

• DEMAND_PLAN_ID — Identifies the demand plan context for the event-scenario association; part of the composite primary key.
• SCENARIO_ID — The Demand Planning scenario to which the event is bound; part of the primary key.
• EVENT_ID — The associated event; part of the primary key and the sole documented foreign key, referencing MSD_EVENTS.
• EVENT_ASSOCIATION_PRIORITY — Controls the precedence or ranking of the event association when multiple events apply.
• DELETEABLE_FLAG — Indicates whether the association can be removed by the user or planning engine.
• ENABLE_NONSEED_FLAG — Governs whether non-seed (customer-defined) events are enabled for the scenario.
• ZD_EDITION_NAME — Supports the editioning / multi-versioning framework introduced in EBS 12.2.
• Standard WHO and concurrent program audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

The primary key is MSD_DP_SCN_EVENTS_PK over (DEMAND_PLAN_ID, EVENT_ID, SCENARIO_ID). A separate unique index, MSD_DP_SCN_EVENTS_U1, covers (DEMAND_PLAN_ID, SCENARIO_ID, EVENT_ID, ZD_EDITION_NAME), making it the business-key candidate that also accommodates the editioning column.

Common Use Cases and Queries

Typical reporting and diagnostics center on identifying which events are attached to a given scenario, priority-ordering those events, and auditing associations that are eligible for deletion or that involve non-seed definitions.

• List all events for a scenario: SELECT EVENT_ID, EVENT_ASSOCIATION_PRIORITY FROM MSD.MSD_DP_SCENARIO_EVENTS WHERE SCENARIO_ID = :scenario AND DEMAND_PLAN_ID = :plan;
• Join to event master data: SELECT e.EVENT_NAME, s.EVENT_ASSOCIATION_PRIORITY FROM MSD.MSD_DP_SCENARIO_EVENTS s JOIN MSD.MSD_EVENTS e ON e.EVENT_ID = s.EVENT_ID WHERE s.SCENARIO_ID = :scenario;
• Audit stale or user-modified rows using CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY.
• Identify associations flagged DELETEABLE_FLAG = 'Y' or ENABLE_NONSEED_FLAG = 'Y' for cleansing and configuration review.

Related Objects

• MSD_EVENTS — Parent table referenced via EVENT_ID; supplies event definitions.
• MSD_DP_SCENARIOS — Scenario master supplying SCENARIO_ID context.
• MSD_DEMAND_PLANS — Demand plan master supplying DEMAND_PLAN_ID context.
• MSD_DP_SCN_EVENTS_PK / MSD_DP_SCN_EVENTS_U1 — Constraint and unique index enforcing the composite and business-key uniqueness.
• MSD concurrent programs and Demand Planning APIs — Consume and maintain these associations during plan generation and scenario copying.