Results for “msd_evt_product_details”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSD_EVT_PRODUCT_DETAILS is a Demand Planning (MSD) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that functions as a child of MSD_EVENT_PRODUCTS. It stores the detail-level event information that qualifies and dimensionally scopes a planning event across multiple level hierarchies, including time, product, geography, sales channel, sales representative, organization, demand class, and user-defined levels. The table is owned by the MSD schema and is marked VALID in the documented ETRM metadata.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link. This classification is a modeling suggestion rather than a physical implementation detail: the table relates an event (via EVENT_ID to MSD_EVENT_PRODUCTS) to the dimensional level identifiers and values that define the event's scope. The presence of a composite primary key and multiple level/qualifier columns is consistent with a link-style construct rather than a pure hub or satellite.

Key Information Stored

The table is documented with 47 columns. The most significant columns and their roles are:

• EVENT_ID, DETAIL_ID, SEQ_ID — the composite primary key columns, defined by the unique constraint MSD_EVT_PRODUCT_DETAILS_PK. EVENT_ID links the detail row to its parent event in MSD_EVENT_PRODUCTS; DETAIL_ID and SEQ_ID distinguish individual detail lines within an event.
• RELATION_ID — identifies the relationship context for the detail row; it also appears in the documented foreign key relationships.
• TIME_LVL_ID, TIME_LVL_VAL_FROM, TIME_LVL_VAL_TO — the time-level identifier and its from/to range values, defining the event window.
• PRODUCT_LVL_ID, PRODUCT_LVL_VAL, SR_PRODUCT_LVL_PK — product-level definition and its surrogate reference.
• GEOGRAPHY_LVL_ID, GEOGRAPHY_LVL_VAL, SR_GEOGRAPHY_LVL_PK — geography-level definition and surrogate reference.
• SALESCHANNEL_LVL_ID, SALESCHANNEL_LVL_VAL, SR_SALESCHANNEL_LVL_PK — sales channel dimension scope.
• ORGANIZATION_LVL_ID, ORGANIZATION_LVL_VAL, SR_ORGANIZATION_LVL_PK — organization-level scope.
• QTY_MODIFICATION_TYPE, QTY_MODIFICATION_FACTOR, PRICE_MODIFICATION_TYPE, PRICE_MODIFICATION_FACTOR — numeric effects applied to the event for quantity and price.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, REQUEST_ID, PROGRAM_ID — standard EBS audit and concurrent program context columns.

The documented unique index MSD_EVT_PRODUCT_DETAILS_U1 (EVENT_ID, SEQ_ID, DETAIL_ID) is a business-key candidate in addition to the primary key, which constrains the same three columns in a different order. Surrogate primary keys for the referenced hierarchy levels are captured in the SR_* columns such as SR_PRODUCT_LVL_PK, SR_GEOGRAPHY_LVL_PK, SR_SALESCHANNEL_LVL_PK, SR_ORGANIZATION_LVL_PK, SR_DEMAND_CLASS_LVL_PK, SR_USER_DEFINED1_LVL_PK, and SR_USER_DEFINED2_LVL_PK.

Common Use Cases and Queries

Typical usage includes retrieving all detail lines for a given planning event, resolving the dimensional scope of an event before demand adjustment, and auditing quantity/price modification factors applied by the planning engine.

• Fetch all details for an event: SELECT * FROM MSD.MSD_EVT_PRODUCT_DETAILS WHERE EVENT_ID = :event_id ORDER BY SEQ_ID;
• Join parent and detail rows: SELECT e.event_id, d.detail_id, d.product_lvl_val, d.qty_modification_factor FROM MSD.MSD_EVENT_PRODUCTS e JOIN MSD.MSD_EVT_PRODUCT_DETAILS d ON e.event_id = d.event_id;
• Analyze quantity impacts by product level: aggregate QTY_MODIFICATION_FACTOR grouped by PRODUCT_LVL_VAL.
• Audit recent changes: filter on LAST_UPDATE_DATE or REQUEST_ID/PROGRAM_ID to trace which concurrent program populated or modified records.

Related Objects

The documented foreign key relationships center on the parent event table and the detail table's own sequencing key:

• MSD_EVENT_PRODUCTS — parent table; joined via MSD_EVT_PRODUCT_DETAILS.EVENT_ID to MSD_EVENT_PRODUCTS.EVENT_ID (and SEQ_ID as documented in the FK mapping).
• MSD_EVT_PRODUCT_DETAILS — self-referencing relationship through EVENT_ID and SEQ_ID as captured in the metadata.
• MSD_EVT_PRODUCT_DETAILS_U1 — unique index supporting business-key lookups on EVENT_ID, SEQ_ID, DETAIL_ID.
• MSD_EVT_PRODUCT_DETAILS_PK — primary key constraint on EVENT_ID, DETAIL_ID, SEQ_ID.

Downstream demand planning processes, worksheet and event maintenance logic, and any custom reporting that resolves event scope across time, product, geography, channel, organization, demand class, and user-defined levels will reference this table alongside MSD_EVENT_PRODUCTS.