Search Results get_agenda_name

Overview

AMS_EVENTSCHEDULE_COPY_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) Applications schema (APPS), belonging to the Oracle Marketing (AMS) product family. The package is classified as a PVT (private) API, meaning it is intended for internal consumption by other Oracle EBS packages and is not exposed as a public, supported integration interface. Its primary business function is to support the duplication of event schedules and their related marketing collateral within the Oracle Marketing module.

The package declares its authorization as AUTHID CURRENT_USER, so all database object references and privilege checks execute under the privileges of the calling user rather than the package owner. The header records a version of 115.16, last modified in May 2003, indicating the code lineage spans multiple EBS releases, including 12.1.1 and 12.2.2, where it remains part of the marketing event schedule copy infrastructure.

At the center of the package is the concept of a "copy" operation for an event schedule. Marketing users frequently need to clone an existing event schedule, including its agendas, categories, products, deliverables, offers, resources, and partner associations, rather than rebuild them from scratch. This package encapsulates that logic by copying attribute and column sets from a source object to a new object.

Key Procedures and Functions

The package exposes four documented program units:

• COPY_EVENT_SCHEDULE — The principal public driver, calls FND_API conventions (API version, initialization of message list, commit flag, validation level, and the standard x_return_status / x_msg_count / x_msg_data output triplet). It accepts a source object identifier together with attribute and column mapping tables defined in AMS_CpyUtility_PVT, and returns the newly created object identifier and a custom setup identifier. This is the entry point for cloning an entire event schedule.
• COPY_EVENT_SCHEDULE_AGENDA — Copies agenda data associated with a source activity type and activity identifier to a new activity type and activity identifier. It returns an error number, error code, and error message, allowing the caller to handle failures individually.
• COPY_ACT_DELIVERY_METHOD — Copies delivery method assignments for an activity from a source activity to a new activity. Like the agenda copy, it reports status through the error number, code, and message output parameters.
• GET_AGENDA_NAME — A simple lookup function that accepts an agenda identifier and returns the corresponding agenda name as a VARCHAR2. This is the specific routine referenced by the search term "get_agenda_name." It is used internally to resolve agenda identifiers into human-readable names during copy operations and related processing.

Tables Accessed

The package reads and writes several base tables through APPS synonyms. AMS_AGENDAS_B and AMS_AGENDAS_TL hold the base and translated agenda definitions that GET_AGENDA_NAME resolves. AMS_ACT_CATEGORIES, AMS_CATEGORIES_TL, AMS_ACT_DELIVERY_METHODS, AMS_DELIVERABLES_ALL_B, and AMS_DELIVERABLES_ALL_TL support the copy of category, delivery method, and deliverable content. AMS_EVENT_OFFERS_ALL_B and AMS_OBJECT_ASSOCIATIONS capture event offers and the generic relationships between source and newly created objects. PLITBLM is an Oracle Applications utility table used to hold message information produced through the standard message stack.

Usage Notes

Because this package is classified as PVT, it should not be called directly from custom code as a supported interface. It is typically invoked by the Oracle Marketing forms and by other internal AMS packages during event schedule duplication, and it is referenced by three other packages within the application. The attribute constants defined at the top of the package specification (DETL, PROD, CATG, ATCH, MESG, RESC, AGEN, PTNR, CPNT) indicate the discrete copyable components, so callers control which portions of an event schedule are duplicated. Customizations that require agenda name resolution should prefer a supported public API where available, and any reliance on GET_AGENDA_NAME or the copy procedures should be revalidated during upgrades between 12.1.1 and 12.2.2, since private APIs are subject to change without notice.