Results for “ams_eventoffer_cuhk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_EVENTOFFER_CUHK is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The suffix "CUHK" identifies it as a customer-specific customization (a "C" hook) of the standard Oracle Marketing event offer logic. Its role is to provide an event-driven extension layer around the seeded Event Offer business object processing performed by AMS_EVENTOFFER_PVT. Whereas AMS_EVENTOFFER_PVT encapsulates the core create, update, delete, lock, and validate operations for marketing event offers, AMS_EVENTOFFER_CUHK intercepts those operations at defined pre- and post-processing points, allowing site-specific validation, defaulting, enrichment, or side effects to be applied without modifying Oracle's base code. In the 12.2.2 ETRM documentation the package is classified as an API classification of OTHER, is marked VALID, and exposes ten documented entry points — five "PRE" and five "POST" procedures — that mirror the five primary event offer transactions. It references AMS_EVENTOFFER_PVT, the FND_API public utility package, and the SYS.STANDARD package, and it is not referenced by any other database object, confirming its position as a leaf-level customization rather than a shared library.

Key Procedures and Functions

The package exposes ten public procedures, organized as pre/post pairs around the standard event offer lifecycle. The naming convention follows Oracle's standard customization pattern, where PRE procedures execute before the corresponding base operation and POST procedures execute after it.

• CREATE_EVENTOFFER_PRE — invoked before a new event offer record is created; typically used to apply custom defaulting, derive values, or perform pre-insert validation.
• CREATE_EVENTOFFER_POST — invoked after the event offer creation completes; used for post-insert actions such as populating dependent data or triggering notifications.
• UPDATE_EVENTOFFER_PRE — runs before an existing event offer is modified, supporting change-specific validation and attribute adjustment.
• UPDATE_EVENTOFFER_POST — runs after the update completes, supporting downstream propagation or logging.
• DELETE_EVENTOFFER_PRE — executes before deletion, allowing referential or business-rule checks that may prevent removal.
• DELETE_EVENTOFFER_POST — executes after deletion, enabling cleanup of related custom data.
• LOCK_EVENTOFFER_PRE — runs before the event offer record is locked, typically prior to an update, to enforce custom locking or concurrency rules.
• LOCK_EVENTOFFER_POST — runs after the lock is obtained, permitting post-lock state checks.
• VALIDATE_EVENTOFFER_PRE — runs before standard validation to apply additional site-specific validation logic.
• VALIDATE_EVENTOFFER_POST — runs after standard validation, allowing supplementary validation or error aggregation.

Tables Accessed

The ETRM metadata for AMS_EVENTOFFER_CUHK does not list any directly referenced application tables. This is consistent with its design as a hook package: direct DML against event offer tables is performed by AMS_EVENTOFFER_PVT, while the CUHK procedures interact primarily with the PL/SQL API and any custom structures introduced by the customer. Any table access is therefore mediated through AMS_EVENTOFFER_PVT and the FND_API layer rather than through direct SQL against AMS base tables.

Usage Notes

AMS_EVENTOFFER_CUHK is not intended to be called directly by end users. It is invoked by Oracle Marketing event offer processing — typically through the standard event offer maintenance forms, the AMS_EVENTOFFER_PVT API, or concurrent processes that drive event offer transactions — wherever the corresponding customization hooks are wired. The documented dependency on FND_API indicates use of the standard Oracle error-handling and message conventions (for example, FND_API.G_RET_STS_SUCCESS and the FND_MSG_PUB stack). Because the package body is marked VALID and is not referenced by any other database object, it can be recompiled or re-customized with limited blast radius. Implementers extending this package should preserve the documented pre/post contract, never alter AMS_EVENTOFFER_PVT signatures, and ensure that all custom logic returns control cleanly so that standard event offer processing continues unaffected.