Search Results validate_schedule_pre

Overview

The APPS.AMS_CAMP_SCHEDULE_CUHK package is a customer-hook (CUP – Custom User Hook) container within the Oracle Marketing (AMS) module of Oracle E-Business Suite. It is classified as an "OTHER" API and executes with AUTHID CURRENT_USER, meaning that its PL/SQL statements resolve privileges against the invoking schema rather than the owning APPS schema. The package exists to provide a supported extension point around the standard campaign schedule public API, AMS_Camp_Schedule_PUB. Rather than modifying Oracle-seeded logic, implementers use this CUP to inject site-specific business rules before and after the standard processing performed by the public API for schedule creation, deletion, locking, updating, and validation. Each procedure follows a consistent naming convention: _pre procedures run before the seeded logic, and _post procedures run after it completes. All ten documented procedures are non-returning (PROCEDURE) and communicate status through a x_return_status OUT parameter.

Key Procedures and Functions

Ten documented procedures are exposed by this package, organized as five pre/post pairs:

• CREATE_SCHEDULE_PRE / CREATE_SCHEDULE_POST — Customer pre- and post-processing for the create-campaign-schedule operation. The pre-hook receives the schedule record in an IN OUT NOCOPY state, allowing the hook to modify values before the seeded create logic executes. The post-hook receives the finalized schedule record and the newly assigned schedule identifier, enabling downstream actions such as logging or integration writes.
• DELETE_SCHEDULE_PRE / DELETE_SCHEDULE_POST — Pre- and post-processing for schedule deletion. The pre-hook can adjust the schedule ID and object version prior to removal; the post-hook operates on the confirmed deleted identifiers.
• LOCK_SCHEDULE_PRE / LOCK_SCHEDULE_POST — Pre- and post-processing for the optimistic-locking operation that participates in the standard API's concurrency control.
• UPDATE_SCHEDULE_PRE / UPDATE_SCHEDULE_POST — Pre- and post-processing for schedule modification.
• VALIDATE_SCHEDULE_PRE / VALIDATE_SCHEDULE_POST — Pre- and post-processing for the validation phase, allowing customers to add or supplement validation rules around a schedule.

Together these hooks cover the full lifecycle of a campaign schedule record as managed through the AMS public API.

Tables Accessed

The ETRM metadata does not document direct table references for this package; any SQL is expected to be executed through APPS synonyms and resolved at runtime under the invoking user's privileges due to the AUTHID CURRENT_USER clause. In practice, customer code inserted into these hooks would typically target AMS marketing tables such as the campaign schedule base and translation tables, but no such references are asserted by the documented metadata. Implementation teams should treat table access as custom code and validate it explicitly.

Usage Notes

This package is not invoked directly by end users. It is called internally by AMS_Camp_Schedule_PUB at each documented extension point during schedule create, delete, lock, update, and validate processing. The package is referenced by one other package in the ETRM inventory, confirming its role as an embedded callback rather than a standalone API. Because the procedures are stubs in the seeded application, the intended usage pattern is for developers to place site-specific logic inside the procedure bodies (or to wrap them), then recompile the package. Typical invocation happens through Oracle Marketing scheduling forms, concurrent programs that process schedule data, or custom code that calls the schedule public API. As with any CUP, changes should be preserved through patching and regression tested against the AMS public API in EBS 12.1.1 and 12.2.2.