Search Results gmp_resources_pub




Overview
Explore in AI Chat

Overview

GMP_RESOURCES_PUB is the public PL/SQL interface for the Oracle Process Manufacturing (OPM) Generic Resources API. It resides in the APPS schema and is classified as a PUB (public) API, meaning it is intended for direct invocation by external callers, including Oracle E-Business Suite forms, concurrent programs, and customer-written extensions. The package provides the supported programmatic mechanism for creating, validating, updating, and deleting Generic Resources within OPM.

The package is defined with AUTHID CURRENT_USER, so it executes with the privileges of the calling session rather than as the package owner. It declares an API version constant (m_api_version) set to 1 and a package name constant (m_pkg_name) equal to 'GMP_RESOURCES_PUB', both used for standard API versioning and error-reporting conventions. The header carries the repository annotations @rep:product GMP, @rep:lifecycle active, and @rep:category BUSINESS_ENTITY GMP_GENERIC_RESOURCE, confirming its active status and its association with the GMP Generic Resource business entity.

The package also declares PL/SQL collection types used to marshal resource data: gmp_resources_tab, a table type based on cr_rsrc_mst%ROWTYPE; gmp_resources_dtl_tab, based on cr_rsrc_dtl%ROWTYPE; and the generic update_tbl_type with its record type update_table_rec_type, which lets callers specify which columns to update and the corresponding values. These types support the bulk, set-oriented handling of resource headers and details within a single API call.

Key Procedures and Functions

The package exposes four documented procedures:

  • INSERT_RESOURCES — Creates one or more Generic Resources from caller-supplied data after performing validation. It inserts rows into the resource master table cr_rsrc_mst. The API follows the standard OPM API signature pattern, accepting an API version, an initialization flag for the message list, a commit flag, and the resource information to be inserted, while returning the message count, the message list, and a return status indicating success, error, or unexpected error.
  • CHECK_DATA — Validates resource data supplied by the caller without persisting it. This procedure is the mechanism by which callers verify that a prospective resource definition satisfies OPM business and referential rules prior to invoking INSERT_RESOURCES or UPDATE_RESOURCES. Because the user searched for "check_data", it is worth noting that this is the validation entry point of the package.
  • UPDATE_RESOURCES — Modifies existing Generic Resource records. It works in conjunction with the update_tbl_type collection, which allows the caller to identify the specific columns requiring change and their new values, rather than supplying the entire row.
  • DELETE_RESOURCES — Removes Generic Resources that are no longer required, subject to the validation rules enforced by the API.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • CR_RSRC_MST — the generic resource master table; the primary target for inserts, updates, and deletes.
  • CR_RSRC_MST_B and CR_RSRC_MST_TL — the base and translation tables underlying the resource master, supporting the standard EBS multi-language entity pattern.
  • CR_RSRC_DTL — resource detail records associated with the master, reflected in the gmp_resources_dtl_tab collection type.
  • CR_RSRC_CLS — resource classes, used to validate the class assigned to a resource.
  • CM_CMPT_MST — the OPM item/master component table, consulted for validation of related entities.
  • MTL_UNITS_OF_MEASURE — the inventory unit-of-measure table, used to validate the UOM assigned to a resource.

Usage Notes

GMP_RESOURCES_PUB is the supported integration point for all programmatic maintenance of OPM Generic Resources. It is typically invoked from the OPM Generic Resources maintenance forms, from concurrent programs that perform bulk resource loads or migrations, and from custom PL/SQL code written by implementers. Callers should follow the standard OPM API protocol: pass the API version, respect the p_init_msg_list and p_commit conventions, inspect x_return_status for 'S', 'E', or 'U', and read x_message_list on failure. The documented metadata records no packages referencing GMP_RESOURCES_PUB, confirming it sits at the top of the call hierarchy rather than being an internal dependency. In EBS 12.1.1 and 12.2.2 environments the package retains the same public contract, with the header revision 120.5.12020000.1 reflecting its current shipped state.