Results for “msd_event_details_v”

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

Overview

MSD_EVENT_DETAILS_V is a reporting and integration view in the Oracle E-Business Suite Demand Planning module (MSD), documented for ETRM 12.1.1 and 12.2.2. It presents the promotional and causal event definitions maintained by planners alongside the granular detail lines that qualify each event, producing a single denormalized result set that is convenient for extract, reporting, and downstream planning consumption.

The view joins the event header view MSD_EVENTS_V to the base detail table MSD_EVENT_DETAILS on the EVENT_ID key. Because the header portion is itself sourced from a view, the result combines descriptive event attributes (name, description, type, modification, period type, introduction type, priority, and product spread dates) with the dimensional detail rows that define uplift factors and the level/value pairs against which each uplift applies.

The metadata records that the object is not implemented in the documented database and that no base objects are separately documented beyond the SQL text. The view is nevertheless part of the standard Demand Planning schema surface and is frequently referenced by custom extracts and DI/ODI style integration mappings that move event and promotion data between planning and execution systems.

Underlying Base Objects

The documented definition is a two-table join:

• MSD_EVENTS_V (aliased MEV) — supplies the event header columns, including EVENT_ID, EVENT_NAME, EVENT_DESCRIPTION, EVENT_TYPE, MODIFICATION, PERIOD_TYPE, INTRODUCTION_TYPE, SPREAD_PRODUCT, PRODUCT_START_TIME, PRODUCT_END_TIME, and EVENT_PRIORITY.
• MSD_EVENT_DETAILS (aliased MED) — supplies the detail line columns, including DETAIL_ID, UPLIFT_FACTOR, TIME_LVL_VAL_FROM, TIME_LVL_VAL_TO, and the level identifier/value pairs for product, geography, customer, sales channel, sales representative, organization, and two user-defined dimensions.

The join predicate is MEV.EVENT_ID = MED.EVENT_ID, a simple equi-join on the event identifier. One header row is therefore repeated for every detail row belonging to that event, which is the expected cardinality for a header/detail reporting view. No additional filter, outer join, or aggregation is present in the documented text.

Key Columns

Columns fall into two logical groups. The header group describes the event itself: EVENT_ID is the unique event key; EVENT_NAME and EVENT_DESCRIPTION are the user-facing labels; EVENT_TYPE_ID and EVENT_TYPE classify the event (for example, promotion or causal); MODIFICATION_TYPE_ID and MODIFICATION describe how the event alters the baseline; PERIOD_TYPE and INTRODUCTION_TYPE govern the time bucketing and how the event is introduced into the plan; SPREAD_PRODUCT, PRODUCT_START_TIME, and PRODUCT_END_TIME control product-level spreading; and EVENT_PRIORITY resolves conflicts between overlapping events.

The detail group qualifies where and how much the event applies. DETAIL_ID is the detail line key. UPLIFT_FACTOR carries the multiplicative or additive adjustment. TIME_LVL_VAL_FROM and TIME_LVL_VAL_TO define the time window of the detail line at the level identified by PERIOD_TYPE, which is the pair most commonly searched when reconciling event timing. The remaining columns follow a consistent pattern of a level identifier (PRODUCT_LVL_ID, GEOGRAPHY_LVL_ID, CUSTOMER_LVL_ID, SALESCHANNEL_LVL_ID, SALES_REP_LVL_ID, ORGANIZATION_LVL_ID, USER_DEFINED1_LVL_ID, USER_DEFINED2_LVL_ID) paired with the corresponding level value, allowing each uplift to be scoped across any supported planning dimension.

Common Use Cases and Queries

Typical uses include auditing promotion definitions, exporting events to external demand systems, validating that uplift windows align with product availability dates, and diagnosing why a forecast changed by tracing an event to its dimensional detail.

A basic listing of events with their time windows:

• SELECT EVENT_ID, EVENT_NAME, EVENT_TYPE, DETAIL_ID, UPLIFT_FACTOR, TIME_LVL_VAL_FROM, TIME_LVL_VAL_TO FROM MSD_EVENT_DETAILS_V ORDER BY EVENT_ID, DETAIL_ID;

Filtering detail rows by a specific event and time window:

• SELECT EVENT_NAME, UPLIFT_FACTOR, TIME_LVL_VAL_FROM, TIME_LVL_VAL_TO FROM MSD_EVENT_DETAILS_V WHERE EVENT_ID = :p_event_id AND TIME_LVL_VAL_FROM >= :p_from;

Aggregating uplift by event for high-level review:

• SELECT EVENT_ID, EVENT_NAME, COUNT(*) detail_lines, SUM(UPLIFT_FACTOR) total_uplift FROM MSD_EVENT_DETAILS_V GROUP BY EVENT_ID, EVENT_NAME;

Because the view performs no filtering, consumers should always constrain by EVENT_ID or time window where possible to avoid full scans of the joined result set.