Search Results msd_evt_prod_relationships




Overview
Explore in AI Chat

Overview

MSD_EVT_PROD_RELATIONSHIPS is a child table in the MSD (Demand Planning) schema of Oracle E-Business Suite, owned by the MSD database account and valid in both release 12.1.1 and 12.2.2. It stores relationship information that supports New Product Introductions (NPI) within the Demand Planning module. The table functions as a subordinate to MSD_EVENT_PRODUCTS, adding the relational detail that links products to planning events at the granular level required for NPI forecasting, launch phasing, and lifecycle transitions.

From a dimensional modeling perspective, the metadata's heuristic classification leans toward a satellite. This suggests the table is best understood as an attribute-bearing structure that hangs off a parent event-product anchor, recording descriptive and behavioral details — such as lag, time windows, and quantity modification factors — rather than acting as an independent hub or a pure link between business entities.

Key Information Stored

The table contains 22 documented columns. The most significant include:

The unique index MSD_EVT_PROD_RELATIONSHIPS_U1 on (EVENT_ID, SEQ_ID, RELATION_ID) serves as a business-key candidate, reinforcing the natural identification of a relationship within an event-product context.

Common Use Cases and Queries

Typical scenarios involve NPI forecasting, where planners define how a new product ramps in relation to an existing event. Analytical queries join this table to its parent to retrieve relationship details:

SELECT r.RELATION_ID, r.EVENT_ID, r.SEQ_ID, r.NPI_PROD_RELATIONSHIP,
       r.LAG, r.START_TIME, r.END_TIME,
       r.QTY_MODIFICATION_TYPE, r.QTY_MODIFICATION_FACTOR
FROM   MSD.MSD_EVT_PROD_RELATIONSHIPS r
WHERE  r.EVENT_ID = :event_id
ORDER  BY r.SEQ_ID;

Reporting use cases include auditing quantity modification rules, validating effective-date windows, and tracing concurrent program lineage via REQUEST_ID and PROGRAM_ID. Data conversion and integration scripts frequently extract rows filtered by LAST_UPDATE_DATE for incremental loads into planning engines.

Related Objects

  • MSD_EVENT_PRODUCTS — The direct parent table. Join on MSD_EVT_PROD_RELATIONSHIPS.EVENT_ID = MSD_EVENT_PRODUCTS.EVENT_ID (with SEQ_ID as an additional correlating key).
  • MSD_EVENTS (MSD_EVENT_...) family — Event headers that govern product events referenced upstream.
  • MSD_EVENT_PRODUCT_... dependent children — Sibling child tables of MSD_EVENT_PRODUCTS organized alongside this relationship table.
  • MSD_PRODUCT_LEVEL / product hierarchy objects — Referenced via PRODUCT_LVL_ID, PRODUCT_LVL_VAL, and SR_PRODUCT_LVL_PK.
  • MSD concurrent programs and requests — Correlated through PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID for lineage.

Together these objects form the event-product data model that underpins New Product Introduction planning in MSD Demand Planning.