Search Results waitlist_action_type_code




Overview
Explore in AI Chat

Overview

The view EDW_BIM_EVNT_EVTOFFERS_LTC_IV is a reporting object within the Oracle E-Business Suite BIM – Marketing Intelligence module. It exposes event offer data for extraction into the Enterprise Data Warehouse (EDW), functioning as an interface view (indicated by the _IV suffix) that flattens event and event-offer attributes into a single denormalized result set. In the Oracle EBS 12.1.1 and 12.2.2 environments, objects of this type are typically consumed by Oracle Business Intelligence, Discoverer workbooks, and custom operational reports that require a consolidated view of marketing event offerings without navigating the underlying transactional schema.

The _LTC_IV naming convention ("Load to Cube / Interface View") signals that the object is intended for batch or incremental extraction rather than online transactional processing. It carries a ROW_ID pseudo-column derived from ROWID, which supports delta detection during extraction routines. The metadata notes that the view is not implemented in this database, meaning it exists as a deployment artifact on customer instances rather than a seeded object in every environment.

Underlying Base Objects

The documented metadata records no explicit base tables, but the view text clearly selects from EDW_BIM_EVNT_EVTOFFERS_LTC. This LTC (Load-to-Cube) object is the staging or materialized layer from which the interface view projects and renames certain columns. Notable transformations include aliasing the source WAITLIST_ACTION_TYPE_CODE as OPERATION_CODE, indicating the view is designed to carry an operation indicator for downstream cube loads.

Because the view is a simple projection with no joins, filter predicates, or aggregation, its grain matches the underlying EDW_BIM_EVNT_EVTOFFERS_LTC table exactly: one row per event offer. The SECURITY_GROUP_ID and ORG_ID columns confirm that multi-org and security-group filtering are expected to be applied by the consuming report or extraction program, not by the view itself.

Key Columns

Common Use Cases and Queries

The most frequent query pattern filters or joins on PRICELIST_HEADER_ID to reconcile event offers against pricing data.

SELECT evtoffer_id,
       event_offer_name,
       pricelist_header_id,
       pricelist_line_id,
       inventory_item_id,
       system_status_code
  FROM edw_bim_evnt_evtoffers_ltc_iv
 WHERE pricelist_header_id = :p_pricelist_header_id;

Incremental extraction for the EDW typically relies on the audit columns:

SELECT *
  FROM edw_bim_evnt_evtoffers_ltc_iv
 WHERE last_update_date >= :p_last_run_date;

Other uses include resolving the price list context for an event offer, auditing offers that reference a specific price list header, and feeding marketing event fact tables with priced offer attributes. Because the view carries no filter, consumers should always constrain by ORG_ID, SECURITY_GROUP_ID, or a date range to bound result sets.