Search Results ams_event_offers_vl




Overview
Explore in AI Chat

Overview

AMS_EVENT_OFFERS_VL is a Marketing (AMS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It returns general information about marketing event offerings, exposing the header-level attributes of an event offer — an entity that represents a bookable, registrable event such as a seminar, conference, or training session. The view is a "VL" (view of translated and untranslated columns) construct, meaning it joins the transactional base entity to its translation table so that both language-independent and language-specific attributes are presented in a single row. It is the principal public interface through which forms, concurrent programs, OAF pages, and custom integrations read event offer data without directly querying the underlying tables. At runtime the object reports a status of VALID, and it is the standard read path for marketing event offer information used across registration, partner, and revenue-related processes.

Underlying Base Objects

The view is defined over two documented base objects, both reached through APPS synonyms:

  • AMS_EVENT_OFFERS_ALL_B — the base (untranslated) table holding the core event offer attributes and all numeric, date, flag, and foreign key columns.
  • AMS_EVENT_OFFERS_ALL_TL — the translation (_TL) table holding language-dependent text columns for each event offer, keyed by language.

The view text is written against the alias B for the base table, so every non-translated column is sourced from AMS_EVENT_OFFERS_ALL_B, with the VL layer supplying the translated columns from AMS_EVENT_OFFERS_ALL_TL. Because the definition spans a _B and a _TL table, the view enforces the standard multi-language pattern: each event offer appears once per installed/selected language, and the VL mechanism exposes the appropriate translation without requiring the caller to join the _TL table explicitly.

Key Columns

The view exposes a broad column set that supports event setup, registration control, and financial tracking:

Common Use Cases and Queries

The view is used for event calendar reporting, registration eligibility checks, revenue and cost analysis, and partner-facing event extracts. Typical retrievals filter by status, date range, and organization:

  • List active upcoming offerings for an operating unit.
  • Determine whether registration is still open and whether the event is full.
  • Report forecasted versus actual revenue and cost by event type.
  • Feed external registration or e-commerce systems with event headers, venues, and pricing references.

Example:

SELECT event_offer_id, event_header_id, event_start_date,
       event_end_date, reg_start_date, reg_end_date,
       reg_maximum_capacity, actual_revenue, currency_code_tc
FROM   apps.ams_event_offers_vl
WHERE  active_flag = 'Y'
AND    org_id = :p_org_id
AND    event_start_date >= SYSDATE
ORDER BY event_start_date;

Custom code should query the view rather than the base tables to remain consistent with the multi-language join and to avoid replicating translation logic.