Search Results msd_events




Overview
Explore in AI Chat

Overview

MSD_EVENTS is a Demand Planning table owned by the MSD schema that stores Marketing Events used by Oracle Demand Planning to model promotional and demand-affecting activities. Each row represents the header record for a marketing event and defines the type, timing, and dimensional scope of that event. It acts as the parent header to MSD_EVENT_PRODUCTS, which holds the product-level detail lines associated with each event, and is referenced by MSD_DP_SCENARIO_EVENTS to associate events with specific demand planning scenarios. The documented physical schema in ETRM 12.2.2 lists 68 columns, with the table status recorded as VALID.

Under the heuristic Data Vault classification mined from the foreign key structure, MSD_EVENTS is hub-leaning. This suggests modeling the table as a hub keyed on EVENT_ID, with the dimensional and attribute columns (such as EVENT_TYPE, PERIOD_TYPE, and the various level ID/value pairs) treated as descriptive attributes that may be split into satellite structures in a Data Vault design.

Key Information Stored

The primary key is MSD_EVENTS_PK, defined on EVENT_ID, which is the surrogate identifier for the event header. A unique index, MSD_EVENTS_U1, also covers EVENT_ID and serves as the documented business-key candidate. The most significant columns include:

Common Use Cases and Queries

MSD_EVENTS is primarily queried when analyzing or troubleshooting demand planning output driven by marketing events. Typical reporting retrieves event headers joined to their product detail and scenario associations.

  • Listing active events by type: SELECT EVENT_ID, EVENT_NAME, EVENT_TYPE FROM MSD_EVENTS WHERE EVENT_TYPE = :type;
  • Joining events to product lines: SELECT e.EVENT_NAME, p.* FROM MSD_EVENTS e JOIN MSD_EVENT_PRODUCTS p ON e.EVENT_ID = p.EVENT_ID;
  • Linking events to scenarios: SELECT e.EVENT_NAME, s.* FROM MSD_EVENTS e JOIN MSD_DP_SCENARIO_EVENTS s ON e.EVENT_ID = s.EVENT_ID;
  • Auditing recent changes via LAST_UPDATE_DATE for reconciliation and diagnostics.

Related Objects

The documented foreign key relationships establish the following significant dependencies:

  • MSD_EVENT_PRODUCTS — child detail table joined on MSD_EVENT_PRODUCTS.EVENT_ID to MSD_EVENTS.EVENT_ID.
  • MSD_DP_SCENARIO_EVENTS — associates events with demand planning scenarios, joined on EVENT_ID.

Additional Demand Planning objects — including scenario definitions, level/member hierarchies referenced by the *_LVL_ID and SR_*_LVL_PK columns, and the MSD planning engine programs that populate and read event data — depend on or interact with MSD_EVENTS. Because the table is the header for the event hierarchy, any analysis of event-driven demand plans should begin from this object and traverse to its child tables.