Search Results lock_resource_pre

Overview

AMS_ACTRESOURCE_CUHK is a customer hook package within the Oracle E-Business Suite Activity Management (AMS) module, which is part of the Enterprise Territory and Resource Management (ETRM) family of applications. The suffix "CUHK" indicates that this is a customer-defined hook, a standard extensibility construct Oracle provides so that organizations can inject custom business logic into seeded public APIs without modifying Oracle-owned code. This package serves as the customer-hook counterpart to the public resource API, AMS_ActResource_PUB, and declares a paired pre-processing and post-processing procedure for each of the major resource lifecycle operations: create, update, delete, validate, and lock. Each procedure body is intended to be implemented by the customer to meet site-specific requirements. The package is declared with AUTHID CURRENT_USER, meaning that at runtime its SQL statements execute with the privileges of the invoking user rather than the package owner, which is significant in a shared APPS schema environment. Its ETRM classification is OTHER, reflecting that it is an extension framework rather than a standalone business API.

Key Procedures and Functions

The package exposes ten documented procedures, organized as five pre/post pairs corresponding to operations on activity resources:

• create_resource_pre — Customer pre-processing hook invoked before a resource is created. It receives the resource record as an IN OUT NOCOPY parameter together with a return status, allowing the customer to inspect or modify the incoming data before the public create logic runs.
• create_resource_post — Customer post-processing hook invoked after resource creation; it is passed the resource record and the newly assigned resource identifier.
• delete_resource_pre — Pre-processing hook for resource deletion, receiving the resource ID and object version as IN OUT NOCOPY parameters so the customer can validate or adjust them before deletion.
• delete_resource_post — Post-processing hook for deletion, provided with the resource ID and object version of the deleted record.
• lock_resource_pre — Customer pre-processing hook for the lock_resource operation, allowing custom validation or side effects before a resource is locked.
• lock_resource_post — Customer post-processing hook for lock_resource, executed after the lock has been applied.
• update_resource_pre — Customer pre-processing hook invoked before a resource is updated.
• update_resource_post — Customer post-processing hook invoked after an update completes.
• validate_resource_pre — Pre-processing hook for resource validation logic.
• validate_resource_post — Post-processing hook for resource validation.

As documented, no parameter lists are invented here beyond what the metadata shows; the purpose of each procedure is customer extension at the designated point in the resource transaction flow.

Tables Accessed

The ETRM metadata excerpt does not enumerate the tables referenced by this package through APPS synonyms. This is consistent with the package's design as a hook template: the declared procedures are stubs, and any table access would be supplied by the customer's own implementation rather than by Oracle. Consequently, no specific AMS base tables (such as the activity resource tables behind AMS_ActResource_PUB) can be asserted from the documentation. The package instead exchanges data with the public API layer via the AMS_ActResource_PUB.Act_Resource_rec_type record structure.

Usage Notes

AMS_ACTRESOURCE_CUHK is not invoked directly by end users. It is called internally by the AMS resource public API, which routes through the corresponding hook at each lifecycle event, giving customers a controlled extension point. The package is referenced by one other package within the ETRM inventory, confirming its role as a dependent extension module rather than an entry point. Typical implementation involves a technical consultant editing the customer hook bodies to add site-specific validation, defaulting, or integration calls, then recompiling the package in the APPS schema. Because AUTHID CURRENT_USER is in effect, privilege and synonym configuration must be checked carefully when implementing custom logic, particularly in Oracle EBS 12.1.1 and 12.2.2 environments where editioning and the Online Patching model in 12.2.2 impose additional file placement and compilation considerations.