Results for “new_product”

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

Overview

MSD_INTRO_EVENTS_V is a reporting and integration view within the Oracle E-Business Suite Advanced Planning and Demand Planning schema, owned by the MSD (Demand Planning) product family. The view presents introduction events configured inside Introduction Plans, which are used to model the phased introduction of new products or product families into a demand plan. Each row represents the association between an introduction plan and a specific event definition that governs how new products are introduced, modified, or spread across the planning horizon.

The view functions as a denormalized, read-only projection. Rather than requiring downstream reports or interfaces to join the three underlying objects manually, MSD_INTRO_EVENTS_V exposes plan-level attributes, event-level attributes, and the linking key in a single relational result set. This makes it suitable for BI Publisher reports, custom concurrent programs, OBIEE/ODI extracts, and ad hoc SQL against the planning schema.

The ETRM metadata records that the object is "Not implemented in this database," meaning no materialized deployment exists in the reference environment. Practically, the view is available only in instances where the Demand Planning (MSD) application is licensed and configured, and where Introduction Plans have been defined through the planning UI or loaded via the standard planning open interfaces.

Underlying Base Objects

The view text defines three referenced objects, though ETRM lists no documented base tables explicitly:

• MSD_INTRODUCTION_EVENTS (MIE) — the transactional/definition table storing the association between an introduction plan and an event. It supplies ROWID and the join keys INTRO_PLAN_ID and EVENT_ID.
• MSD_INTRODUCTION_PLANS_V (MIPV) — a view supplying plan-level attributes: INTRO_PLAN_ID, INTRO_PLAN_NAME, and PLAN_DESCRIPTION.
• MSD_EVENTS_V (MEV) — a view supplying event-level attributes, including event name, type, modification, period type, introduction type, product hierarchy level, spread flag, start/end times, and priority.

The joins are equijoins on MIPV.INTRO_PLAN_ID = MIE.INTRO_PLAN_ID and MEV.EVENT_ID = MIE.EVENT_ID. Because two of the three sources are themselves views, the effective query depth is greater than a single table scan, which is relevant when tuning extracts.

Key Columns

• ROW_ID — the physical row identifier of the introduction-event link record.
• INTRO_PLAN_ID, INTRO_PLAN_NAME, PLAN_DESCRIPTION — identify and describe the parent introduction plan.
• EVENT_ID, EVENT_NAME, EVENT_DESCRIPTION — identify and describe the event.
• EVENT_TYPE_ID, EVENT_TYPE — classification of the event (e.g., new product introduction, modification).
• MODIFICATION_TYPE_ID, MODIFICATION — the nature of any modification applied to an existing product.
• PERIOD_TYPE_ID, PERIOD_TYPE — the time bucket over which the event applies.
• INTRODUCTION_TYPE_ID, INTRODUCTION_TYPE — how the product is introduced into the plan.
• HEADER_PRODUCT_LVL_VAL — the product hierarchy level at which the event header is defined.
• SPREAD_PRODUCT — flag controlling whether demand is spread across the product hierarchy.
• PRODUCT_START_TIME, PRODUCT_END_TIME — effective time window for the product's introduction.
• EVENT_PRIORITY — precedence when multiple events compete for the same product/period.

Common Use Cases and Queries

Typical usages include auditing which events belong to which introduction plan, reporting event priorities and windows, and feeding downstream planning extracts.

List all events for a given plan:

SELECT INTRO_PLAN_NAME, EVENT_NAME, EVENT_TYPE,
       INTRODUCTION_TYPE, EVENT_PRIORITY
  FROM MSD_INTRO_EVENTS_V
 WHERE INTRO_PLAN_ID = :p_intro_plan_id
 ORDER BY EVENT_PRIORITY;

Trace which plans reference a particular event:

SELECT INTRO_PLAN_ID, INTRO_PLAN_NAME, EVENT_NAME
  FROM MSD_INTRO_EVENTS_V
 WHERE EVENT_ID = :p_event_id;

Report products with defined spread behaviour and their effective windows:

SELECT EVENT_NAME, SPREAD_PRODUCT,
       PRODUCT_START_TIME, PRODUCT_END_TIME
  FROM MSD_INTRO_EVENTS_V
 WHERE SPREAD_PRODUCT = 'Y'
 ORDER BY PRODUCT_START_TIME;