Results for “attendant_contact_id”

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

Overview

The AST_EVENT_HISTORY_V view, owned by the APPS schema, is a reporting and inquiry object within the Oracle E-Business Suite AST (TeleSales) product family. It consolidates event registration history into a single denormalized row per registration, exposing registration, offer, party, contact, order, pricing, and status information in one structure. The view is defined as VALID and is intended for read-only consumption by reports, concurrent programs, forms, and integration interfaces that require a complete historical picture of event registrations without navigating the normalized AMS and HZ schemas directly.

The view is registered against the AMS (Marketing) foundation, since event registrations and offers are stored in the AMS schema. Because it also joins to Oracle Order Management and Advanced Pricing objects, it is commonly used where TeleSales event registrations generate or reference sales orders and price lists. It is a stable interface for extracting registration history rather than a transactional entity, so it should not be updated or inserted into directly.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists the following referenced base objects: AMS_EVENT_OFFERS_VL (VIEW), AMS_EVENT_REGISTRATIONS (SYNONYM), AMS_LOOKUPS (VIEW), HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), HR_SECURITY (PACKAGE), HZ_CONTACT_POINTS (SYNONYM), HZ_PARTIES (SYNONYM), HZ_RELATIONSHIPS (SYNONYM), JTF_RS_RESOURCE_EXTNS (SYNONYM), OE_ORDER_HEADERS (SYNONYM), PER_PEOPLE_F (VIEW), and QP_LIST_HEADERS_TL (SYNONYM).

The central driver table is AMS_EVENT_REGISTRATIONS (aliased AER), which supplies the registration, offer, order, registrant, attendant, confirmation, and status attributes. AMS_EVENT_OFFERS_VL (AEOV) provides the multilingual event offer name and inventory item. HZ_PARTIES is joined multiple times (HP1 through HP4) to resolve registrant party, registrant contact, attendant party, and attendant contact names, with a filter requiring HP1.PARTY_TYPE = 'PERSON'. HZ_CONTACT_POINTS is outer-joined to retrieve attendant contact phone information. AMS_LOOKUPS (AL1, AL2, AL3) supplies lookup meanings for system status, payment status, and cancellation reason. OE_ORDER_HEADERS (OOH) contributes currency, payment type, and payment amount. QP_LIST_HEADERS_TL (QLHT) supplies the price list name. PER_PEOPLE_F (PPF) resolves the event coordinator name and telephone.

Key Columns

• EVENT_REGISTRATION_ID, EVENT_OFFER_ID, EVENT_OFFER_NAME — the registration and its associated offer.
• ORDER_HEADER_ID, DATE_REGISTRATION_PLACED — linkage to the sales order and registration timestamp.
• REGISTRANT_PARTY_ID / REGISTRANT_PARTY, REGISTRANT_CONTACT_ID / REGISTRANT_CONTACT — registrant and contact identities resolved from HZ_PARTIES.
• ATTENDANT_PARTY_ID / ATTENDANT_PARTY, ATTENDANT_CONTACT_ID / ATTENDANT_CONTACT, ATTENDANT_CONTACT_PHONE — attendant and contact details, with phone assembled from country code, area code, number, and extension.
• CONFIRMATION_CODE, SYSTEM_STATUS_CODE / SYSTEM_STATUS — registration confirmation and decoded system status via AMS_LOOKUPS.
• INVENTORY_ITEM_ID, TRANSACTIONAL_CURR_CODE, PAYMENT_TYPE_CODE, PAYMENT_AMOUNT, PRICE_LIST_NAME — order and pricing context.
• CANCELLATION_REASON_CODE / CANCELLATION_REASON — decoded cancellation reason.
• EVENT_COORDINATOR, COORDINATOR_PHONE — coordinator resolved from PER_PEOPLE_F.
• OBJECT_VERSION_NUMBER — optimistic locking version attribute.

Common Use Cases and Queries

The view supports event attendance reporting, order-to-registration reconciliation, cancellation analysis, and integration extracts. The presence of AMS_LOOKUPS indicates status and reason codes are decoded in-line, reducing the need for callers to join lookup tables or query AMS_LOOKUPS directly. A representative query follows:

• SELECT event_offer_name, registrant_party, attendant_party, system_status, payment_status, payment_amount, cancellation_reason FROM apps.ast_event_history_v WHERE TRUNC(date_registration_placed) BETWEEN :start_date AND :end_date ORDER BY event_offer_name, registrant_party;
• Registrations without a confirming order: SELECT event_registration_id, event_offer_name, registrant_party FROM apps.ast_event_history_v WHERE order_header_id IS NULL;
• Cancellation summary: SELECT event_offer_name, cancellation_reason, COUNT(*) FROM apps.ast_event_history_v WHERE cancellation_reason_code IS NOT NULL GROUP BY event_offer_name, cancellation_reason;

Because the view resolves party and person details at query time and relies on HR security packages, performance should be assessed with proper date and offer predicates. All access should be granted through the APPS schema rather than base AMS or HZ tables.