Search Results ams_event_registrations_v




Overview
Explore in AI Chat

Overview

The AMS_EVENT_REGISTRATIONS_V view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and delivered as part of the AMS (Marketing) product family in releases 12.1.1 and 12.2.2. It presents the registration details of participants to a marketing event, consolidating registration header data with the registrant's party and contact information into a single reporting surface. The view is defined as a UNION ALL query, which reflects the fact that registration records may originate from distinct sources—for example, a primary registration flow and a secondary or relationship-driven flow—and both must be surfaced uniformly to consumers.

Because AMS is tightly integrated with the Oracle Marketing Online (OMO) and Oracle Trade Management (OTM) sub-modules, this view serves as a reporting and integration access point for event registration analytics, customer attendance tracking, and downstream campaign attribution. Developers and analysts query it to avoid reconstructing joins across the underlying registration, lookup, status, and party tables.

Underlying Base Objects

The documented base objects referenced by the view are:

Joins in the visible branch connect REG.USER_STATUS_ID to AUS.USER_STATUS_ID, REG.REGISTRANT_PARTY_ID to HZ.PARTY_ID, and an outer join to AMS_LOOKUPS on the payment status lookup type. The condition REG.REGISTRANT_PARTY_ID = REG.REGISTRANT_CONTACT_ID restricts rows to registrations where the party and contact coincide in the first union branch.

Key Columns

Common Use Cases and Queries

Typical use cases include registration-volume reporting by event offer, channel attribution, attendance tracking, and payment/cancellation analysis.

SELECT EVENT_REGISTRATION_ID,
       EVENT_OFFER_ID,
       CUSTOMER_NAME,
       USER_STATUS_ID,
       INBOUND_CHANNEL_ID,
       INBOUND_MEDIA_ID,
       DATE_REGISTRATION_PLACED
  FROM APPS.AMS_EVENT_REGISTRATIONS_V
 WHERE ACTIVE_FLAG = 'Y'
   AND DATE_REGISTRATION_PLACED >= :p_from_date;

Channel attribution for inbound marketing effectiveness:

SELECT INBOUND_CHANNEL_ID, COUNT(*) reg_count
  FROM APPS.AMS_EVENT_REGISTRATIONS_V
 WHERE EVENT_OFFER_ID = :p_offer_id
 GROUP BY INBOUND_CHANNEL_ID;

Attendance versus no-show analysis:

SELECT ATTENDED_FLAG, ATTENDANCE_RESULT_CODE, COUNT(*)
  FROM APPS.AMS_EVENT_REGISTRATIONS_V
 GROUP BY ATTENDED_FLAG, ATTENDANCE_RESULT_CODE;

Because the view performs live joins (including an outer join to lookups), queries should filter on indexed base columns such as EVENT_OFFER_ID and EVENT_REGISTRATION_ID to avoid full scans on AMS_EVENT_REGISTRATIONS.