Search Results create_resource_group

Overview

APPS.JTF_RS_GROUPS_PUB_W is a public PL/SQL wrapper package within the Oracle E-Business Suite Resource Management (JTF_RS) schema family. Its principal business function is to provide a programmatic interface for the creation, migration, and maintenance of resource groups — logical collections of resources (such as employees, partners, or service personnel) that are used throughout CRM and field service modules for assignment, routing, scheduling, and reporting. The package encapsulates the underlying business logic and validation rules required to persist resource group definitions consistently, so that calling applications do not interact directly with the base tables.

The package header originates from a relatively early release (header revision 120.0, dated 2005) and the wrapper pattern indicated by the "_PUB_W" suffix confirms that it is a published, callable API rather than an internal implementation unit. It is classified under the ETRM API classification of OTHER, meaning it is not a primary business object API but rather a supporting utility API. Notably, the package is referenced by zero other packages according to the ETRM metadata, indicating that it is intended to be invoked by external callers — concurrent programs, forms, or custom extensions — rather than by other PL/SQL units within the same application. The API exposes standard messaging and transaction-control conventions, including x_return_status, x_msg_count, and x_msg_data out parameters, which is consistent with the Oracle Application Object Library (AOL) error-handling pattern.

Key Procedures and Functions

The package documents three callable procedures:

• CREATE_RESOURCE_GROUP — The primary creation routine. It accepts identifying attributes such as group name, description, an exclusivity flag, an email address, start and end dates for active status, and an accounting code. It returns the generated resource group identifier and group number to the caller through out parameters. This procedure is the entry point implied by the user search term "create_resource_group."
• CREATE_RESOURCE_GROUP_MIGRATE — A migration-oriented variant of the creation routine. In addition to the standard descriptive attributes, it accepts a caller-supplied group identifier and a full set of fifteen attribute columns plus an attribute_category, allowing legacy or external data to be loaded while preserving source identifiers and descriptive-flexfield values. Both generated group identifier and group number are returned.
• UPDATE_RESOURCE_GROUP — Updates an existing resource group. It identifies the target group by group identifier or group number and permits modification of the descriptive, exclusivity, email, date-range, and accounting attributes.

All three procedures carry parameters for API version, message list initialization, and commit control, consistent with standard EBS public API signatures. The message list initialization and commit flags allow the caller to control transaction boundaries and manage the validation message stack.

Tables Accessed

The ETRM metadata provided does not enumerate the specific base tables accessed through APPS synonyms. Functionally, the package is expected to read from and write to the JTF_RS resource group base tables (for example, JTF_RS_GROUPS_B and JTF_RS_GROUPS_TL, which hold the group identifiers, numbers, names, descriptions, date ranges, and translated name/description columns), together with associated group member tables maintained by sibling APIs. Callers should treat these tables as encapsulated and use this package exclusively rather than performing direct DML, which would bypass validation and date-effectivity logic. The package also participates in the standard EBS validation pattern through the AOL message dictionary.

Usage Notes

Because the package has no internal package dependencies, it is typically invoked from external client code, concurrent programs, or Oracle Forms-based maintenance screens. The recommended pattern for a custom caller is to initialize the message list, invoke the procedure with p_commit set to FALSE, inspect x_return_status for success or failure, retrieve and log error messages using the returned message count and data, and commit only after all validations succeed. The migrate variant should be reserved for data conversion, legacy migration, or integrations that supply pre-existing identifiers and flexfield attributes; it is not intended for standard runtime creation. As with all published EBS APIs, the interface should be treated as a stable contract, and callers should rely on the documented out parameters for generated identifiers and error reporting.