Results for “activate_schedule”

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

Overview

AMS_ACTIVATE_EVENTSCHED_PVT is a private PL/SQL package in the Oracle E-Business Suite Advanced Marketing (AMS) application, owned by the APPS schema and classified as a PVT (private) API. Its principal business function is the activation of event and campaign schedules within Oracle Marketing. Schedules define the timing rules by which marketing events, campaigns, and associated offers are executed; activation is the step that transitions a schedule from a staged or draft state into an active state where it governs downstream execution. The package is designed to be driven by a concurrent program rather than invoked directly by end users, and it delegates the substantive activation work to the underlying activation schedules API. Because the package is declared with AUTHID CURRENT_USER, it executes with the privileges of the calling user and relies on the APPS synonym layer for access to the marketing base tables. The header identifies the original source as amsvevcs.pls, version 115.3, last shipped in March 2004, and the earliest documented history entry credits creation to gmadana in January 2002. Although the package ships in EBS 12.1.1 and 12.2.2, its code lineage is unchanged from the 11i era.

Key Procedures and Functions

The package exposes two documented overloads of a single procedure, ACTIVATE_SCHEDULE.

• ACTIVATE_SCHEDULE (concurrent program wrapper): This overload accepts the standard concurrent program OUT parameters errbuf and retcode. It exists specifically so that schedule activation can be launched from an Oracle Applications concurrent program, providing the conventional error buffer and completion code expected by the concurrent manager. Its documented purpose is to call the internal activation API on behalf of the concurrent request.
• ACTIVATE_SCHEDULE (API-style overload): This overload follows the standard Oracle EBS PL/SQL API conventions, accepting p_api_version, p_init_msg_list, and p_commit as IN parameters and returning x_return_status, x_msg_count, and x_msg_data as OUT parameters. Its documented purpose is to activate available schedules. Callers receive a standardized return status and a message stack suitable for error handling. It is declared to be called by the concurrent program wrapper described above.

No additional public functions or procedures are documented beyond these two overloads. Implementation details of the actual activation logic reside in the underlying activation schedules API that this private package invokes.

Tables Accessed

The package and its delegated activation logic reference four marketing base tables through APPS synonyms:

• AMS_CAMPAIGNS_ALL_B: The campaign base table; activation may update campaign-level status derived from schedule activation.
• AMS_EVENT_HEADERS_ALL_B: The event header base table; events governed by the activated schedule have their scheduling attributes and status confirmed here.
• AMS_EVENT_OFFERS_ALL_B: The event-offer association base table, linking offers to events whose schedules are being activated.
• AMS_USER_STATUSES_B: The user-defined status base table, providing the valid status values to which records are transitioned during activation.

These tables constitute the core marketing object model for events, campaigns, and offers, which is consistent with a package whose sole responsibility is schedule state transition.

Usage Notes

AMS_ACTIVATE_EVENTSCHED_PVT is a private package and is not intended as a public integration point. In standard operation it is invoked by an Oracle Marketing concurrent program that activates event schedules; the errbuf/retcode overload exists precisely for that concurrent manager contract. The API-style overload is available to the concurrent program wrapper and, in principle, to custom code that must activate schedules programmatically, though the PVT classification signals that the interface is unsupported for external callers and may change without notice. The metadata records zero other packages referencing this package directly, indicating it sits at the outer edge of the marketing activation call stack, calling inward to the activation schedules API rather than being called by other PL/SQL units. When troubleshooting schedule activation failures, the output of this package should be traced through its underlying activation API rather than through this wrapper alone. The header note confirming creation in 2002 and the absence of any later revision beyond version 115.3 indicate stable, legacy behavior across EBS 12.1.1 and 12.2.2.