Search Results ams_actresource_cuhk

Overview

AMS_ACTRESOURCE_CUHK is a PL/SQL package body owned by the APPS schema that implements the customization hook layer for the Oracle Marketing (AMS) resource activity API. The suffix "CUHK" denotes the Oracle E-Business Suite customization hook naming convention: these packages are delivered as stub bodies intended to be modified or extended by implementers so that site-specific business logic executes at defined interception points around the standard API processing. Rather than replacing the base API, the hook package allows extensions to run immediately before ("_PRE") and immediately after ("_POST") each core operation performed by AMS_ACTRESOURCE_PUB, preserving Oracle's upgrade path for the seeded code.

In release 12.1.1 and 12.2.2 the object is documented with a VALID status, an API classification of OTHER, and a dependency on AMS_ACTRESOURCE_PUB, FND_API, and the SYS STANDARD package. Ten documented entry points are exposed, covering resource creation, update, deletion, locking, and validation.

Key Procedures and Functions

All ten documented program units are parameterless hook stubs in the seeded version; implementers add logic within each body. They are organized as pre- and post-processing pairs:

• CREATE_RESOURCE_PRE — Executes before the standard resource creation logic in AMS_ACTRESOURCE_PUB. Typically used to default or derive attribute values, perform prerequisite validations, or seed ancillary data required by the create transaction.
• CREATE_RESOURCE_POST — Executes after a resource has been successfully created. Commonly used for integration side effects such as notifications, outbound interface calls, or denormalized updates in custom tables.
• UPDATE_RESOURCE_PRE — Runs before an existing resource record is modified, permitting last-minute validation or adjustment of the incoming changes.
• UPDATE_RESOURCE_POST — Runs after a successful update, supporting audit capture, dependent record synchronization, or workflow initiation.
• DELETE_RESOURCE_PRE — Runs before resource deletion; frequently used to block deletion when referential conditions exist or to archive data prior to removal.
• DELETE_RESOURCE_POST — Runs after deletion completes, allowing cleanup of related custom data.
• LOCK_RESOURCE_PRE — Runs before a resource is locked, supporting eligibility checks or the capture of lock context.
• LOCK_RESOURCE_POST — Runs after locking, typically for notification or audit purposes.
• VALIDATE_RESOURCE_PRE — Runs prior to standard validation, permitting additional site-specific validation rules to be asserted.
• VALIDATE_RESOURCE_POST — Runs after validation, used to react to validation results or to persist derived validation outcomes.

Tables Accessed

The ETRM metadata for AMS_ACTRESOURCE_CUHK does not enumerate direct table references through APPS synonyms. This is consistent with its role as a hook package: in the seeded form the bodies are empty and therefore issue no SQL. Any table access is introduced by customer extensions and would typically target the Oracle Marketing resource tables managed by AMS_ACTRESOURCE_PUB (for example, resource and resource-activity association entities), plus any customer-defined staging or audit tables. Because the package is not referenced by any other database object, its runtime footprint is determined entirely by the customization logic applied within each hook.

Usage Notes

AMS_ACTRESOURCE_CUHK is not invoked directly by end users. It is called internally by AMS_ACTRESOURCE_PUB at the designated pre- and post-processing points whenever the base resource API is executed — whether from Oracle Marketing forms, concurrent programs, or custom code that invokes AMS_ACTRESOURCE_PUB. The documented dependency chain (AMS_ACTRESOURCE_PUB referencing AMS_ACTRESOURCE_CUHK, which in turn references FND_API and STANDARD) reflects that the base API owns the calls into the hook while the hook may leverage FND_API for message handling and error stacking.

Implementers should note that AMS_ACTRESOURCE_CUHK is referenced by exactly one other package, so changes to it have a narrow but critical blast radius: the resource activity API path. Standard practice is to keep hook logic defensive, respect the FND_API error-handling conventions, and avoid raising unhandled exceptions that would abort the calling API transaction. Because the hooks are customer-owned extension points, their contents are not overwritten by patching, but they must be re-validated after upgrades to confirm compatibility with the current AMS_ACTRESOURCE_PUB signature and processing sequence.