Search Results msd_events_u1

Overview

The MSD.MSD_EVENTS table is a core transactional entity within the Oracle E-Business Suite Advanced Planning and Demand Planning (MSD) schema. It stores marketing event definitions used by the demand planning engine to model promotions, product introductions, phase-outs, and cannibalization effects on forecasting. Each row represents a distinct marketing event header that governs how demand is adjusted across products, geographies, customers, sales channels, sales representatives, and organizations. In Oracle EBS 12.1.1 and 12.2.2, this table resides in the APPS_TS_TX_DATA tablespace and is owned by the MSD schema, with the FND design data designation MSD.MSD_EVENTS. It serves as the parent header record for event detail lines held in MSD_EVENT_PRODUCTS.

Based on the mined foreign key structure, MSD_EVENTS exhibits hub-leaning characteristics under a Data Vault modeling heuristic. This suggests that EVENT_ID functions as a durable business key anchoring a hub, while event attributes could be modeled as satellites and the downstream references as links. This classification is a modeling suggestion only; the physical implementation in EBS is a conventional normalized table.

Key Information Stored

The table is anchored by the surrogate primary key EVENT_ID (NUMBER), which is also the single column of the unique index MSD_EVENTS_U1 in the APPS_TS_TX_IDX tablespace. This index enforces the primary key constraint MSD_EVENTS_PK and represents the sole documented business-key candidate for uniqueness.

• EVENT_ID — Surrogate primary key and the join column to all dependent tables.
• EVENT_NAME — Descriptive name (up to 240 characters) identifying the marketing event.
• EVENT_TYPE — Category governed by the MSD_EVENT_TYPE lookup: Competitive Promotion, Compulsory Promotion, New Product Introduction, Product Phase Out, Competitive/Compulsory Cannibalization, and the "Other" variants.
• INTRODUCTION_TYPE — Governed by the MSD_INTRODUCTION_TYPE lookup; either History Based or Forecast Based.
• PRODUCT_START_TIME and PRODUCT_END_TIME — DATE columns bracketing the effective window of the event.
• PRIORITY and EVENT_PRIORITY — Numeric ranking that resolves conflicts when multiple events overlap.
• PRODUCT_LVL_ID/PRODUCT_LVL_VAL, GEOGRAPHY_LVL_ID/GEOGRAPHY_LVL_VAL, CUSTOMER_LVL_ID/CUSTOMER_LVL_VAL — Dimension level identifiers and values scoping the event.
• SALESCHANNEL_LVL_ID, SALES_REP_LVL_ID, ORGANIZATION_LVL_ID, USER_DEFINED1_LVL_ID, USER_DEFINED2_LVL_ID — Additional scoping dimensions with matching _LVL_VAL columns.
• SPREAD_PRODUCT, MODIFICATION_TYPE, PERIOD_TYPE, FORECAST_BASIS, AUTO_UPDATE_SS_FLAG — Control flags for spreading, forecast basis, and automatic update behavior.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — Standard and enhanced WHO columns supporting audit and concurrent program traceability.

The table also carries ATTRIBUTE1 through ATTRIBUTE15, INSTANCE, and the SR_*_LVL_PK surrogate reference columns, bringing the documented column count to 68.

Common Use Cases and Queries

Reporting and interface development typically revolve around retrieving active events within a date window and resolving their dimensional scope. A representative query joins the header to its product lines:

SELECT e.event_id, e.event_name, e.event_type, e.priority, p.product_id
FROM msd.msd_events e, msd.msd_event_products p
WHERE e.event_id = p.event_id
AND sysdate BETWEEN e.product_start_time AND e.product_end_time;

Additional patterns include pivoting EVENT_TYPE against the MSD_EVENT_TYPE lookup for promotional mix analysis, filtering by dimension level values (for example, GEOGRAPHY_LVL_VAL) to isolate regional promotions, and auditing rows modified by a specific concurrent request using REQUEST_ID. Because PRIORITY governs overlap resolution, planners frequently query it to determine which event takes precedence when multiple definitions apply to the same product and period.

Related Objects

• MSD.MSD_EVENT_PRODUCTS — Child detail table joined on EVENT_ID; holds the product-level breakdown of each event header.
• MSD.MSD_DP_SCENARIO_EVENTS — References EVENT_ID, associating events with demand planning scenarios.
• MSD_EVENT_TYPE lookup — Validates the EVENT_TYPE column values.
• MSD_INTRODUCTION_TYPE lookup — Validates the INTRODUCTION_TYPE column values.
• FND concurrent program framework — Populates REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for processing traceability.
• FND standard WHO columns — LAST_UPDATE_DATE, CREATED_BY, and related audit fields shared across the MSD schema.

The table's hub-leaning profile and the MSD_EVENTS_U1 unique index make it the authoritative anchor for all event-related demand planning data in the ETRM 12.2.2 data model.