Search Results copy_event_schedule




Overview
Explore in AI Chat

Overview

AMS_EVENTSCHEDULE_COPY_PVT_W is a private PL/SQL wrapper package in the Oracle Marketing (AMS) application schema, owned by APPS and declared with AUTHID CURRENT_USER. Its sole purpose is to expose the copy operation that duplicates an existing event schedule — the recurring or multi-occurrence timing definition attached to a marketing event — into a new event schedule record. The package belongs to the "Copy" family of private APIs used by Oracle Marketing's event management and campaign scheduling functionality, and it is the public-facing entry point through which the underlying private package AMS_EVENTSCHEDULE_COPY_PVT is invoked.

The suffix "_W" denotes a wrapper package. In the AMS architecture, wrapper packages accept the standard Oracle Application Object Library (AOOL) API calling convention and delegate the actual business logic to a non-wrapper private package. The header annotation ($Header: amswescs.pls 115.4 2004/04/08 ...) indicates the file was last revised in the 11.5.x code line and has been carried forward essentially unchanged into E-Business Suite 12.1.1 and 12.2.2, where it remains an internal, undocumented-for-customers API. The user-facing search term "copy_event_schedule" corresponds directly to the package's single documented procedure.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure in this package:

  • COPY_EVENT_SCHEDULE — Performs the duplication of an event schedule. It follows the standard EBS API signature pattern: p_api_version, p_init_msg_list, p_commit, and p_validation_level as input parameters, plus the standard output trio x_return_status, x_msg_count, and x_msg_data. The business-specific inputs are p_source_object_id (the event schedule being copied) and two attribute tables of type JTF_VARCHAR2_TABLE_100 and JTF_VARCHAR2_TABLE_4000, used to carry the source attribute names/values and the target column values for the new record. The procedure returns x_new_object_id, the identifier of the newly created event schedule, and x_custom_setup_id, identifying any associated custom setup record generated during the copy.

The presence of the two JTF_VARCHAR2_TABLE parameters reflects the AMS generic copy framework, in which callers supply a flexibly-sized array of source/target attribute mappings rather than a fixed list of columns, allowing the same copy procedure to serve different schedule types and enabled attribute sets.

Tables Accessed

The ETRM metadata for this package does not enumerate the base tables referenced. Based on the documented parameters and the naming of the underlying private package, the copy operation logically reads the source row (and its child attribute rows) from the AMS event schedule entities — principally the event schedule header table and its associated schedule/attribute detail tables — and inserts corresponding new rows. The x_custom_setup_id output implies a write into a custom-setup table when the source schedule carries user-defined setup data. Because the package is declared AUTHID CURRENT_USER and is accessed through APPS synonyms, all such DML executes against the APPS-owned objects under the caller's privileges. Any customer extension that references this package should not assume a specific table layout, since the metadata does not expose one.

Usage Notes

AMS_EVENTSCHEDULE_COPY_PVT_W is an internal private API. It is not designed for direct invocation by customer code, and Oracle does not certify it as a public interface. In practice it is called by Oracle Marketing forms and by internal concurrent or PL/SQL routines that implement "Copy Event" and "Copy Schedule" user actions. Callers must supply a valid p_api_version, pass FND_API.G_TRUE/G_FALSE for p_init_msg_list and p_commit, and interpret x_return_status against the standard FND_API.G_RET_STS_SUCCESS, G_RET_STS_ERROR, and G_RET_STS_UNEXP_STATUS constants. Because the procedure performs DML, transaction control should be considered carefully: passing G_TRUE for p_commit commits within the API. The metadata records that no other package references this wrapper, confirming its role as a terminal entry point rather than a shared library. Customers extending event schedule copy behavior should prefer documented AMS APIs or form personalization over this private wrapper, and should re-validate any dependency when upgrading between 12.1.1 and 12.2.2, as the wrapper may be replaced by later private-package revisions.