Results for “ams_event_headers_agenda_v”

22 results




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

Overview

AMS_EVENT_HEADERS_AGENDA_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema within the AMS (Marketing) product family. It exposes general information about marketing event headers that pertain specifically to event agendas, returning one row per sub-level marketing event. The view is a filtered, denormalized projection over the event header data model and is intended primarily for reporting, inquiry, and integration scenarios where the agenda-level attributes of child events must be presented alongside their parent event context.

The view restricts its result set to records where EVENT_LEVEL equals 'SUB', meaning it is scoped to subordinate events tied to a parent event through PARENT_EVENT_HEADER_ID. This design makes it a convenient source for agenda dashboards, event workflow reports, and extracts that need parent/child event relationships in a single query. Because it resolved to a VALID status in both EBS 12.1.1 and 12.2.2, the object remains a stable, supported reference across these releases.

Underlying Base Objects

The view is defined over three documented base objects:

The join between EVH and PEVH is an outer join (PEVH.EVENT_HEADER_ID(+)), so sub-events without a matching parent still appear, with parent columns null. The join to AMS_USER_STATUSES_VL is an inner join, and the join to FND_LANGUAGES_VL is an outer join.

Key Columns

Common Use Cases and Queries

Typical usage includes agenda reporting, parent/child event roll-ups, registration configuration review, and integration extracts. A representative query locating sub-events that charge for registration is:

SELECT event_header_name, parent_name, reg_charge_flag, reg_required_flag, agenda_start_time, agenda_end_time
FROM apps.ams_event_headers_agenda_v
WHERE reg_charge_flag = 'Y'
AND active_flag = 'Y';

The view may also be joined to registration and attendee tables via EVENT_HEADER_ID for capacity and attendance analysis. Because it is filtered to EVENT_LEVEL = 'SUB', callers should not expect top-level events to appear; those must be sourced from AMS_EVENT_HEADERS_VL directly.