Results for “ams_registrants_pub”

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

Overview

APPS.AMS_REGISTRANTS_PUB is a public PL/SQL package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. It exposes an API surface for creating, updating, and managing event registrants and their associated registration records. In the Oracle EBS 12.1.1 and 12.2.2 releases, the AMS schema family underpins the Marketing and Events functionality, where registrants represent parties who have signed up for an event such as a seminar, trade show, or campaign activity. This package encapsulates the business rules that govern how a registrant's party information, contact details, attendance status, and event linkage are persisted, insulating callers from the underlying AMS_EVENT_REGISTRATIONS and TCA (Trading Community Architecture) table structures.

The package is declared with AUTHID CURRENT_USER and carries the standard PL/SQL API conventions used throughout Oracle EBS: a record type, FND_API-style G_MISS defaults for "Who" columns, and a public procedure for registration. It is classified as a PUB (public) API, meaning it is intended and supported for use by external callers such as forms, concurrent programs, and custom extensions. It is referenced by two other packaged objects, indicating that it also functions as a shared service component within the Marketing event-registration flow.

Key Procedures and Functions

The ETRM metadata documents a single public procedure:

• REGISTER — The principal entry point for registering a party to an event. Based on the associated record type RegistrationDet, this procedure accepts a structured set of registration and registrant attributes, including event source code, registration source type, attendance, waitlist, and cancellation flags, confirmation and cancellation reason codes, and an extensive set of party and contact details (name, address, title, gender, communication preferences, and organization characteristics). The procedure is responsible for validating and applying these values against the registration and party records. It is the canonical mechanism by which AMS persists a new or updated registration.

The RegistrationDet record type itself is a significant part of the package's interface, since it defines the complete input contract for a registration transaction and uses FND_API G_MISS sentinels to distinguish "no change" from explicit null values.

Tables Accessed

The package operates against the following documented tables through APPS synonyms:

• AMS_EVENT_REGISTRATIONS — The primary transaction table for event registration. REGISTER inserts or updates rows here, storing event linkage, registration source, attendance, waitlist, cancellation, and confirmation data.
• HZ_PARTIES — The TCA master table of parties (persons and organizations). The procedure reads and writes party-level attributes such as party name, party type, and identifying flags for the registrant.
• HZ_RELATIONSHIPS — The TCA relationship table used to associate the registrant party with related parties, such as contacts, organizations, or other entities connected to the registration.

Usage Notes

AMS_REGISTRANTS_PUB is typically invoked from Oracle Marketing event-registration forms, from concurrent programs that load registrations in bulk, and from custom PL/SQL wrappers. Because it is a public API, direct calls should supply the full RegistrationDet record and initialize unused "Who" columns to FND_API.G_MISS_DATE or FND_API.G_MISS_NUM to preserve existing values. Callers should also perform standard EBS initialization (MO_GLOBAL or FND_GLOBAL for organization and user context) before invocation.

As an API in the AMS schema, it should not be called with direct SQL against its base tables; the package encapsulates necessary validation and TCA integration. In 12.1.1 and 12.2.2 the object is preserved for backward compatibility, and any customization should reference it rather than reimplementing registration logic.