Results for “cancellation_reason_code”

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

Overview

The EDW_BIM_EVNT_EVENTS_LTC table is a Marketing Intelligence (BIM) data object within the Oracle E-Business Suite, implemented in the BIM schema. It represents the event-level denormalized event record used by the Enterprise Data Warehouse (EDW) extract layer for Oracle Marketing and Advanced Marketing Services (AMS). The _LTC suffix denotes a "load-to-cache" or extraction staging variant, indicating that the table is populated from AMS source tables and serves as a flattened, reporting-optimized representation of marketing events—seminars, trade shows, webinars, training sessions, and certification events—along with their scheduling, registration, capacity, and coordination attributes.

With 55 documented columns and two unique indexes (EVENT_PK_KEY and the composite EVENT_PK/EVENT_PK_KEY), the table functions as a widened event dimension. The metadata's heuristic Data Vault classification labels this table as standalone, a modeling suggestion indicating it does not participate in a classic hub-link-satellite topology and instead behaves as a self-contained event satellite/flattened view. This makes it suitable for direct consumption by BI tools without multi-table joins for core event reporting.

Key Information Stored

The table's surrogate identifier is EVENT_PK, with a documented business-key candidate EVENT_PK_KEY, enforced by EDW_BIM_EVNT_EVENTS_LTC_U1 and EDW_BIM_EVNT_EVENTS_LTC_U2. The most significant columns include:

• EVENT_HEADER_ID — foreign key to the AMS event header, linking the EDW row to the transactional event master.
• EVENT_HEADER_NAME and NAME — the human-readable event title.
• PARENT_EVENT_HEADER_ID and EVENT_LEVEL — supporting hierarchical parent/child event structures.
• EVENT_TYPE_CODE, STREAM_TYPE_CODE, and PRIORITY_TYPE_CODE — classification and prioritization attributes.
• USER_STATUS_ID, SYSTEM_STATUS_CODE, and LAST_STATUS_DATE — workflow and lifecycle state tracking.
• ACTIVE_FROM_DATE and ACTIVE_TO_DATE, plus DAY_OF_EVENT, DURATION, and DURATION_UOM_CODE — scheduling and effective dating.
• REG_MINIMUM_CAPACITY, REG_MAXIMUM_CAPACITY, and the REG_*_FLAG columns — registration control parameters.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing multi-org data access.
• COORDINATOR_ID and OWNER_USER_ID — responsibility and ownership assignments.

Common Use Cases and Queries

Typical usage covers event performance dashboards, registration funnel analysis, and capacity planning. Because the table is pre-joined at the event level, analysts can query directly without traversing AMS base tables.

A representative pattern counts events by type and status within an effective window:

SELECT event_type_code, system_status_code, COUNT(*)
FROM   bim.edw_bim_evnt_events_ltc
WHERE  active_from_date BETWEEN :start_date AND :end_date
GROUP  BY event_type_code, system_status_code;

Capacity utilization reporting joins the AMS header for detailed registration counts:

SELECT e.event_header_name, e.reg_maximum_capacity
FROM   bim.edw_bim_evnt_events_ltc e
WHERE  e.event_header_id = :event_id;

Security-filtered extracts add a predicate on SECURITY_GROUP_ID to honor responsibility-based access, a common requirement for multi-org marketing deployments.

Related Objects

The following objects are most significant based on documented foreign-key relationships:

• AMS_EVENT_HEADERS_ALL_B — the base event header table; joined on EVENT_HEADER_ID = AMS_EVENT_HEADERS_ALL_B.EVENT_HEADER_ID.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for responsibility-based data restriction.
• AMS event child tables (registrations, schedules, teams) that share EVENT_HEADER_ID for drill-down beyond the EDW flattening.
• BIM Analytics and Marketing Intelligence dashboards that consume this table as their event dimension.

Because the metadata classifies the object as standalone, no other EDW link tables are required to resolve its relationships.