Search Results delete_group_usage_pre

Overview

The APPS.JTF_RS_GROUP_USAGE_IUHK package is an Internal Industry User Hook API shipped with Oracle E-Business Suite Release 12.1.1 and 12.2.2 as part of the CRM Resource Manager (JTF_RS) schema. Its purpose is to provide a formal customization extension point around the creation and deletion of resource group usage records. Resource group usage describes the assignment of a usage classification to a resource group, thereby governing how members of that group may be utilized within the CRM resource model.

The package is classified as an "OTHER" API object in the ETRM repository. Rather than implementing business logic directly, it declares hook procedures that the Internal Industry — Oracle's framework for partner- and customer-specific extensions — may flesh out with pre- and post-processing logic. In its seeded/unmodified state, the bodies of these hooks are effectively empty, allowing customer-specific code to be layered in without modifying Oracle-owned source. This reflects the standard Oracle EBS practice of exposing internal industry hooks at well-defined transaction boundaries.

The header timestamp (120.0 2005/05/11) confirms the package has been stable since the 11i/12.0 era and remains present through 12.2.2, underscoring its role as a long-standing extension contract rather than an evolving functional module.

Key Procedures and Functions

Four procedures are documented in the package specification, each corresponding to a lifecycle event on resource group usage records:

• CREATE_GROUP_USAGE_PRE — Internal Industry hook invoked before a resource group usage record is created. It provides an entry point for validation or data preparation prior to the insert or update operation performed by the calling API.
• CREATE_GROUP_USAGE_POST — Internal Industry hook invoked after a resource group usage record is created. This is the procedure referenced by the search term "create_group_usage_post." It accepts the newly created group usage identifier, the associated group identifier, and the usage value, and returns a status indicator. It is intended for post-commit side effects such as logging, notification, or downstream synchronization.
• DELETE_GROUP_USAGE_PRE — Internal Industry hook invoked before a resource group usage record is removed, allowing pre-deletion checks or dependency validation.
• DELETE_GROUP_USAGE_POST — Internal Industry hook invoked after a resource group usage record is removed, permitting cleanup or audit activity.

All four procedures follow a consistent signature pattern: the relevant identifiers, the group usage value, and an X_RETURN_STATUS output parameter used to signal success or failure back to the caller. None of the procedures are documented as returning a value; they are procedural hooks with out-parameter status.

Tables Accessed

The ETRM metadata does not enumerate any tables referenced through APPS synonyms by this package. This is consistent with its design as a hook package: the seeded bodies contain no DML, and any table access occurs only in customer-supplied customization code added by the Internal Industry. Consequently, no direct INSERT, UPDATE, DELETE, or SELECT against base tables is documented as part of the delivered object. The underlying resource group usage data itself resides in the CRM resource tables managed by the corresponding non-hook APIs, not within this hook package.

Usage Notes

This package is not intended to be invoked directly by end users or standard Oracle forms. Instead, it is called by the primary CRM resource group usage APIs at defined points in their execution flow — specifically around create and delete operations. The ETRM repository records that the package is referenced by one other package, which serves as the calling API responsible for triggering these hooks.

Typical adoption follows the standard Oracle Internal Industry User Hook pattern: a customer or partner adds custom PL/SQL logic inside the seeded hook bodies via a supported patching or extension mechanism, thereby injecting business rules into the resource group usage lifecycle without altering Oracle-owned code. Because the hooks ship effectively empty, any behavior observed from them is entirely dependent on site-specific customization. Support and upgrade considerations therefore hinge on the extension code, not on the delivered package. Developers investigating "create_group_usage_post" should treat it strictly as an extension point for post-insert processing on resource group usage records.