Results for “event_type_id”

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

Overview

MSD_EVENTS_V is a seeded, VALID database view owned by the APPS schema within the MSD (Demand Planning) product family of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. It functions as the event header API for the Demand Planning "Events" feature, which allows planners to model promotional lifts, causal factors, and other demand-shaping activities that influence forecast generation. The view defines the types of Events and serves as the header to the companion API MSD_EVENT_PRODUCTS_V, which supplies the event-to-product association lines.

Because the view exposes decoded values rather than raw lookup codes, it is the preferred interface for reporting, integrations, and downstream planning logic that needs human-readable event classification. The PL/SQL APIs registered against it (typically via OTA-style table handlers) read and write MSD_EVENTS through this view, so the view acts as the supported programmatic access point to the underlying event data for Demand Planning and its integrations with Advanced Supply Chain Planning (ASCP).

Underlying Base Objects

The view is defined over two documented base objects:

• MSD_EVENTS (exposed in the database as a SYNONYM) — the primary transactional table holding the event records. All ID, name, description, priority, and WHO/tracing columns originate here.
• FND_LOOKUP_VALUES_VL (VIEW) — the standard Oracle Application Object Library lookup view, joined twice to translate the stored lookup codes into their display meanings.

Two outer joins to FND_LOOKUP_VALUES_VL decode the event type and introduction type. The first join is a mandatory (non-outer) join on LOOKUP_TYPE = 'MSD_EVENT_TYPE', meaning every event returned must resolve to a valid event type meaning. The second is an outer join on LOOKUP_TYPE = 'MSD_INTRODUCTION_TYPE', allowing events without a defined introduction type to still be reported with a null meaning. This design means the view is sensitive to the setup of these two lookup types in FND_LOOKUP_TYPES/FND_LOOKUP_VALUES: an inactive or missing event-type lookup value will suppress the corresponding row from the view result set.

Key Columns

The view exposes the following documented columns, in addition to the decoded meanings:

• ROW_ID — the ROWID of the MSD_EVENTS row, used as the unique row identifier for programmatic update/delete.
• INSTANCE — the planning instance (server) identifier, used in multi-instance MSD deployments.
• EVENT_ID — the unique numeric primary key of the event.
• EVENT_NAME and EVENT_DESCRIPTION — the user-entered short name and free-text description of the event.
• EVENT_TYPE / EVENT_TYPE_ID — the stored lookup code and its decoded meaning from the MSD_EVENT_TYPE lookup.
• INTRODUCTION_TYPE / INTRODUCTION_TYPE_ID — the stored code and decoded meaning from the MSD_INTRODUCTION_TYPE lookup (nullable via outer join).
• EVENT_PRIORITY — the ranking applied when multiple overlapping events affect the same product/period.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request and program tracing columns populated when the row was last touched by a concurrent program.

Common Use Cases and Queries

The view is most frequently used to list and validate the event header definitions maintained in Demand Planning, to reconcile events against their product lines in MSD_EVENT_PRODUCTS_V, and to drive integrations that publish event calendars to external forecasting or execution systems. A typical listing query is:

SELECT event_id, event_name, event_type, introduction_type,
       event_priority, creation_date, last_update_date
FROM   apps.msd_events_v
WHERE  event_type = 'PROMOTION'
ORDER  BY event_priority, event_name;

An audit-oriented variant restricting to changed rows, using the who columns, is:

SELECT event_id, event_name, last_updated_by, last_update_date
FROM   apps.msd_events_v
WHERE  last_update_date >= TRUNC(SYSDATE) - 7;

Join patterns against the products view are common, as the header alone carries no item reference:

SELECT h.event_id, h.event_name, p.inventory_item_id, p.organization_id
FROM   apps.msd_events_v          h,
       apps.msd_event_products_v   p
WHERE  h.event_id = p.event_id;

Because the event type join is mandatory, queries returning unexpectedly few rows should be diagnosed against the MSD_EVENT_TYPE lookup definition. All access should be granted through the APPS schema, with data integrity maintained by the registered APIs rather than by direct DML against MSD_EVENTS.