Search Results payment_status_code

Overview

The AST_EVENT_ENROLL_HISTORY_V view belongs to the Oracle E-Business Suite TeleSales (AST) module and presents enrollment history for event registrations captured through the Oracle Marketing and TeleSales event management flow. It consolidates registration, customer, enrollee, order, pricing, and payment-status information into a single denormalized reporting structure, allowing event enrollment records to be queried without joining the underlying AMS, HZ, OE, and QP tables manually.

In EBS 12.1.1 and 12.2.2 this view is defined in the database but is not implemented as a seeded concurrent program or base table; it is a query-only construct used for reporting, extracts, and integration endpoints. Because the ATTENDANT_* columns are surfaced directly, it is commonly the target of searches keyed on attendant_account_id.

Underlying Base Objects

Based on the documented view text, AST_EVENT_ENROLL_HISTORY_V is defined over these base objects:

• AMS_EVENT_REGISTRATIONS — the driving registration record (aliased REG).
• AMS_EVENT_OFFERS_VL — event offer header details (EVT).
• HZ_PARTIES — three aliases (CST customer, CST1 main contact, CST2 enrollee/attendant).
• HZ_ORG_CONTACTS and HZ_PARTY_RELATIONSHIPS — linkage between party and contact.
• JTF_PARTY_PHONES_V — primary phone number for the contact.
• AMS_LOOKUPS — payment status meaning.
• OE_ORDER_HEADERS and OE_ORDER_LINES — sales order header/line created for the registration.
• QP_LIST_HEADERS_VL — price list name.

Outer joins are applied to phone, lookup, attendant party, contact, and order/price list objects so that enrollments without a matching attendant or order still appear.

Key Columns

• EVENT_REGISTRATION_ID, EVENT_OFFER_ID, EVENT_OFFER_NAME — registration identity and event.
• ORDER_HEADER_ID, ORDER_LINE_ID — the sales order associated with the enrollment.
• CUSTOMER_ID, MAIN_CONTACT_FULL_NAME, MAIN_CONTACT_ID, MAIN_CONTACT_PARTY_ID, MAIN_CONTACT_ACCOUNT_ID — the registrant relationship and primary contact.
• ATTENDANT_PARTY_ID, ATTENDANT_CONTACT_ID, ATTENDANT_ACCOUNT_ID — the individual being enrolled; this is the column family returned for attendant_account_id searches.
• ENROLLEE_FULL_NAME, ENROLLEE_NUMBER, ENROLLEE_PHONE_NUMBER — enrollee display attributes.
• CONFIRMATION_CODE, SYSTEM_STATUS_CODE, REG_SOURCE_TYPE_CODE — registration status and origin.
• UNIT_SELLING_PRICE, TRANSACTIONAL_CURR_CODE, PRICE_LIST_ID, PRICE_LIST_NAME — pricing context.
• PAYMENT_STATUS_CODE, PAYMENT_STATUS, PAYMENT_TYPE_CODE, PAYMENT_AMOUNT — payment tracking.
• OBJECT_VERSION_NUMBER — optimistic locking support.

Common Use Cases and Queries

The view is typically used to audit who enrolled in an event, which order fulfilled the enrollment, and the payment state. A common query filters on the attendant account to find all enrollment history for a given party:

SELECT event_offer_name,
       enrollee_full_name,
       attendant_account_id,
       confirmation_code,
       payment_status,
       order_header_id,
       date_registration_placed
FROM   ast_event_enroll_history_v
WHERE  attendant_account_id = :attendant_account_id;

Other scenarios include reconstructing enrollment-to-order reconciliation, reporting event revenue by price list, and exporting enrollee contact details to external systems. Because the view is read-only and not implemented as a base object, it is safe for SELECT access in custom reports and BI Publisher extracts. Performance on large registration volumes benefits from indexing AMS_EVENT_REGISTRATIONS.