Search Results validate_frt_class

Overview

GMI_VALID_GRP is an inventory validation package owned by the APPS schema in Oracle EBS. It is classified as a Group (GRP) API within the Enterprise Technical Reference Model, indicating that it aggregates a family of related validation routines rather than exposing a single business transaction. The package header declares AUTHID CURRENT_USER, meaning that its unqualified references to database objects resolve against the privileges of the calling session, a design consistent with an internal validation library rather than a public, self-contained API.

The package source, GMIGVALS.pls, dates from the original Process Manufacturing (OPM) product line and carries a header revision of 115.2 from July 1999. Its stated purpose is to contain inventory validation functions and procedures. In practice, GMI_VALID_GRP centralises the attribute-level edit checks applied to item, lot, sublot, location, warehouse and classification master data before that data is committed by OPM inventory programs. Because these checks are grouped, callers can reuse the same validation logic across forms, concurrent programs and batch interfaces, ensuring consistent enforcement of OPM data rules across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented interface comprises 47 callable units. The following are the most significant, grouped by the entity they validate.

• Item validation: VALIDATE_ITEM_EXISTANCE confirms that a supplied item number exists in the item master; VALIDATE_NONINV_IND verifies the non-inventory flag; VALIDATE_INACTIVE_IND checks the item's active/inactive status; VALIDATE_ITEM_ABCCODE validates the ABC classification code.
• Unit of measure validation: VALIDATE_DUALUM_IND validates the dual unit of measure indicator and VALIDATE_ITEM_UM2 validates the secondary unit of measure in relation to that indicator.
• Lot and sublot validation: VALIDATE_LOT_CTL validates the lot control flag; VALIDATE_LOT_INDIVISIBLE — the routine associated with the search term "validate_lot_indivisible" — verifies that a lot-indivisible indicator is consistent with the item's lot control setting; VALIDATE_SUBLOT_CTL validates sublot control against lot control.
• Quality and shelf-life validation: VALIDATE_DEVIATION validates deviation limits; VALIDATE_SHELF_LIFE validates shelf-life attributes; VALIDATE_RETEST_INTERVAL validates the retest interval.
• Location and warehouse validation: VALIDATE_LOCT_CTL validates location control, drawing on the location master.
• Classification validation: VALIDATE_MATCH_TYPE and the class validators — VALIDATE_GL_CLASS, VALIDATE_INV_CLASS, VALIDATE_SALES_CLASS, VALIDATE_SHIP_CLASS, VALIDATE_FRT_CLASS and VALIDATE_INV_TYPE — confirm that classification codes and inventory types supplied by a caller exist and are valid for the item.

Return types vary by routine. Some return NUMBER, others BOOLEAN, and VALIDATE_ITEM_EXISTANCE is declared to return NUMBER. Callers must therefore observe the individual signature rather than assume a uniform Boolean result.

Tables Accessed

The package resolves its data through APPS synonyms over the OPM inventory schema. Item-level checks read IC_ITEM_MST (the item master), with conversions and packaging data read from IC_ITEM_CNV and IC_ITEM_CPG. Lot and sublot rules draw on IC_LOTS_MST. Location and warehouse checks reference IC_LOCT_MST and IC_WHSE_MST. Supplier validation uses PO_VEND_MST, while method data is read from CM_MTHD_MST. The classification validators read the corresponding class masters: IC_ALLC_CLS, IC_COMD_CDS, IC_COST_CLS, IC_CTMS_CLS, IC_FRGT_CLS, IC_GLED_CLS, IC_SQDT_CLS and CR_SQDT_CLS. All access is read-oriented validation lookups.

Usage Notes

GMI_VALID_GRP is an internal validation library. It is referenced by four other packages within the OPM inventory and process execution stack, which use it to pre-validate user input before insert or update operations. Typical invocation points include OPM item and lot maintenance forms, inventory transaction and lot entry forms, and batch or interface programs that stage records before committing to the item and lot masters. Custom code should call the individual validation function appropriate to the attribute being checked and handle the returned NUMBER or BOOLEAN value explicitly, rather than attempting to invoke the package as a single validation entry point. Because the package executes with AUTHID CURRENT_USER, custom callers require direct privileges on the underlying IC_ and CM_ tables, or must be granted execute on the package through a privileged schema.