Search Results ams_eventoffer_pub




Overview
Explore in AI Chat

Overview

APPS.AMS_EVENTOFFER_PUB is a public PL/SQL package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. Its role is to expose a stable, supported API surface for managing the association between marketing events and the offers presented during those events — the records commonly known as event offers. In the AMS data model, an event offer links a marketing event to an offer so that the campaign or event can record and act on the promotional content delivered to attendees or targeted audiences. The package is classified as a PUB (public) API, meaning it is intended for invocation by external callers, including other AMS packages, forms, concurrent programs, and customer-developed extensions. Internally, AMS_EVENTOFFER_PUB delegates its business logic to the private package APPS.AMS_EVENTOFFER_PVT, which performs the substantive validation and DML operations. This layering follows the standard Oracle EBS public/private API pattern, isolating transactional logic behind a controlled interface. In the documented ETRM metadata for release 12.2.2, the package is listed with VALID status under the APPS schema and exposes five documented program units. It is referenced by two other packages, AMS_CAMP_SCHEDULE_PVT and AMS_EVENTOFFER_PUB_W, confirming its integration into campaign scheduling and possible web or workflow invocation paths.

Key Procedures and Functions

The documented public interface consists of five procedures:

  • CREATE_EVENTOFFER — Creates a new event offer record, establishing the association between a marketing event and an offer. This is the primary entry point for introducing event-offer data into the AMS schema.
  • UPDATE_EVENTOFFER — Modifies an existing event offer, allowing attributes of the event-to-offer relationship to be maintained after initial creation.
  • DELETE_EVENTOFFER — Removes an event offer record, reversing the association previously created.
  • LOCK_EVENTOFFER — Acquires a lock on an event offer record, typically as a precursor to update or delete operations, ensuring concurrency safety within the transaction.
  • VALIDATE_EVENTOFFER — Performs validation of event offer data, checking business rules and referential integrity before create or update processing proceeds.

All five procedures follow the conventional maintenance lifecycle — validate, lock, create, update, and delete — typical of Oracle AMS public APIs. Parameter lists are not enumerated in the supplied metadata and should be confirmed against the package specification in the target instance.

Tables Accessed

The ETRM excerpt documents table access via APPS synonyms but does not enumerate the specific underlying tables. Based on AMS event offer functionality, the package operates against the event offer base tables owned by the AMS schema, reading and writing the rows that store event-to-offer associations. Read operations support validation and query of existing records; write operations support creation, modification, and deletion. Because the documented metadata does not list explicit table names, implementers should inspect the package body or the AMS data model documentation in the target environment to confirm the exact tables involved. No table names beyond the referenced synonyms should be assumed without verification.

Usage Notes

AMS_EVENTOFFER_PUB is invoked when event offer data must be created or maintained programmatically rather than through the standard Marketing forms. The dependency listing shows it is referenced by AMS_CAMP_SCHEDULE_PVT, indicating that campaign scheduling logic calls into the event offer API during scheduling operations. It is also referenced by AMS_EVENTOFFER_PUB_W, a wrapper package commonly used to adapt the public API for web or workflow invocation. Custom code should call this package rather than manipulating AMS event offer tables directly, preserving validation and concurrency behavior. Callers are expected to initialize the FND_API global environment and honor the standard savepoint and error-handling conventions. As with all PUB APIs in EBS 12.1.1 and 12.2.2, the specification of AMS_EVENTOFFER_PUB should be treated as the supported contract, while AMS_EVENTOFFER_PVT remains private and subject to change. Because event offers are tied to marketing events and campaigns, usage is typically transactional and scoped to a single logical business operation.