Search Results ams_event_reg_status




Overview
Explore in AI Chat

Overview

The APPS.AST_EV_HIS_ORG_V view is a reporting and integration construct within Oracle E-Business Suite that consolidates event registration history for an operating unit (organization) context. It is defined in the APPS schema and exposes registration-level data for events managed by the Oracle Marketing (AMS) module, joining registration records to event offers, customer party information, contact details, order headers, price lists, and lookup values. The view is denormalized and read-only, intended to flatten the relationships required to present a complete picture of who registered for which event, under what payment and system status, and at what price. Because it spans AMS, Oracle Receivables/HZ (Trading Community Architecture) party data, and Oracle Order Management objects, it is typically consumed by operational reports, CRM dashboards, and downstream integrations rather than by transactional forms.

Underlying Base Objects

The view is defined over the following documented base objects:

  • AMS_EVENT_REGISTRATIONS (synonym) — the primary driver table supplying registration, offer, order, payment status, and cancellation columns.
  • AMS_EVENT_OFFERS_VL (view) — supplies the event offer name and inventory item identifier.
  • AMS_LOOKUPS (view) — joined twice to decode the system status code (AMS_EVENT_REG_STATUS) and the payment status code (AMS_EVENT_PAYMENT_STATUS).
  • HZ_PARTIES (synonym) — joined multiple times (aliases CST, CST1, CST2) to resolve the registrant, enrollee/attendant contact, and related party names and party types.
  • HZ_CONTACT_POINTS (synonym) — provides the primary phone contact point for the enrollee via an outer join.
  • OE_ORDER_HEADERS (synonym) — supplies transactional currency, payment type, payment amount, and price list identifier.
  • QP_LIST_HEADERS_TL (synonym) — resolves the price list name.
  • HZ_RELATIONSHIPS (synonym) — referenced in the metadata for related-party resolution as part of the view's family of party joins.

The view text is a UNION ALL of two branches, differing in how the registrant versus enrollee/related-party linkage is derived. Most joins to party, contact point, order, and lookup tables are outer joins, allowing registrations to surface even when optional data such as phone, payment, or price list is absent.

Key Columns

Common Use Cases and Queries

Typical uses include registration status reporting, revenue and payment reconciliation, and customer attendance rosters. A common filter is on the decoded system status, which explains the frequent search term ams_event_reg_status. For example:

SELECT EVENT_REGISTRATION_ID, EVENT_OFFER_NAME, MAIN_CONTACT_FULL_NAME,
       ENROLLEE_FULL_NAME, SYSTEM_STATUS_CODE, PAYMENT_STATUS, PAYMENT_AMOUNT
FROM   APPS.AST_EV_HIS_ORG_V
WHERE  SYSTEM_STATUS_CODE = 'Confirmed'
AND    DATE_REGISTRATION_PLACED >= SYSDATE - 90;

Because the view aggregates party, order, and lookup context, it is well suited to feed BI Publisher reports and interface extracts without requiring callers to reproduce the underlying multi-table joins.