Search Results jtf_rs_group_usage_vuhk




Overview
Explore in AI Chat

Overview

JTF_RS_GROUP_USAGE_VUHK is a Vertical Industry User Hook (VUHK) package in the Oracle E-Business Suite Resource Manager (JTF_RS) module. Its purpose is to expose extension points that allow vertical industry solutions and customer-specific customizations to inject business logic into the lifecycle of resource group usage records. The package is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoker rather than the definer, so any implementation logic runs under the calling user's security context. The header comment identifies it explicitly as the Vertical Industry User Hook API, and notes that vertical industries may register pre- and post-processing procedures against resource group usage operations.

In Oracle EBS 12.1.1 and 12.2.2, the resource group usage construct associates a resource group with a particular usage classification. The VUHK pattern is a standard Oracle extension mechanism: the base product calls empty stub procedures at defined points, and implementers replace or extend those stubs with their own logic. No functional transformation occurs in the shipped package itself; it is a placeholder for downstream customization.

Key Procedures and Functions

Four procedures are documented in the package specification, covering pre- and post-processing for both creation and deletion of resource group usage records.

  • CREATE_GROUP_USAGE_PRE — Invoked before a resource group usage record is created. Intended for validation, defaulting, or derivation logic that must run prior to the insert. Accepts the group identifier and usage value as inputs and returns a status indicator.
  • CREATE_GROUP_USAGE_POST — Invoked after the resource group usage record has been created. Intended for side effects such as audit logging, downstream synchronization, or notification. Accepts the newly created usage identifier, the group identifier, and the usage value, and returns a status indicator.
  • DELETE_GROUP_USAGE_PRE — Invoked before a resource group usage record is deleted. Intended for referential checks or business rule enforcement that should block or permit the deletion. Accepts the group identifier and usage value and returns a status indicator.
  • DELETE_GROUP_USAGE_POST — Invoked after deletion. Intended for cleanup or archival activity triggered by the removal. Accepts the group identifier and usage value and returns a status indicator.

Each procedure surfaces an X_RETURN_STATUS OUT parameter, enabling the hook implementation to signal success or failure back to the calling application. Notably, the creation hooks receive a P_USAGE parameter (the value the user searched for), while the post-creation hook additionally receives P_GROUP_USAGE_ID, since the primary key is only known after the insert.

Tables Accessed

The ETRM metadata lists references to CN_REPOSITORIES_ALL, CN_SRP_INTEL_PERIODS, and PLITBLM through APPS synonyms. These associations are inherited from the broader JTF_RS group usage processing stack rather than from the hook bodies themselves, which are empty in the shipped product. CN_REPOSITORIES_ALL and CN_SRP_INTEL_PERIODS belong to the Channel Manager / sales resource planning schema and are relevant where resource group usage participates in territory or intelligence period configuration. PLITBLM is the standard PL/SQL table-to-database bulk manipulation utility used by the Oracle Forms infrastructure, consistent with the package being invoked from an EBS form.

Usage Notes

This package is not typically invoked directly by end users or by concurrent programs. It is called by the base JTF_RS resource group maintenance logic—most commonly the Resource Groups form—at each of the four defined extension points. The metadata records that it is referenced by one other package, confirming it sits within a call chain rather than at the top level.

Implementation guidance follows the VUHK convention: the APPS-owned specification should not be modified. Instead, a custom package implementing the same signatures is registered, or the existing stubs are replaced through a supported customization path during an upgrade-safe patch. Because the procedures run under AUTHID CURRENT_USER, custom implementations must ensure the invoking user holds the necessary object privileges. When upgrading between 12.1.1 and 12.2.2, existing hook implementations should be reviewed to confirm that the group usage call points remain intact.