Search Results as_event_enrollments_all




Overview
Explore in AI Chat

Overview

The AS_EVENT_ENROLLMENTS_ALL table is a core transactional data object within the Oracle E-Business Suite (EBS) Sales Foundation module (AS). It serves as the central repository for recording and managing event enrollments. An event enrollment represents the registration or sign-up of a contact from a customer account for a specific marketing or sales event. These events are typically defined as promotions within the AS_PROMOTIONS_ALL table. The table's "ALL" suffix indicates it is a multi-organization enabled table, storing data partitioned by the operating unit (ORG_ID), which is a standard architectural pattern in Oracle EBS to support complex enterprise structures. Its primary role is to track participation, forming a critical link between customers, their contacts, and the marketing activities designed to engage them.

Key Information Stored

The table's structure is designed to capture the essential relationships and attributes of an enrollment. The primary identifier is the EVENT_ENROLLMENT_ID. The fundamental relationships are enforced through foreign key columns: CONTACT_ID links to the specific individual enrolled, EVENT_ID points to the relevant event in AS_PROMOTIONS_ALL, and CUSTOMER_ID references the parent account in RA_CUSTOMERS. The ADDRESS_ID links to the contact's address in RA_ADDRESSES_ALL. A unique key constraint on the combination of CONTACT_ID and EVENT_ID ensures a contact cannot be enrolled multiple times in the same event. Additional important columns typically include STATUS_CODE to track the enrollment lifecycle (e.g., 'REGISTERED', 'ATTENDED', 'CANCELLED'), ENROLLMENT_DATE, and SOURCE_PROMOTION_ID to track which specific promotion instance generated the enrollment. The ORG_ID column is crucial for data isolation in multi-org deployments.

Common Use Cases and Queries

This table is central to reporting and analytics on event marketing effectiveness. Common use cases include generating attendance rosters for events, measuring event registration rates, and analyzing customer engagement across different promotion types. A typical query might join to customer, contact, and promotion tables to produce a detailed enrollment report. For example:

  • Listing all enrollments for a specific event to manage logistics.
  • Identifying the most active customers based on event participation history.
  • Measuring the conversion rate from a campaign by joining enrollment data with opportunity or lead data.

A sample SQL pattern to retrieve basic enrollment details would be:
SELECT aee.event_enrollment_id, rc.customer_name, aee.contact_id, ap.name event_name, aee.status_code, aee.enrollment_date FROM as_event_enrollments_all aee, ra_customers rc, as_promotions_all ap WHERE aee.customer_id = rc.customer_id AND aee.event_id = ap.promotion_id AND aee.org_id = :p_org_id;

Related Objects

AS_EVENT_ENROLLMENTS_ALL is a nexus table with defined relationships to several key EBS entities. Its primary foreign key dependencies, as documented, are:

  • RA_CUSTOMERS: Links the enrollment to the customer account.
  • RA_ADDRESSES_ALL: Links to the enrolled contact's address.
  • AS_PROMOTIONS_ALL (via EVENT_ID): Links to the definition of the event itself.
  • AS_PROMOTIONS_ALL (via SOURCE_PROMOTION_ID): Links to the originating promotion or campaign.

It is also related to the AS_CONTACTS entity through the CONTACT_ID column. This table is likely referenced by various Oracle APIs, seeded reports, and user interfaces within the Marketing and Sales modules for creating, updating, and querying enrollment data. The primary key (AS_EVENT_ENROLLMENTS_PK) and unique key (AS_EVENT_ENROLLMENTS_UK) constraints are critical for maintaining data integrity.