Search Results msd_event_products_pk

Overview

MSD_EVENT_PRODUCTS is a child table within the MSD (Demand Planning) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores the association between an event defined in MSD_EVENTS and the products (items or product groupings) participating in that event. Events in Demand Planning represent demand-shaping activities such as promotions, price changes, or marketing campaigns, and MSD_EVENT_PRODUCTS captures the product dimension of those activities so planners can model event-driven lift, cannibalization, and incremental demand at the appropriate level of the product hierarchy.

Because the table has a composite primary key of EVENT_ID and SEQ_ID, and holds descriptive attributes about the event-product relationship rather than transactional facts alone, a heuristic Data Vault classification would place it in a hub-leaning category — effectively a key-bearing entity that other satellites and links attach to. It is not a pure satellite; it is a dependent child of MSD_EVENTS and a parent to detail and relationship tables. The documented physical implementation shows 19 columns and a unique business-key index, MSD_EVENT_PRODUCTS_U1, on (EVENT_ID, SEQ_ID), which mirrors the primary key constraint MSD_EVENT_PRODUCTS_PK.

Key Information Stored

The table’s business identity is defined by the composite key EVENT_ID and SEQ_ID. EVENT_ID identifies the parent event in MSD_EVENTS, while SEQ_ID sequences the multiple product rows belonging to a single event. The unique index MSD_EVENT_PRODUCTS_U1 on these two columns is the documented business-key candidate, and the primary key constraint MSD_EVENT_PRODUCTS_PK enforces uniqueness on the same pair. There is no single-column surrogate primary key; the composite pair serves that role.

• PRODUCT_LVL_ID and PRODUCT_LVL_VAL — identify the level of the product hierarchy and the specific value at that level for the event-product association.
• START_TIME and END_TIME — the effective window during which the product participates in the event, enabling date-bounded demand modeling.
• SPREAD_PRODUCT_LVL_ID and SPREAD_PRODUCT_LVL_VAL — the product level and value used when spreading event demand across the hierarchy, supporting allocation to child products.
• SR_PRODUCT_LVL_PK — a stored reference to the source product-level key, useful for synchronizing with the planning server or external product masters.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the run that created or last modified the row.
• INSTANCE — the application instance identifier, relevant for multi-instance or replicated planning environments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns for change tracking and user accountability.

Common Use Cases and Queries

Typical reporting retrieves all products attached to a given event, often joining to MSD_EVENTS to obtain event metadata and to the product master for descriptions. A representative pattern:

• List products for an event: SELECT p.EVENT_ID, p.SEQ_ID, p.PRODUCT_LVL_ID, p.PRODUCT_LVL_VAL, p.START_TIME, p.END_TIME FROM MSD.MSD_EVENT_PRODUCTS p WHERE p.EVENT_ID = :event_id ORDER BY p.SEQ_ID;
• Active-event product coverage: filter on SYSDATE BETWEEN START_TIME AND END_TIME to identify products currently participating in demand events.
• Audit and lineage: query by REQUEST_ID or PROGRAM_ID to trace which concurrent program populated the rows.
• Hierarchy spreading analysis: compare PRODUCT_LVL_ID/LVL_VAL with SPREAD_PRODUCT_LVL_ID/LVL_VAL to verify whether event demand is recorded at the same level it is spread to.

These queries support promotion effectiveness reporting, forecast overrides, and reconciliation between the planning server and the EBS database.

Related Objects

MSD_EVENT_PRODUCTS is a hub within a small constellation:

• MSD_EVENTS — parent table; join on MSD_EVENT_PRODUCTS.EVENT_ID = MSD_EVENTS.EVENT_ID.
• MSD_EVT_PRODUCT_DETAILS — child detail table; joins on both EVENT_ID and SEQ_ID.
• MSD_EVT_PROD_RELATIONSHIPS — child relationship table; joins on EVENT_ID and SEQ_ID, typically modeling product-to-product relationships such as cannibalization or affinity.
• MSD_EVENT_PRODUCTS_PK and MSD_EVENT_PRODUCTS_U1 — the primary key constraint and unique index enforcing row uniqueness.

Together these objects comprise the event-product model used by Oracle Demand Planning to translate demand-shaping events into product-level forecast adjustments.