Results for “ams_p_event_reg_roster_v”

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

Overview

AMS_P_EVENT_REG_ROSTER_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. It returns the registration details of participants (registrants) to a marketing event, joining event offer attributes, registrant party information, event location details, and registration status lookups into a single denormalized roster. The view carries a VALID status in both EBS 12.1.1 and 12.2.2 and is documented in the ETRM repository for the 12.2.2 release.

Its role is primarily reporting and integration-oriented: it exposes one row per event registration, enriched with the associated event, venue, registrant, and status context. Because it is a public view in the APPS schema, it can be safely referenced by custom reports, Discoverer workbooks, concurrent programs, and external integrations without requiring joins against the underlying transactional tables directly. The view is read-only by construction and inherits the security and grants applied to the APPS schema objects it references.

Underlying Base Objects

The view is defined over five documented base objects, combined through inner joins:

• AMS_EVENT_OFFERS_VL (VIEW) — the event offer header, providing the event name, location, start/end dates, inventory item, and the offer's own user status.
• AMS_EVENT_REGISTRATIONS (SYNONYM) — the registration transaction, supplying registrant identifiers, confirmation and cancellation codes, waitlist priority, registration group, and order references.
• AMS_USER_STATUSES_VL (VIEW) — the status lookup used to resolve the registration's user status ID into a system status code and status name.
• HZ_LOCATIONS (SYNONYM) — the event venue, providing city, state, province, and country.
• HZ_PARTIES (SYNONYM) — the registrant party, providing the party name.

Join predicates link EVENT_OFFER_ID between the offer and registration, EVENT_LOCATION_ID to LOCATION_ID, REGISTRANT_PARTY_ID to PARTY_ID, and USER_STATUS_ID to the status lookup. Because every join is an equality join without an outer qualifier, only registrations with matching offers, locations, parties, and statuses are returned.

Key Columns

• EVENT_OFFER_ID / EVENT_OFFER_NAME — unique identifier and display name of the marketing event offer.
• EVENT_LOCATION_ID, CITY, STATE, PROVINCE, COUNTRY — the venue and its geographic attributes.
• EVENT_START_DATE, EVENT_START_TIME, EVENT_END_DATE, EVENT_END_TIME — the event schedule. Note that the view text derives these from EVENT_START_DATE_TIME and EVENT_END_DATE_TIME; the date/time split is exposed as discrete columns in the documented column list. Users searching on "event_start_time" will locate the schedule through these columns rather than a column literally named EVENT_START_TIME in all releases.
• REGISTRANT_PARTY_ID / REGISTRANT_PARTY_NAME — the party registered for the event.
• REGISTRANT_ACCOUNT_ID / REGISTRANT_CONTACT_ID / REGISTRANT_CONTACT_NAME — the associated account and contact, where populated.
• EVENT_REGISTRATION_ID — primary key of the registration record.
• CONFIRMATION_CODE / CANCELLATION_CODE — codes used to confirm or cancel a registration.
• WAITLIST_PRIORITY — position on the waitlist when the registration is waitlisted.
• REGISTRATION_STATUS_ID, REG_STATUS_CODE, REG_STATUS_NAME — the resolved registration status.
• REGISTRATION_GROUP_ID, INVENTORY_ITEM_ID, ORDER_HEADER_ID, ORDER_LINE_ID — grouping and order linkage for the registration.

Common Use Cases and Queries

Typical uses include attendance rosters, waitlist review, venue-based capacity reporting, and reconciliation of event registrations to sales orders. A roster report for a specific event:

• SELECT event_offer_name, event_start_date, event_start_time, registrant_party_name, reg_status_name FROM ams_p_event_reg_roster_v WHERE event_offer_id = :p_event_offer_id ORDER BY registrant_party_name;

Waitlisted registrants by priority:

• SELECT event_offer_name, registrant_party_name, waitlist_priority FROM ams_p_event_reg_roster_v WHERE reg_status_code = 'WAITLISTED' ORDER BY event_offer_id, waitlist_priority;

Registrations linked to orders for downstream invoicing or revenue recognition:

• SELECT event_offer_name, event_registration_id, order_header_id, order_line_id FROM ams_p_event_reg_roster_v WHERE order_header_id IS NOT NULL;

Because the view provides no outer joins, reports expecting registrations without a resolved location or status will not see those rows through this view; such cases require querying AMS_EVENT_REGISTRATIONS directly with outer joins to the lookup tables.