Search Results validate_deliverable

Overview

APPS.AMS_DELIVERABLE_VUHK is a customer user hook (VUHK) package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. Its sole architectural purpose is to expose user-defined extension points for the public deliverable API, AMS_Deliverable_PUB, which governs the lifecycle of marketing deliverables — the tangible or intangible outputs tracked against a campaign or marketing activity, such as collateral, events, or media placements.

User hook packages in EBS follow a consistent convention: the core public API invokes stubbed pre- and post-processing procedures at defined points in its execution flow. The shipping version of the hook contains empty bodies, and customers or implementation partners insert custom PL/SQL logic into those bodies without modifying Oracle-owned code. This preserves upgrade safety, since the hook package is flagged as a customer-owned object and is not overwritten by patching. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than as the APPS schema owner, which is the standard posture for customer extension code.

Key Procedures and Functions

The package exposes ten documented procedures arranged as five pre/post pairs, mirroring the five operations of the underlying public API:

• CREATE_DELIVERABLE_PRE / CREATE_DELIVERABLE_POST — Pre-processing fires before the deliverable record is inserted; post-processing fires afterward and receives the generated deliverable identifier, allowing the hook to write dependent rows or external system references.
• UPDATE_DELIVERABLE_PRE / UPDATE_DELIVERABLE_POST — Extend the update flow of an existing deliverable record, useful for propagating changes to downstream entities or enforcing cross-attribute validation.
• DELETE_DELIVERABLE_PRE / DELETE_DELIVERABLE_POST — Allow custom logic to execute around removal of a deliverable. The pre-hook carries the deliverable identifier and object version, supporting concurrency checks before deletion proceeds.
• LOCK_DELIVERABLE_PRE / LOCK_DELIVERABLE_POST — Hook points around the locking operation, which is used to prevent concurrent modification of a deliverable record.
• VALIDATE_DELIVERABLE_PRE / VALIDATE_DELIVERABLE_POST — Surround validation logic, permitting additional business rules to be applied before or after the seeded validation step. This is the procedure pair most commonly associated with the user's search term "validate_deliverable."

Common conventions across these hooks include an IN OUT record parameter typed against AMS_Deliverable_PVT.deliv_rec_type for create, and an OUT return status parameter (x_return_status) by which the hook signals success, error, or unexpected failure back to the calling API. The post-validation and post-create procedures receive the deliverable identifier as an IN parameter because the record has already been persisted at that point.

Tables Accessed

The ETRM metadata records no direct table references for this package. This is consistent with its design: the hook procedures operate on the PL/SQL record type defined in AMS_Deliverable_PVT and rely on the public API to perform all DML against the underlying AMS deliverable tables. Any table access performed by customer code inserted into these hooks is the responsibility of that custom code, not of the seeded package.

Usage Notes

AMS_DELIVERABLE_VUHK is not invoked directly by end users. It is called programmatically by AMS_Deliverable_PUB and, per the metadata, is referenced by one other package. Typical invocation paths include the Oracle Marketing deliverable forms, concurrent programs that bulk-create or update deliverables, and custom integrations that call the public API. Because the seeded bodies are empty no-ops, the package has no runtime effect until a customer implements logic within one or more of the ten hooks. Implementers should note that exceptions raised inside a hook propagate to the calling API and can abort the entire transaction; therefore, error handling and the correct setting of x_return_status are essential. Because the package is AUTHID CURRENT_USER, any custom SQL must reference objects through synonyms or fully qualified names accessible to the invoking schema.