Search Results create_schedule_post




Overview
Explore in AI Chat

Overview

APPS.AMS_CAMP_SCHEDULE_VUHK is a PL/SQL vertical-industry user hook package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. Its name follows the standard EBS "VUHK" convention — a Vertical User Hook — and it is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer. The package exists to provide an extension point around the campaign schedule lifecycle managed by AMS_CAMP_SCHEDULE_PUB, the public API for creating, updating, deleting, locking, and validating campaign schedules. For each corresponding public API operation, the VUHK package exposes a pair of pre- and post-processing hooks, allowing vertical or customer-specific logic to execute before and after the standard processing without modifying Oracle's seeded code. The header comment ($Header: amsischs.pls 115.4 2002/11/16) indicates the file has been shipped since early releases and carried forward into 12.1.1 and 12.2.2. The package is classified in ETRM as API classification OTHER, reflecting its role as a hook layer rather than a standalone application programming interface.

Key Procedures and Functions

The documented interface consists of ten procedures, organized as five pre/post pairs corresponding to the campaign schedule public API operations:

  • CREATE_SCHEDULE_PRE — vertical pre-processing executed before a campaign schedule is created. It receives the schedule record structure in an IN OUT NOCOPY mode, permitting the hook to modify the record prior to standard validation and insertion.
  • CREATE_SCHEDULE_POST — vertical post-processing executed after schedule creation. Accepts the schedule record and the newly assigned schedule identifier, allowing follow-on actions such as defaulting dependent data.
  • DELETE_SCHEDULE_PRE — vertical pre-processing for deletion. The schedule identifier and object version number are passed IN OUT NOCOPY so the hook can adjust or veto the values before the delete proceeds.
  • DELETE_SCHEDULE_POST — vertical post-processing performed after a schedule has been deleted. This is the procedure associated with the user's search term, "delete_schedule_post"; it accepts the schedule identifier and object version number as read-only inputs and returns a status code, enabling cleanup or audit logic after the standard delete.
  • LOCK_SCHEDULE_PRE and LOCK_SCHEDULE_POST — pre- and post-processing hooks around the schedule locking operation.
  • UPDATE_SCHEDULE_PRE and UPDATE_SCHEDULE_POST — pre- and post-processing hooks around schedule updates.
  • VALIDATE_SCHEDULE_PRE and VALIDATE_SCHEDULE_POST — pre- and post-processing hooks around schedule validation.

All procedures return a status value through an OUT NOCOPY parameter, following the standard EBS API error-handling convention. The documented metadata does not expose the full parameter lists beyond those excerpted, and no parameter lists are inferred here.

Tables Accessed

The supplied ETRM metadata does not enumerate specific base tables referenced through APPS synonyms. Because the package functions purely as a hook layer wrapping AMS_CAMP_SCHEDULE_PUB, any persistent table access — principally the AMS campaign schedule tables underlying the public API — is expected to be performed by the public API rather than by the hook procedures themselves. Vertical implementations typically extend the hooks to read or write customer-specific tables. The metadata confirms the package is referenced by one other package, consistent with its hook role.

Usage Notes

AMS_CAMP_SCHEDULE_VUHK is not intended to be called directly by end users. It is invoked implicitly by AMS_CAMP_SCHEDULE_PUB whenever a schedule operation is performed, whether from the Oracle Marketing forms, from concurrent programs, or from custom code that calls the public API. In the seeded Oracle code the hook bodies are stubs with no business logic; customers and vertical partners are expected to populate them with site-specific pre- and post-processing. The object version number parameter in the delete hooks supports optimistic locking, ensuring the schedule row has not been modified by another session before deletion. Because the package runs AUTHID CURRENT_USER, any custom logic added must account for the invoking user's privileges and schema context. The procedures should not be renamed or have their signatures altered, since the calling public API depends on the documented interface.