Search Results create_group_usage_pre

Overview

The APPS.JTF_RS_GROUP_USAGE_IUHK package is an Internal Industry User Hook (IUHK) API within the Oracle E-Business Suite Resource Manager (JTF_RS) module. Its purpose is to expose controlled extension points where Oracle's Internal Industry vertical can insert customer-specific pre- and post-processing logic around the creation and deletion of resource group usage records. Resource group usage associates a resource group with a particular usage type, and this hook package sits between the caller and the underlying group usage business logic so that additional validation, defaulting, integration calls, or side effects can be applied without modifying base Oracle code.

The package is a specification-only stub: every documented procedure body is empty by default, which is the standard pattern for EBS user hooks. Customers or Internal Industry developers populate the stub bodies in a copied or customized version of the package, or the hooks are invoked by the framework at the designated lifecycle moments.

Key Procedures and Functions

The package exposes four documented procedures, all of which return status information to the caller:

• CREATE_GROUP_USAGE_PRE — The pre-processing hook executed before a resource group usage row is created. It is invoked with the group identifier and the usage value, and returns an out status parameter so that callers can detect whether the hook succeeded. Because it is the "pre" event, this is the appropriate place for validations or defaults that must complete before the insert.
• CREATE_GROUP_USAGE_POST — The post-processing hook executed after the resource group usage record has been created. It receives the newly assigned group usage identifier in addition to the group identifier and usage value, allowing downstream processing (such as integration with other modules) to reference the generated primary key.
• DELETE_GROUP_USAGE_PRE — The pre-processing hook executed before a resource group usage record is deleted. It receives the group identifier and usage value and returns a status, enabling callers to abort or augment the deletion.
• DELETE_GROUP_USAGE_POST — The post-processing hook executed after deletion, receiving the same group identifier and usage value so that cleanup or logging logic can be performed.

All four procedures follow the same parameter pattern: input parameters identify the affected group and usage, and a single out parameter (X_RETURN_STATUS) communicates success or failure back to the calling process.

Tables Accessed

The ETRM metadata documents no direct table references for this package via APPS synonyms. This is consistent with its role as a hook specification: the package itself does not perform DML, but instead is invoked by the base resource manager logic that manipulates the resource group usage tables. Any table access occurs in the calling packages or in custom hook implementations rather than in this API.

Usage Notes

This hook package is referenced by one other package, which is the base implementation that calls these procedures at the appropriate points during group usage creation and deletion. It is not typically invoked directly from Oracle Forms or concurrent programs; instead, the framework calls the hooks transparently whenever a resource group usage is added or removed through the standard Resource Manager APIs or associated application flows.

Customization is performed by placing customer-specific logic inside the stub procedures. If the hooks are not customized, they execute as no-ops and return a successful status, preserving normal behavior. When customized, the out status parameter should be set to a failure indicator to signal the calling process to discontinue the operation, particularly in the "pre" hooks. Because the package is owned by APPS and versioned as part of the JTF_RS schema, upgrades may overwrite modifications; customizations should therefore be managed through the supported EBS extension mechanisms.