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
- EVENT_ENROLLMENT_ID — Primary key uniquely identifying each enrollment record.
- EVENT_ID — Reference to the event for which the enrollment was created.
- CUSTOMER_ID, ADDRESS_ID, CONTACT_ID — Identifiers for the enrolled party, its location, and the specific contact.
- STATUS_CODE — Current enrollment status (for example, enrolled, cancelled, or attended).
- NUM_ENROLLED, NUM_ATTENDED — Counts of enrolled and attended participants.
- CONFIRMED_FLAG — Indicator of whether the enrollment has been confirmed; the term matches the user's search.
- STATUS_CHANGE_FLAG — Indicator that the enrollment status has changed.
- PAYMENT_AMOUNT, CURRENCY_CODE — Payment value and its currency for the enrollment.
- SOURCE_PROMOTION_ID — Promotion that generated the enrollment, if any.
- ORG_ID — Operating unit that owns the record and governs multi-org access.
- Audit and concurrent columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield storage for extensible enrollment attributes.
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.
-
View: AS_EVENT_ENROLLMENTS 12.1.1
Event enrollments (multi-org)
Not implemented in this database·Explore AS module →
-
View: AS_EVENT_ENROLLMENTS 12.2.2
Event enrollments (multi-org)
Not implemented in this database·Explore AS module →
-
Enrolled Attendees Count View
Not implemented in this database·Explore ICX module →
-
Enrolled Attendees Count View
Not implemented in this database·Explore ICX module →
-
View: AS_EVENT_ENROLLMENTS_V 12.2.2
Event enrollments view
Not implemented in this database·Explore AS module →
-
View: AS_EVENT_ENROLLMENTS_V 12.1.1
Event enrollments view
Not implemented in this database·Explore AS module →
-
Enrolled Attendees View
Not implemented in this database·Explore ICX module →
-
View: AS_EVENT_MERGE_V 12.1.1
Event merge view
Not implemented in this database·Explore AS module →
-
View: AS_EVENT_MERGE_V 12.2.2
Event merge view
Not implemented in this database·Explore AS module →
-
Enrolled Attendees View
Not implemented in this database·Explore ICX module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2