Search Results ams_event_registrations




Overview
Explore in AI Chat

Overview

The AMS_EVENT_REGISTRATIONS table is a core transactional data store within the Oracle E-Business Suite Marketing (AMS) module for versions 12.1.1 and 12.2.2. It serves as the central repository for managing participant enrollment in marketing events. The table's primary function is to record the complete lifecycle of an event registration, tracking who is registered, their attendance status, and associated details. This data is critical for event management, campaign analysis, and customer engagement tracking, linking marketing activities directly to customer and account entities within the broader Oracle EBS ecosystem.

Key Information Stored

The table stores a comprehensive set of attributes for each registration. The primary key, EVENT_REGISTRATION_ID, uniquely identifies each enrollment record. Key data points include identifiers for the marketing event itself (EVENT_OFFER_ID), and detailed party information for both the registrant and the actual attendant through columns like REGISTRANT_PARTY_ID, ATTENDANT_PARTY_ID, and their corresponding account (REGISTRANT_ACCOUNT_ID, ATTENDANT_ACCOUNT_ID) and contact IDs. The registration's workflow state is managed via USER_STATUS_ID, linking to the AMS_USER_STATUSES_B table. Additional critical columns capture the source of the registration (INBOUND_CHANNEL_ID, INBOUND_MEDIA_ID), the responsible owner (OWNER_USER_ID), the associated marketing list (TARGET_LIST_ID), and language preference (ATTENDANT_LANGUAGE).

Common Use Cases and Queries

This table is central to operational reporting and process automation for event marketing. Common use cases include generating attendee rosters, tracking registration conversion rates, and analyzing event performance by source channel. A typical query might join with HZ_PARTIES and AMS_EVENT_OFFERS_ALL_B to produce a contact list for a specific event. For example:

SELECT aer.EVENT_REGISTRATION_ID, hp.party_name, aeob.name EVENT_NAME, ausb.user_status_name
FROM ams_event_registrations aer,
hz_parties hp,
ams_event_offers_all_b aeob,
ams_user_statuses_b ausb
WHERE aer.registrant_party_id = hp.party_id
AND aer.event_offer_id = aeob.event_offer_id
AND aer.user_status_id = ausb.user_status_id
AND aeob.event_offer_id = :p_event_id;

Another common scenario involves updating the USER_STATUS_ID to reflect a change in attendance status (e.g., from 'Registered' to 'Attended') via standard AMS APIs or direct SQL within customizations.

Related Objects

AMS_EVENT_REGISTRATIONS is highly interconnected within the EBS data model. Its primary foreign key relationship is with AMS_EVENT_OFFERS_ALL_B, which defines the event. It extensively references the Trading Community Architecture (TCA) schema for party (HZ_PARTIES), account (HZ_CUST_ACCOUNTS), and contact (HZ_ORG_CONTACTS) data. Status management is governed by AMS_USER_STATUSES_B. The table also links to resource management (JTF_RS_RESOURCE_EXTNS for the owner), marketing channels and media (AMS_CHANNELS_B, AMS_MEDIA_B), and list management (AMS_LIST_HEADERS_ALL). These relationships ensure data integrity and enable comprehensive reporting across marketing and sales functions.