Results for “event_status_code”

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

Overview

BIM_DIMV_EVENT_HEADERS is a read-only dimensional view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and associated with the BIM – Marketing Intelligence product family. As documented in ETRM, the view "shows all events," exposing marketing event header data in a denormalized, dimension-ready format suitable for analytical reporting, data extraction, and downstream integration with business intelligence tooling.

The view is frequently reached by users and developers searching for ams_event_headers_vl, since the AMS_EVENT_HEADERS_VL view is the sole documented base object from which BIM_DIMV_EVENT_HEADERS is constructed. The BIM_DIMV prefix indicates the object's role within the Marketing Intelligence dimensional model, where it serves as an event dimension source rather than a transactional interface object. The view is defined with the WITH READ ONLY clause, which prevents DML against it and reinforces its purpose as a query-only reporting artifact.

Underlying Base Objects

The ETRM documentation identifies exactly one referenced base object:

• AMS_EVENT_HEADERS_VL — the Marketing event headers view (a translated/MLS view over the underlying AMS_EVENT_HEADERS table).

BIM_DIMV_EVENT_HEADERS reads from this VL view and applies a fixed filter of EVTH.EVENT_LEVEL = 'MAIN', meaning only top-level (main) events flow through. Child or sub-events are excluded, and the filtered results are shaped into the dimensional column set described below. No joins to other base tables are documented; all projected values originate from AMS_EVENT_HEADERS_VL.

Key Columns

The view projects a defined set of columns from the event header source:

• ID — synthetic key formed as 'EVEH' || TO_CHAR(EVENT_HEADER_ID), used as the surrogate identifier in the dimensional model.
• VALUE — a truncated (80-character) event header name, typically presented as the dimension display value.
• EVENT_ID, EVENT_NAME, EVENT_DESCRIPTION — mapped from the event header ID, name, and description.
• EVENT_TYPE, EVENT_LEVEL, EVENT_STATUS_CODE, EVENT_STATUS_DATE — event classification, level (always 'MAIN'), workflow status, and last status change date.
• EVENT_SOURCE_CODE, EVENT_STANDALONE_FLAG — origin of the event and standalone indicator.
• ACTIVE_FROM_DATE, ACTIVE_TO_DATE, EVENT_ACTIVE_FLAG — effective dating and active status.
• EVENT_ITEM_ID — the associated inventory item ID.
• PARENT_EVENT_HEADER_ID — decoded to the same 'EVEH' || TO_CHAR(...) format, returning NULL when no parent exists.
• ORG_ID — hard-coded to NULL in the view definition; the view is not operating-unit partitioned.

Common Use Cases and Queries

Typical usage centers on marketing event dimension lookups, event listing reports, and joins into fact-style BI datasets. A representative query is:

• SELECT event_id, event_name, event_type FROM apps.bim_dimv_event_headers ORDER BY event_name;
• Filtering active events: ... WHERE event_active_flag = 'Y' AND SYSDATE BETWEEN active_from_date AND NVL(active_to_date, SYSDATE);
• Retrieving only standalone or item-linked events: ... WHERE event_standalone_flag = 'Y'; or ... WHERE event_item_id IS NOT NULL;
• Finding hierarchical relationships: ... WHERE parent_event_header_id IS NOT NULL;

Because ORG_ID returns NULL and the view is read-only, it is best consumed for reporting, dimensional loading, and cross-referencing against AMS_EVENT_HEADERS_VL when additional, unprojected event attributes are required.