Search Results check_who

Overview

GMD_SPEC_VRS_GRP is the group-layer PL/SQL package in Oracle EBS Process Manufacturing (OPM) that manages Specification Validity Rules. Specification Validity Rules determine which quality specifications apply to a given item, organization, customer, supplier, or WIP context during a defined validity window. The package body implements the business logic required to create, validate, and delete validity rules across five specification domains: monitoring, inventory, WIP, customer, and supplier specifications. It is classified as a "GRP" (group) API in the ETRM register, meaning it exposes higher-level, transaction-oriented entry points built on top of the underlying specification table APIs.

The package header identifies the file as GMDGSVRB.pls (version 120.11.12010000.2), with an original author history dating to 2002 and continued maintenance through 2004 covering bug fixes and enhancements such as delayed lot entry support (Enhancement #3476560) and duplicate obsolete-status handling (Bug 3090290). Because the logic spans both Oracle EBS 12.1.1 and 12.2.2, the package remains relevant in either release when OPM quality modules are licensed and configured.

Key Procedures and Functions

The 23 documented entry points fall into three functional families.

• Domain validators — VALIDATE_MON_VR, VALIDATE_INV_VR, VALIDATE_WIP_VR, VALIDATE_CUST_VR, and VALIDATE_SUPP_VR check a proposed validity rule for a specific specification type, enforcing required attributes, foreign-key integrity, and control flags such as delayed lot entry.
• Null and FK helpers — CHECK_FOR_NULL_AND_FKS_IN_MVR, CHECK_FOR_NULL_AND_FKS_IN_IVR, CHECK_FOR_NULL_AND_FKS_IN_WVR, CHECK_FOR_NULL_AND_FKS_IN_CVR, and CHECK_FOR_NULL_AND_FKS_IN_SVR perform the mandatory-column and referential checks that the validators call.
• Existence checks — MON_VR_EXIST, INV_VR_EXIST, WIP_VR_EXIST, CUST_VR_EXIST, and SUPP_VR_EXIST determine whether a conflicting or duplicate rule already exists; the history notes indicate the messages returned include the specification name and version, and that obsolete-status duplicates are permitted.
• Delete guards — VALIDATE_BEFORE_DELETE_INV_VRS, VALIDATE_BEFORE_DELETE_WIP_VRS, VALIDATE_BEFORE_DELETE_CST_VRS, and VALIDATE_BEFORE_DELETE_SUP_VRS prevent removal of rules still referenced by dependent data.
• Audit helper — CHECK_WHO is the routine directly associated with the user's search term "c_who." It resolves the current application user identifier (the WHO column populated in FND_USER) so that created_by, last_updated_by, and related audit columns are stamped consistently across all validity-rule rows.

Tables Accessed

The package reads and writes the five OPM validity-rule tables through APPS synonyms: GMD_MONITORING_SPEC_VRS, GMD_INVENTORY_SPEC_VRS, GMD_WIP_SPEC_VRS, GMD_CUSTOMER_SPEC_VRS, and GMD_SUPPLIER_SPEC_VRS. GMD_SPECIFICATIONS provides the parent specification header used for name and version validation. FM_FORM_MST, FM_FORM_MST_B, FM_MATL_DTL, and FM_ROUT_DTL support formula and routing associations when a recipe is supplied, and CR_RSRC_MST and CR_RSRC_DTL supply resource definitions. GMD_OPERATIONS and GMD_PARAMETERS_HDR are consulted for operation and parameter context, while FND_USER is queried by CHECK_WHO to resolve the current user.

Usage Notes

GMD_SPEC_VRS_GRP is typically invoked from the OPM Specification Validity Rules maintenance forms, from quality or recipe-related concurrent programs that must validate rule integrity before processing, and from custom extensions that create validity rules programmatically. At least one other documented package references it, confirming its role as a shared service layer. Callers should route all insert, update, and delete operations through the VALIDATE_* and VALIDATE_BEFORE_DELETE_* procedures so that null checks, foreign-key checks, existence checks, and audit stamping are applied uniformly; direct DML against the GMD_*_SPEC_VRS tables bypasses these controls and is not recommended.