Search Results ams_event_headers_v




Overview
Explore in AI Chat

Overview

AMS_EVENT_HEADERS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. In both release 12.1.1 and 12.2.2 the object carries a VALID status and returns the general header-level information about marketing events. The view is a consolidation layer: rather than requiring consumers to join the event header table to lookup, status, and language tables manually, it presents a single denormalized row per marketing event, with descriptive values such as the event type meaning and the user status name already resolved. Because it is a view and not a table, it introduces no storage of its own and inherits the read-only, query-oriented behaviour expected of EBS reporting objects. It is commonly consumed by concurrent programs, BI Publisher reports, Discoverer worksheets, and custom PL/SQL packages that need event header attributes without reproducing the underlying join logic. The view also forms a convenient integration point for extract processes that publish marketing event data to external campaign management or CRM systems.

Underlying Base Objects

The documented definition is built over four referenced objects. AMS_EVENT_HEADERS_VL is the principal source and supplies the overwhelming majority of columns; the suffix VL indicates a translatable view that exposes the base language and translated (_TL) descriptions. AMS_USER_STATUSES_VL provides the user-defined status name through AUS.NAME. FND_LANGUAGES_VL supplies the NLS language description used to render MAIN_LANGUAGE_CODE. AMS_LOOKUPS, despite its name, is itself a view in the referenced object list and is outer-joined on LOOKUP_TYPE 'AMS_EVENT_TYPE' to translate EVENT_TYPE_CODE into the derived EVENT_TYPE column. The outer join preserves header rows whose event type code has no active lookup entry.

Key Columns

Common Use Cases and Queries

The view is typically queried to list active events, to reconcile funding amounts across currencies, or to feed downstream reporting. All queries should restrict EVENT_LEVEL, since the definition filters to main events when used as intended. A representative query returning event identity with currency and funding is:

SELECT event_header_id, event_header_name, event_type, currency_code_tc, fund_amount_tc, currency_code_fc, fund_amount_fc FROM apps.ams_event_headers_v WHERE active_flag = 'Y' AND TRUNC(active_from_date) >= TRUNC(SYSDATE) ORDER BY active_from_date;

A second pattern aggregates funding by functional currency for budget review:

SELECT currency_code_tc, COUNT(*) event_count, SUM(fund_amount_tc) total_fund FROM apps.ams_event_headers_v GROUP BY currency_code_tc ORDER BY total_fund DESC;

Because AMS_EVENT_HEADERS_VL is the driving object, security applied at the translatable view level is inherited. Listing currency_code_tc together with its FC counterpart and the corresponding fund amounts is the correct approach whenever multi-currency event budgets must be reported or interfaced, as it preserves both the functional ledger view and the original entered currency.