Search Results duration_uom_code

Overview

The EDW_BIM_EVNT_EVENTS_LCV view is a Marketing Intelligence (BIM) reporting object within the Oracle E-Business Suite 12.1.1 / 12.2.2 data warehouse layer. It exposes event header information from the Marketing (AMS) module in a denormalized, conformed form suitable for loading into the Enterprise Data Warehouse (EDW) and for downstream business intelligence consumption. The view is classified as an LCV (Load Control / column-mapped view) and, as documented in the ETRM metadata, is not implemented in this database — meaning it exists as a reference definition only and is not deployed as a physical dictionary object in the target environment.

Its central purpose is to present a unified event record keyed by a synthetic primary key. The EVENT_PK is constructed by concatenating the event header identifier, the instance code, and the literal suffix '-EVENT', producing a globally unique key across multiple EBS instances consolidated into the warehouse. This design supports multi-instance data marts where the same logical event may exist in more than one source system.

Underlying Base Objects

The view text defines a join between two objects: AMS_EVENT_HEADERS_VL (aliased AEH) and EDW_LOCAL_INSTANCE (aliased INST). The ETRM metadata records no formally documented base objects, but the view text is authoritative for the join structure.

• AMS_EVENT_HEADERS_VL — the Marketing event header view providing all event-level attributes (name, type, status, registration parameters, scheduling, and marketing content).
• EDW_LOCAL_INSTANCE — the data warehouse instance registry, supplying INSTANCE_CODE to qualify each row by source EBS instance.
• The join is effectively unconditional within the defined view text, with the instance acting as a partitioning/qualifier dimension for the EDW load.

Key Columns

The user's search term, event_header_name, is exposed by this view under three aliases, each serving a distinct warehouse role:

• EVENT_DP and NAME — both mapped from AEH.EVENT_HEADER_NAME; the former as the display attribute, the latter as the conformed name.
• EVENT_HEADER_NAME — the verbatim source column, retained for traceability.
• EVENT_PK — synthetic key built from EVENT_HEADER_ID, INSTANCE_CODE and '-EVENT'.
• EVENT_HEADER_ID / PARENT_EVENT_HEADER_ID — primary key and self-referencing parent, enabling event hierarchies.
• EVENT_LEVEL, EVENT_TYPE_CODE, SYSTEM_STATUS_CODE, USER_STATUS_ID — classification and lifecycle columns.
• REG_* columns (REQUIRED_FLAG, INVITED_ONLY_FLAG, CHARGE_FLAG, MINIMUM/MAXIMUM_CAPACITY) — registration control attributes.
• ACTIVE_FROM_DATE / ACTIVE_TO_DATE, DAY_OF_EVENT, DURATION, DURATION_UOM_CODE — scheduling and validity dimensions.
• INVENTORY_ITEM_ID, ORG_ID — inventory and operating unit context for financial linkage.
• INSTANCE — the source instance code, plus CREATION_DATE and LAST_UPDATE_DATE for audit.

Common Use Cases and Queries

A frequent requirement is to report events by name across all consolidated instances. Because the view tags each row with INSTANCE_CODE, the following query resolves events by their header name and instance:

• List all events and their status: SELECT EVENT_HEADER_NAME, SYSTEM_STATUS_CODE, INSTANCE FROM EDW_BIM_EVNT_EVENTS_LCV;
• Filter by a specific name: SELECT * FROM EDW_BIM_EVNT_EVENTS_LCV WHERE EVENT_HEADER_NAME = :p_name;
• Reconcile instances: SELECT EVENT_HEADER_ID, INSTANCE, EVENT_PK FROM EDW_BIM_EVNT_EVENTS_LCV ORDER BY EVENT_HEADER_NAME;

Typical applications include event catalog dashboards, registration-capacity analysis, marketing campaign reporting, and cross-instance consolidation audits. As the object is not implemented in the database, consumers should treat it as a specification blueprint for building ETL mappings rather than a directly queryable view.