Results for “ams_actresource_vuhk”

27 results




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

Overview

AMS_ACTRESOURCE_VUHK is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as an Oracle Marketing (AMS) resource API object. Its name follows the EBS "VUHK" naming convention used for table-handler (or validation, update, and handling) components associated with an underlying entity, in this case the "resource" concept managed by AMS_ACTRESOURCE_PUB. The package acts as a thin, event-oriented wrapper around the public resource API, exposing a symmetrical set of pre- and post-processing hooks that surround each core operation performed on marketing resources.

Within the Oracle Marketing and Trade Management (ETRM) modules, resources represent the parties, people, or units that can be assigned to campaigns, offers, and other marketing activities. The VUHK package provides the interception layer that allows business events such as validation, creation, update, deletion, and locking to be extended, audited, or augmented without modifying the central AMS_ACTRESOURCE_PUB API. This separation of concerns is characteristic of the Oracle Application Object Library (FND) coding style, and the package depends on FND_API for standard API constants and error-handling primitives.

Key Procedures and Functions

The package body documents ten entry points, organized as five paired pre- and post-operation handlers:

This pre/post pattern means each documented procedure is a hook rather than a full business operation; the substantive persistence logic resides in APPS.AMS_ACTRESOURCE_PUB. Parameter lists are not enumerated in the available metadata and should be confirmed against the decrypted package source before extending the code.

Tables Accessed

The documented metadata records no tables referenced directly via APPS synonyms. All database access is therefore indirect, performed through the AMS_ACTRESOURCE_PUB API, which in turn reads and writes the underlying AMS resource tables. Consequently, the VUHK body should be treated as a lightweight orchestration unit rather than a data-access module. Any resource attributes the hooks need must be obtained by calling AMS_ACTRESOURCE_PUB or other standard APIs, consistent with the product's encapsulation rules.

Usage Notes

Because the package is not referenced by any database object and is itself dependent on AMS_ACTRESOURCE_PUB, FND_API, and SYS.STANDARD, it is not intended as a general-purpose entry point. It is invoked internally by the resource API framework or by marketing setup procedures that have been configured to call event hooks. Typical invocation scenarios include marketing forms and concurrent programs that process resource records, where the pre- and post-handlers offer an extension point for custom validation, auditing, or integration logic without patching seeded code. The same package body is valid in both EBS 12.1.1 and 12.2.2; the object is reported as valid, and one other package references it. Customizations should be placed in a separate custom package that is called from these hooks rather than modifying the seeded body directly, ensuring upgrade safety.