Results for “as_event_enrollments”

12 results




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

Overview

AS_EVENT_ENROLLMENTS is a multi-org reporting view in the Oracle E-Business Suite Sales Foundation (AS) module. It presents enrollment records that associate customers, addresses, and contacts with marketing or sales events, capturing the lifecycle of a participant from registration through attendance. The view is a secured, organization-filtered projection of the underlying AS_EVENT_ENROLLMENTS_ALL table, exposing enrollment identifiers, status, payment information, attendance counts, and descriptive flexfield attributes.

The view is intended primarily for queries, reports, and integrations that require operational enrollment data scoped to the current operating unit. Because it enforces multi-org security through the CLIENT_INFO session context, records returned are restricted to the organization of the active session. Notably, the ETRM metadata records this object as not implemented in the reference database, meaning it is documented as part of the AS schema but may not be deployed in every environment. In Oracle EBS 12.1.1 and 12.2.2, such documentation-only entries typically reflect seeded or optional components rather than universally installed ones.

Underlying Base Objects

The view is defined over AS_EVENT_ENROLLMENTS_ALL, the multi-org base table that stores enrollment records across all operating units. The view text applies a WHERE clause comparing the ORG_ID column to the operating unit derived from the USERENV('CLIENT_INFO') session value, a standard Oracle multi-org security pattern. The DECODE and SUBSTRB expressions extract the first ten characters of CLIENT_INFO and treat a leading space as NULL, defaulting to -99 when no organization context is present.

The documented metadata does not list additional referenced base objects beyond AS_EVENT_ENROLLMENTS_ALL. Foreign key relationships to customer, address, contact, event, promotion, and currency entities are implied by the exposed identifier columns but are not documented as separate referenced objects. The organization identifier ORG_ID is the principal partitioning key governing row visibility.

Key Columns

Common Use Cases and Queries

Typical uses include reporting confirmed enrollments, reconciling payments, tracking attendance against enrollment counts, and feeding downstream marketing analytics. The CONFIRMED_FLAG column directly supports filtering for confirmed versus unconfirmed records, which is the scenario implied by the user's search term.

Example query returning confirmed enrollments for the current operating unit:

  • SELECT ee.EVENT_ENROLLMENT_ID, ee.EVENT_ID, ee.CUSTOMER_ID, ee.STATUS_CODE, ee.CONFIRMED_FLAG, ee.NUM_ENROLLED, ee.NUM_ATTENDED, ee.PAYMENT_AMOUNT, ee.CURRENCY_CODE FROM AS_EVENT_ENROLLMENTS ee WHERE ee.CONFIRMED_FLAG = 'Y';
  • SELECT ee.EVENT_ID, COUNT(*) total_enrollments, SUM(ee.PAYMENT_AMOUNT) total_payments FROM AS_EVENT_ENROLLMENTS ee WHERE ee.CONFIRMED_FLAG = 'Y' GROUP BY ee.EVENT_ID;

Queries should be executed within an initialized multi-org session, since the view's organization predicate depends on a valid CLIENT_INFO value; otherwise an ORG_ID of -99 may return no rows. Where the view is not deployed, equivalent results can be obtained directly from AS_EVENT_ENROLLMENTS_ALL with an explicit ORG_ID predicate.