Search Results create_next_schedule

Overview

The APPS.AMS_SCHEDULER_PVT package body is a private API within the Oracle E-Business Suite Marketing (AMS) module. It encapsulates the core scheduling logic used by Oracle Marketing to generate, replicate, and maintain campaign schedules, activity schedules, and related marketing execution records. The package operates on the AMS_SCHEDULER_S base table and its associated campaign schedule entities, and it coordinates the propagation of schedule data into dependent list, media channel, and association structures. Because it is a PVT-classified package, it is intended to be invoked by other AMS packages and concurrent programs rather than directly by end users or external integrations. In Oracle EBS 12.1.1 and 12.2.2, the package is VALID in the APPS schema and forms part of the scheduling engine supporting campaign execution and repeated activity generation.

Key Procedures and Functions

The documented package exposes four procedures/functions: WRITE_LOG, SCHEDULE_REPEAT, CREATE_NEXT_SCHEDULE, and CREATE_SCHEDULER. No parameter signatures are published in the ETRM metadata, so their descriptions below are functional only.

• WRITE_LOG — Writes diagnostic or audit entries to the AMS logging infrastructure, typically using FND_LOG and FND_MSG_PUB, to record the execution path and errors encountered during schedule processing.
• SCHEDULE_REPEAT — Handles recurring schedule definitions, applying repeat rules held in AMS_SCHEDULERULES_PVT and AMS_CAMP_SCHEDULE_PVT so that campaigns can spawn successive scheduled occurrences.
• CREATE_NEXT_SCHEDULE — Generates the subsequent schedule instance in a recurrence chain, reading the current schedule records and producing the next dated entry in AMS_SCHEDULER_S and associated schedule tables.
• CREATE_SCHEDULER — Creates the primary scheduler record, coordinating with AMS_SCHEDULER_B_PKG and related private packages to persist the schedule header, its detail rows, and downstream list-media associations.

Tables Accessed

The package references a defined set of tables through APPS synonyms. AMS_SCHEDULER_S is the principal scheduling table holding schedule definitions and instances. AMS_CAMPAIGN_SCHEDULES_B and AMS_CAMPAIGN_SCHEDULES_VL store campaign-level schedule headers and their translated views. AMS_ACT_LISTS and AMS_LIST_ENTRIES link schedules to activity/contact lists and their members, while AMS_MEDIA_CHANNELS supplies media channel definitions used when scheduling outbound campaign touches. AMS_USER_STATUSES_B provides user-defined status codes for schedule lifecycle management. IBC_ASSOCIATIONS supplies crosstab/content association data relevant to scheduled deliveries, and DUAL supports single-row procedural logic. These reads and writes allow the package to persist schedules and propagate them into the marketing execution model.

Usage Notes

AMS_SCHEDULER_PVT is a private package and is normally invoked by sibling AMS packages such as AMS_SCHEDULER_B_PKG, AMS_CAMP_SCHEDULE_PVT, AMS_SCHEDULERULES_PVT, and AMS_COPYELEMENTS_PVT, and it is referenced by three other database objects. It is typically triggered from the Oracle Marketing forms interface when a user creates or repeats a campaign schedule, and from concurrent programs that process recurring schedules and generate the next occurrences. It depends on FND_API, FND_GLOBAL, FND_LOG, FND_MSG_PUB, and FND_PROFILE for API error handling, logging, environment context, and profile-option retrieval. Because the package is classified PVT, custom code should not call it directly; supported integration should use the corresponding public AMS APIs, with AMS_SCHEDULER_PVT reserved for internal marketing schedule processing.