Search Results msd_event_type




Overview
Explore in AI Chat

Overview

APPS.MSD_EVENTS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) environment, defined in the Application Object Library schema and owned by APPS. It is part of the ETRM (Enterprise Trade and Risk Management) / Supply Chain Management data model and exposes the business events maintained in the MSD_EVENTS table alongside their corresponding lookup-code meanings. The view is documented in ETRM 12.2.2 and is available in the 12.1.1 / 12.2.2 code lines.

The view is primarily designed to present user-friendly, decoded values in place of the raw lookup codes stored on the base table. It resolves three separate lookups — MSD_EVENT_TYPE, MSD_INTRODUCTION_TYPE, and MSD_FORECAST_BASIS — by joining to FND_LOOKUP_VALUES_VL, returning the MEANING values for each. This makes MSD_EVENTS_V well suited for reporting layers, OBIEE/BI Publisher data models, and integration interfaces that must display or transmit descriptive text rather than internal codes. The view is read-only by nature and reflects current lookup definitions at query time.

Underlying Base Objects

The view is defined over two documented base objects:

  • MSD_EVENTS (SYNONYM) — the primary driving table, aliased ME. It supplies all event attributes, including the codes that the view decodes.
  • FND_LOOKUP_VALUES_VL (VIEW) — referenced three times as FLV1, FLV2, and FLV3 to resolve each lookup code into its meaning.

The join conditions are critical to the view's semantics. FLV1 (the event type lookup) is joined with an inner join, so only events whose EVENT_TYPE has a valid code in lookup type MSD_EVENT_TYPE are returned. FLV2 (MSD_INTRODUCTION_TYPE) and FLV3 (MSD_FORECAST_BASIS) are joined with the outer-join operator (+), meaning events with no matching introduction type or forecast basis are still returned, with null meanings for those columns.

Key Columns

Common Use Cases and Queries

Because MSD_EVENTS_V replaces lookup codes with their meanings, it is commonly used in event reports, dashboards, and integration extracts. A typical query lists all events with their decoded type, introduction type, and forecast basis:

  • SELECT visit.event_id, visit.event_name, visit.event_type, visit.meaning FROM apps.msd_events_v.
  • Filtering by type: WHERE msd_event_type = '<code>' using the lookup code as stored on MSD_EVENTS.
  • Reporting only active forecast-relevant events: WHERE forecast_basis IS NOT NULL.

The view is a convenient single source for decoding MSD_EVENTS without embedding join logic to FND_LOOKUP_VALUES_VL in each report.