Results for “event_type_description”

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

Overview

The BIM_DIMV_EVENT_TYPES view is a reporting and integration object within the BIM – Marketing Intelligence product family of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Owned by the APPS schema and documented with a status of VALID, it presents a consolidated, read-only list of all event types defined in the Marketing Intelligence (BIM) module. The view serves as a dimensional source (hence the DIMV naming convention, indicating a dimensional view) for event-type reference data, exposing a denormalized, business-friendly projection of the underlying lookup values managed by Oracle Marketing (AMS).

Its principal role is to decouple consuming reports, extracts, and integration interfaces from the physical structure of the AMS lookup table. Because the view is declared WITH READ ONLY, it guarantees that downstream consumers can query event-type metadata without risk of accidental data modification, making it safe for concurrent use in analytics, ETL staging, and dimensional modeling scenarios.

Underlying Base Objects

The view is defined over a single documented base object: AMS_LOOKUPS, which is itself a view in the APPS schema. The definition filters that source strictly on the lookup type AMS_EVENT_TYPE, ensuring that only event-type lookup rows are surfaced. The documented view text is:

• Source object: AMS_LOOKUPS (VIEW)
• Filter predicate: AML.LOOKUP_TYPE = 'AMS_EVENT_TYPE'
• Access mode: WITH READ ONLY

Because it inherits its data from a view rather than a base table, the object reflects the current state of the AMS lookup definition and any downstream views layered upon it. Changes made to event-type lookup values in Oracle Marketing are therefore visible through BIM_DIMV_EVENT_TYPES without further transformation.

Key Columns

The view exposes six columns, each mapping a lookup attribute to a semantically meaningful event-type field:

• EVENT_TYPE — The lookup code (AML.LOOKUP_CODE) identifying the event type; this is the primary business key used in joins and filters.
• EVENT_TYPE_NAME — The user-facing meaning (AML.MEANING) of the event type, suitable for display in reports.
• EVENT_TYPE_DESCRIPTION — A longer descriptive text (AML.DESCRIPTION) providing additional context.
• ENABLED_FLAG — Indicates whether the event type is currently active or disabled (Y/N).
• START_DATE_ACTIVE — The date from which the event type becomes effective.
• END_DATE_ACTIVE — The date after which the event type is no longer effective.

Together, the date columns support effective-dated filtering, allowing consumers to retrieve only the event types valid as of a given point in time.

Common Use Cases and Queries

Typical scenarios include populating event-type drop-downs in custom OAF or Forms pages, feeding dimensional loads in a marketing data warehouse, and validating event captures in integration flows. A representative query returning all enabled event types valid today is:

• SELECT event_type, event_type_name, event_type_description
• FROM apps.bim_dimv_event_types
• WHERE enabled_flag = 'Y'
• AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

Because the view is read-only and standardized, it is the preferred access path for external reports and interfaces requiring the approved set of Marketing Intelligence event types, insulating them from the structural changes that may occur in the underlying AMS lookup model.