Search Results update_deliverable_pre

Overview

AMS_DELIVERABLE_CUHK is the Customer User Hook (CUHK) package that corresponds to the Oracle Marketing (AMS) deliverable business object. It belongs to the Oracle Advanced Marketing / Marketing Online product family and resides in the APPS schema, declared with AUTHID CURRENT_USER so that it executes with the privileges of the calling session rather than the definer. The package header carries the version banner $Header: amscdels.pls 115.1 2002/11/14 00:20:48 musman noship $, confirming it was introduced in the earliest AMS release and has remained stable through Oracle E-Business Suite 12.1.1 and 12.2.2.

The package does not itself contain deliverable business logic. Instead it defines a set of empty, extensible hook points that Oracle Development exposes so that implementers can inject customer-specific behavior around the public deliverable API, AMS_Deliverable_PUB, without modifying Oracle-owned code. Its purpose, as stated in the ETRM header comments, is "Customer user hook package for AMS_Deliverable_PUB." Every routine in the package is a stub that Oracle calls at a defined moment; the customer overrides the body to perform extra validation, defaulting, logging, or integration.

Key Procedures and Functions

The package exposes ten documented procedures, organized as pre- and post-hooks around five deliverable operations:

• CREATE_DELIVERABLE_PRE / CREATE_DELIVERABLE_POST — Pre-processing and post-processing during creation of a deliverable. The post-hook receives the new deliverable identifier, allowing customer code to act on the freshly created record.
• DELETE_DELIVERABLE_PRE / DELETE_DELIVERABLE_POST — Pre-processing and post-processing around deletion of a deliverable. These are the routines a user searching for "delete_deliverable" is looking for: DELETE_DELIVERABLE_PRE runs before Oracle removes the row (permitting a customer to veto or to clean up dependent data), and DELETE_DELIVERABLE_POST runs after the delete has been committed within the transaction.
• LOCK_DELIVERABLE_PRE / LOCK_DELIVERABLE_POST — Hooks invoked when a deliverable is locked for update, used to enforce customer concurrency rules or audit locking activity.
• UPDATE_DELIVERABLE_PRE / UPDATE_DELIVERABLE_POST — Hooks surrounding modification of an existing deliverable.
• VALIDATE_DELIVERABLE_PRE / VALIDATE_DELIVERABLE_POST — Hooks surrounding validation, allowing additional customer-specific validation rules to be applied before persistence.

Each hook returns a return status so that the calling API can react to customer-code errors.

Tables Accessed

The ETRM metadata records no direct table references for this package. This is consistent with its nature as a user hook: the PL/SQL specification contains only procedure signatures and has no embedded SQL. All data manipulation is performed by the parent package AMS_Deliverable_PVT and its public wrapper AMS_Deliverable_PUB, which operate on the AMS deliverable tables (such as AMS_DELIVERABLES). Customer code that implements these hooks is responsible for any additional SQL it issues, typically reading or writing AMS deliverable tables or customer-maintained extension tables via APPS synonyms.

Usage Notes

AMS_DELIVERABLE_CUHK is never invoked directly by end users. It is called indirectly by AMS_Deliverable_PUB whenever a deliverable is created, updated, deleted, locked, or validated — whether the request originates from the Marketing Online forms, a concurrent program, or custom code that calls the public API. ETRM records that this package is referenced by one other package, which is the public deliverable API that fires the hooks.

Because the shipped routines are empty stubs, they perform no action until an implementer replaces the package body with customer logic. Typical implementations use DELETE_DELIVERABLE_PRE to prevent deletion of deliverables that are referenced by downstream campaigns or to cascade cleanup of related records, and the corresponding post-hook for audit trail writes. All customizations must be reapplied after patching or upgrade, since Oracle may reissue the stub body.