Search Results create_group_usage




Overview
Explore in AI Chat

Overview

The PL/SQL package body APPS.JTF_RS_GROUP_USAGES_PVT is a private (PVT) API within the Oracle E-Business Suite Resource Manager (JTF_RS) module. Its purpose is to manage resource group usages, which are the associations that define how a given resource group is classified or applied — for example, whether a group functions as a team, a department, a resource pool, or another usage category recognized by the application. The package encapsulates the business logic required to create and remove these usage relationships while isolating callers from the underlying table structures.

As a private package, it is not intended as a public integration surface. Instead, it is invoked by other packages within the JTF_RS family, which serve as the supported entry points for external and framework-level callers. The package header comment confirms that its role is to perform business validations and then delegate the physical inserts and deletes to the corresponding table handler packages.

Key Procedures and Functions

The documented API exposes two procedures:

  • CREATE_GROUP_USAGE — Creates a new resource group usage record. The procedure accepts an API version, standardized message-list and commit control flags, a group identifier, a usage value, and a set of descriptive (attribute) columns. It applies business validation rules to the supplied group and usage combination before passing the request to the table handler that performs the actual insert. The commit flag allows the calling routine to defer or force the transaction boundary.
  • DELETE_GROUP_USAGE — Removes an existing resource group usage association. It validates that the usage relationship exists and is eligible for deletion, then delegates the physical delete to the appropriate table handler.

Both procedures follow the standard Oracle EBS private API convention: a version parameter for compatibility checking, message-list initialization and commit controls, and error propagation through the FND message stack rather than raised application exceptions. No public functions are documented for this body.

Tables Accessed

  • JTF_RS_GROUP_USAGES — The primary transactional table holding group-to-usage associations. This is the principal target of the create and delete operations.
  • JTF_RS_GROUP_USAGES_S — The sequence used to generate surrogate primary keys for new usage rows.
  • JTF_RS_GROUP_MEMBERS — Referenced as the source of the descriptive attribute column definitions used by the create procedure, and consulted for validation of group-related data.
  • JTF_RS_ROLE_RELATIONS — Consulted during business validation to confirm role and relationship constraints relevant to the group usage being created or removed.
  • DUAL — Used for lightweight validation and sequencing queries.

The documented table list reflects the package's pattern of validating against master and relationship data before writing to the usage table, ensuring referential and business consistency.

Usage Notes

This package is an internal implementation component rather than a public API. It is referenced by one other package, which acts as the supported caller and shields dependent code from changes to this body. Typical direct invocation originates from Resource Manager setup and administration flows, such as forms that maintain resource groups and their usage classifications, and from internal processing that provisions or retires group usages as part of team or resource-pool maintenance.

Custom code should avoid calling this private package directly. Where the functionality must be replicated or extended, the supported public API layer over JTF_RS should be used. When callers do invoke the procedures, they must observe the commit and message-list conventions: pass P_COMMIT as FND_API.G_FALSE when participating in a larger transaction, initialize the message list when standard error handling is required, and always supply the correct API version so compatibility checks succeed. In 12.1.1 and 12.2.2 the package signature and the documented table dependencies remain consistent.