Search Results cancellation_reason_code

Overview

AST_EV_HIS_PER_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AST (TeleSales) product family. The view consolidates event registration history into a single, person-centric result set, joining registration records to event offers, customer party records, contact points, order headers and lines, price lists, and lookup values. Its name reflects its purpose: "EV_HIS" for event history and "PER" for the person or enrollee perspective through which the data is presented.

The view is registered as VALID and is available in ETRM for both 12.1.1 and 12.2.2. Because it is a view rather than a base table, it carries no storage of its own; it exposes a denormalized read of the underlying TeleSales and Order Management data for query, reporting, and integration purposes. It is commonly consumed by Oracle Reports, BI Publisher data templates, custom concurrent programs, and inbound/outbound interface logic that needs a flattened picture of who registered for which event offer and how that registration was billed.

Underlying Base Objects

The view is defined over the following documented base objects:

• AMS_EVENT_REGISTRATIONS (accessed via synonym) — the driving table, supplying event_registration_id, event_offer_id, order references, confirmation code, and system status.
• AMS_EVENT_OFFERS_VL (view) — supplies the event offer name and inventory item.
• HZ_PARTIES (synonym) — joined twice, once as the customer/registrant and once as the attendant contact or enrollee.
• HZ_CONTACT_POINTS (synonym) — joined with outer-join syntax to retrieve the enrollee's primary active phone number.
• AMS_LOOKUPS (view) — outer-joined on lookup_type AMS_EVENT_PAYMENT_STATUS to translate the payment status code.
• OE_ORDER_HEADERS (synonym) — outer-joined on header_id for currency, payment type, and payment amount.
• OE_ORDER_LINES (synonym) — outer-joined on line_id, linking the registration to its sales order line and price list.
• QP_LIST_HEADERS_VL (view) — outer-joined to resolve the price list name.

All order and lookup-related joins use the Oracle outer-join operator (+), reflecting that a registration may exist before, or independently of, a completed order. The AS keyword is not used in the stored text, consistent with legacy EBS view definitions.

Key Columns

• EVENT_REGISTRATION_ID — primary identifier of the registration record; the column most frequently used in the user's search context and in downstream joins.
• EVENT_OFFER_ID / EVENT_OFFER_NAME — the event offer and its display name.
• ORDER_HEADER_ID — the associated sales order header, when one exists.
• DATE_REGISTRATION_PLACED — date the registration was created.
• CUSTOMER_ID / PARTY_TYPE / MAIN_CONTACT_FULL_NAME — registrant party attributes.
• MAIN_CONTACT_ID / ENROLLEE_FULL_NAME / ENROLLEE_PHONE_NUMBER — attendee contact details; the phone number is concatenated with country code, area code, and extension.
• CONFIRMATION_CODE / SYSTEM_STATUS_CODE — registration confirmation and workflow status.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• INVENTORY_ITEM_ID — item associated with the event offer.
• TRANSACTIONAL_CURR_CODE / PAYMENT_TYPE_CODE / PAYMENT_AMOUNT / PAYMENT_STATUS — order and payment attributes.
• PRICE_LIST_NAME / CANCELLATION_REASON_CODE — pricing context and, where applicable, the reason a registration was cancelled.

Common Use Cases and Queries

A typical use is retrieving registration history for a specific event or registrant, filtered by the identifier most often searched:

• Look up a single registration and its enrollee by ID.
• List all registrations for an event offer, with payment status and price list.
• Reconcile registrations against order headers and lines for billing review.

Sample query:

SELECT event_registration_id, event_offer_name, enrollee_full_name, confirmation_code, payment_status, payment_amount FROM apps.ast_ev_his_per_v WHERE event_registration_id = :p_registration_id;

A second pattern lists all registrations for an event and sorts by the date placed:

SELECT event_registration_id, enrollee_full_name, enrollee_phone_number, system_status_code FROM apps.ast_ev_his_per_v WHERE event_offer_id = :p_event_offer_id ORDER BY date_registration_placed DESC;

Because the view already joins parties, orders, and lookups, it removes the need for consumers to replicate the outer-join logic against AMS_EVENT_REGISTRATIONS directly. Query performance depends on indexes on AMS_EVENT_REGISTRATIONS and the HZ and OE base tables; restricting on event_registration_id or event_offer_id generally yields the most efficient execution plans. Although the standard name is AST_EV_HIS_PER_V, many ETRM documentation extracts also reference it as AST_EV_HIS_PER_V, and it should not be confused with similarly named base tables in the AMS schema.