Search Results validate_input_params




Overview
Explore in AI Chat

Overview

APPS.GMD_ITEM_TECHNICAL_DATA_PUB is a public PL/SQL package body within the Oracle E-Business Suite Process Manufacturing (OPM) module. Its business function is to expose a programmatic interface for creating, maintaining, retrieving, and removing item technical data records. Item technical data represents the process-manufacturing attributes that are associated with an item across a specific organization, including technical parameters that describe quality, specification, and processing characteristics used by formula, recipe, and quality workflows.

The package follows the standard Oracle EBS public API design pattern. It defines a header record type (technical_data_hdr_rec) and a detail table type (technical_data_dtl_tab) that allow callers to pass structured item technical data in a single invocation. A private validation routine, VALIDATE_INPUT_PARAMS, is declared to verify the header record, the detail table, and the requested operation before the database is modified. Because the object is classified as a PUB package, it is intended to be called from outside its own module and is treated as a stable integration point.

Key Procedures and Functions

The documented package exposes four public procedures, each mapping to a standard CRUD operation on item technical data:

  • INSERT_ITEM_TECHNICAL_DATA — Creates a new item technical data header together with its associated detail lines. It accepts standard API parameters including API version, initialization message list, commit flag, return status, and message count/data outputs, along with the header record and detail table.
  • UPDATE_ITEM_TECHNICAL_DATA — Modifies existing item technical data records, applying changes to the header and its detail rows for a specified item and organization context.
  • DELETE_ITEM_TECHNICAL_DATA — Removes item technical data records identified by the caller-supplied keys.
  • FETCH_ITEM_TECHNICAL_DATA — Retrieves item technical data into the header record and detail table output structures for downstream processing or display.

In addition to the four public procedures, the body contains the private helper VALIDATE_INPUT_PARAMS, which the user searched for. This routine is declared in the package header with inputs of the header record, the detail table, and the operation name, returning a return status. It centralizes parameter-level validation so that each public procedure can reject malformed or incomplete input before performing persistence work. It is not callable directly by external code.

Tables Accessed

The package reads and writes the core item technical data tables and their surrounding reference tables through APPS synonyms:

  • GMD_TECHNICAL_DATA_HDR and GMD_TECHNICAL_DATA_DTL — the header and detail tables that store the item technical data being inserted, updated, deleted, or fetched.
  • GMD_TECH_PARAMETERS_B — the technical parameter definition table, queried (as shown in the source cursor) to determine the data type of a technical parameter for a given organization, including parameters defined at the global organization level.
  • GMD_PARAMETERS_HDR — parameter header definitions supporting the technical parameter validation and interpretation.
  • FM_FORM_MST and FM_MATL_DTL — formula and material detail tables, used to validate that the technical data references valid formula or material structures.
  • MTL_SYSTEM_ITEMS — the master item table, used to validate the item being processed.
  • MTL_LOT_NUMBERS — lot number data, supporting lot-level technical data association.
  • PLITBLM — a temporary/work table used during processing of detail collections.

Usage Notes

GMD_ITEM_TECHNICAL_DATA_PUB is typically invoked from Process Manufacturing setup and maintenance forms, from concurrent programs that load or maintain item technical data, and from custom PL/SQL integration code. Since it is a PUB API, callers should invoke it within the standard API framework: set the initialization message list as needed, supply a valid API version, check x_return_status for FND_API.G_RET_STS_SUCCESS, and inspect the message count and message data outputs for error handling. Because the referenced-by count is one package, the direct dependency surface is small, but the tables underneath are shared process-manufacturing entities, so transaction control and commit handling should follow OPM conventions.