Results for “as_event_enrollments_v”

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

Overview

AS_EVENT_ENROLLMENTS_V is a reporting and inquiry view in the Oracle EBS Sales Foundation (AS) module. It presents a denormalized, business-ready picture of event enrollment activity, combining enrollment records from AS_EVENT_ENROLLMENTS with the customer, contact, and telephone details of the enrolled party, and decoding the enrollment status code into a user-facing meaning. The view is primarily used by Oracle Sales Online / iStore event and seminar functionality as well as custom reporting on seminar registrations, attendance, and payment behavior.

Because the view flattens several parent-child joins and applies the status lookup translation inline, consumers do not need to reconstruct the RA_CONTACTS and RA_CUSTOMERS joins themselves. This makes it a convenient source for concurrent programs, Oracle Reports, OBIEE/BIP datasets, and ad-hoc SQL where the enrollment record must be reported alongside the enrolling contact.

Underlying Base Objects

The view is defined over five base objects, joined as follows:

• AS_EVENT_ENROLLMENTS (alias EVNTENR) — the core enrollment transaction table, providing the event enrollment ID, event ID, customer ID, contact ID, status code, payment amount, currency, and descriptive flexfield attributes.
• AS_LOOKUPS (alias ASLKP1) — joined by EVNTENR.STATUS_CODE = ASLKP1.LOOKUP_CODE with LOOKUP_TYPE restricted to 'EVENT_ENROLLMENT_STATUS', supplying the translated status MEANING.
• RA_CUSTOMERS (alias CUST) — joined by EVNTENR.CUSTOMER_ID = CUST.CUSTOMER_ID, supplying CUSTOMER_NAME.
• RA_CONTACTS (alias CONT) — joined by EVNTENR.CONTACT_ID = CONT.CONTACT_ID, supplying LAST_NAME, FIRST_NAME, and JOB_TITLE. This is the source for the commonly searched attribute contact_job_title.
• RA_PHONES (alias PHON) — outer-joined by CONTACT_ID with PRIMARY_FLAG(+) = 'Y' and STATUS(+) = 'A', returning the active primary phone number, area code, and extension when one exists.

Key Columns

Identity and audit columns include ROW_ID, EVENT_ENROLLMENT_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and the standard who-columns. Business columns of interest:

• EVENT_ID / CUSTOMER_ID / CONTACT_ID / ADDRESS_ID / SOURCE_PROMOTION_ID — foreign keys identifying the event, customer, contact, address, and originating promotion.
• STATUS_CODE — the raw lookup code; MEANING — the decoded status (e.g., enrolled, confirmed, cancelled).
• NUM_ENROLLED, NUM_ATTENDED, CONFIRMED_FLAG, STATUS_CHANGE_FLAG — quantities and lifecycle flags for enrollment and attendance tracking.
• PAYMENT_AMOUNT and CURRENCY_CODE — the fee associated with the enrollment.
• JOB_TITLE — the contact's job title, sourced from RA_CONTACTS and returned as contact_job_title in this view.
• PHONE_ID, PHONE_NUMBER, AREA_CODE, EXTENSION — the contact's primary active telephone details, null if none exist.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segment columns.

Common Use Cases and Queries

Typical scenarios include seminar roster reports, attendance reconciliation, revenue-by-event analysis, and marketing follow-up by contact job title. A typical query selecting enrollment details with the contact job title is:

SELECT EVENT_ENROLLMENT_ID, CUSTOMER_NAME, FIRST_NAME, LAST_NAME, JOB_TITLE, MEANING, PAYMENT_AMOUNT, CURRENCY_CODE, NUM_ATTENDED, PHONE_NUMBER
FROM AS_EVENT_ENROLLMENTS_V
WHERE EVENT_ID = :p_event_id
ORDER BY LAST_NAME, FIRST_NAME;

To aggregate revenue and attendance per status, the MEANING column can be grouped directly without re-joining AS_LOOKUPS, and the JOB_TITLE column supports segmentation queries such as filtering to enrollments where the contact's job title matches a target audience. Because the view restricts phone joins to PRIMARY_FLAG = 'Y' and STATUS = 'A' via outer join, enrollments without a valid primary phone still appear, with phone columns null.