Search Results create_camp_schedule




Overview
Explore in AI Chat

Overview

AMS_CAMP_SCHEDULE_PUB is the public (PUB) API package for the Oracle Marketing (AMS) campaign schedule entity. It provides the sanctioned PL/SQL interface through which Oracle E-Business Suite applications and custom code create, maintain, lock, validate, and copy campaign schedules — the date-bounded execution records that tie a marketing campaign to its channel, offer, and delivery characteristics. The package body source (amspschb.pls, version 120.4, dated 31-May-2006) delegates all substantive business logic to the private package AMS_Camp_Schedule_PVT, and its principal internal routine, Convert_PubRec_To_PvtRec, maps the public record type schedule_rec_type onto the corresponding private record type before any DML is performed. The header comments record the package's evolution: parameter p_validation_level was added to the create, update, delete, and validate APIs in May 2001; eBlast columns were introduced in July 2001; the copy API was added in September 2001; security group handling was removed from the record structure later that month; and subsequent releases added sales_methodology_id (August 2003) and delivery_mode (May 2006).

Key Procedures and Functions

The package exposes six documented public procedures, each accepting a validation-level parameter that governs the strictness of the checks performed:

  • CREATE_CAMP_SCHEDULE — inserts a new campaign schedule row from the supplied public record, after converting it to the private record structure and applying the requested validation level.
  • UPDATE_CAMP_SCHEDULE — modifies an existing schedule, typically keyed by schedule_id, using the same conversion and validation pattern.
  • DELETE_CAMP_SCHEDULE — removes a schedule record, subject to the standard validation and locking conventions of the AMS API family.
  • LOCK_CAMP_SCHEDULE — acquires a row-level lock on the schedule so that concurrent callers cannot modify it while a transaction is in progress.
  • VALIDATE_CAMP_SCHEDULE — performs validation only, without persisting changes; this is the API reached when a caller invokes the "validate_camp_schedule" behavior, and it is the natural entry point for pre-save checks in forms or custom integrations.
  • COPY_CAMP_SCHEDULE — duplicates an existing schedule, a capability added in September 2001 to support rapid creation of similar campaign scheduling records.

All six routines operate on the package's public schedule_rec_type, which carries standard WHO audit columns (creation_date, created_by, last_update_date, last_updated_by, last_update_login, object_version_number) in addition to the schedule attributes.

Tables Accessed

The ETRM metadata for this package does not enumerate the underlying base tables; the documentation records that the package references tables through APPS synonyms. Based on the AMS data model and the record structure evident in the source, the package operates on the campaign schedule table (AMS_CAMP_SCHEDULES) together with the campaign and channel/offer reference tables needed to validate a schedule. Because INSERT, UPDATE, and DELETE are performed through the private package, row-level locking is applied to the schedule table when LOCK_CAMP_SCHEDULE is called. The package is referenced by eight other packages within the AMS schema, indicating it functions as an upstream dependency in the campaign scheduling call chain.

Usage Notes

AMS_CAMP_SCHEDULE_PUB is invoked from the Oracle Marketing campaign scheduling forms, from concurrent programs that build or refresh campaign schedules, and from custom PL/SQL integrations that must respect the AMS validation and concurrency rules. Callers should populate the public schedule_rec_type, pass an appropriate p_validation_level, and always invoke LOCK_CAMP_SCHEDULE before an UPDATE or DELETE to guarantee row-level integrity. Because the package delegates to AMS_Camp_Schedule_PVT, custom code should never call the private package directly: the public package is the supported interface and remains the stable contract across EBS 12.1.1 and 12.2.2. For validation-only scenarios, VALIDATE_CAMP_SCHEDULE is the correct entry point, as it performs the same checks as the create and update paths without committing any data.