Search Results ams_event_headers_vl




Overview
Explore in AI Chat

Overview

AMS_EVENT_HEADERS_VL is a bilingual (translated) view owned by the APPS schema in Oracle E-Business Suite, defined within the Advanced Marketing (AMS) product family. It exposes the general information pertaining to marketing events at the header level, returning one logical row per event header for the session's current language. In Oracle EBS 12.1.1 and 12.2.2, the "_VL" suffix denotes a view that joins a base ("_B") table to its translation ("_TL") table so that language-dependent descriptive columns are surfaced alongside the transactional and attribute columns. The view is documented as VALID in ETRM for release 12.2.2 and is a standard integration and reporting entry point for event data consumed by AMS event management pages, concurrent programs, and custom reporting.

Underlying Base Objects

The view is defined over two synonyms that resolve to the actual marketing tables:

  • AMS_EVENT_HEADERS_ALL_B — the base table holding non-translated event header attributes such as status, scheduling, financial, and descriptive flexfield columns.
  • AMS_EVENT_HEADERS_ALL_TL — the translation table holding the language-specific descriptive text.

The join condition is B.EVENT_HEADER_ID = T.EVENT_HEADER_ID AND T.LANGUAGE = USERENV('LANG'), so the view automatically filters translation rows to the language of the current database session. A single event header therefore yields exactly one row in this view, assuming a translation row exists for the session language. The ROW_ID column is drawn from the base table's ROWID.

Key Columns

Columns exposed by the view fall into several functional groups:

Common Use Cases and Queries

Typical uses include event listing and registration reporting, revenue-versus-cost analysis by event, and integration extracts for external marketing or CRM systems. Because the translation filter applies automatically, queries return descriptions in the session's language without an explicit join to the _TL table.

A representative query selecting active events with their schedule and financials:

  • SELECT event_header_id, event_header_name, event_type_code, system_status_code, active_from_date, active_to_date, forecasted_revenue, actual_revenue FROM apps.ams_event_headers_vl WHERE active_flag = 'Y' AND org_id = :p_org_id ORDER BY active_from_date DESC;

A second example joining to registration or financial detail tables would use EVENT_HEADER_ID as the foreign key. Because the view is a _VL object, reports that must display multiple languages or fall back to a base language should query the underlying AMS_EVENT_HEADERS_ALL_TL table directly with an explicit LANGUAGE predicate.