Search Results check_uom

Overview

APPS.GMD_OPERATION_RESOURCES_PUB is a public PL/SQL package in Oracle EBS Process Manufacturing (OPM) that provides the programmatic interface for maintaining operation resources in a process routings and recipes context. Its body, delivered as GMDPOPRB.pls, encapsulates the business logic required to create, modify, and delete the resource assignments that describe what equipment, labor, or other resources are consumed at a given operation step. The package is classified as PUB, meaning it is a supported public API intended for external callers, not merely an internal implementation artifact. It sits within the OPM routing and operations module and is referenced by four other packages, confirming its role as a dependency point for higher-level recipe and routing logic. The header history shows continuous hardening across releases: initial creation in 2002 by Sandra Dulyk, a rewrite in late 2002 (Bug 2679110) to standardize error handling and expand validations, removal of a redundant FND_PROFILE debug check in 2004, cursor cleanup before exception propagation in 2006 (Bug 5172254), and the significant column migration in 2008 (Bug 7118558) replacing um_code with uom_code and the legacy sy_uoms_mst table with mtl_units_of_measure.

Key Procedures and Functions

The package body exposes three documented public procedures, all operating on operation resource records:

• INSERT_OPERATION_RESOURCES — Creates new resource assignments for an operation activity, applying the package's internal validation cursors before committing the record.
• UPDATE_OPERATION_RESOURCES — Modifies attributes of an existing operation resource record, re-running the same validations to ensure referential and master-data integrity.
• DELETE_OPERATION_RESOURCES — Removes an operation resource assignment, subject to the same consistency checks.

Although not public, the private cursor check_uom is central to the user's query. Defined as CURSOR check_uom(v_uom VARCHAR2), it selects from mtl_units_of_measure where uom_code matches the input and disable_date is null or in the future. This enforces that the unit of measure supplied to the three public procedures is both valid and currently enabled. It works alongside sibling cursors such as check_oprn_line_id (against gmd_operation_activities) and check cursors against cost component class and cost analysis code. Bug 5172254 established the convention of closing these cursors before raising validation exceptions to avoid leaking open handles.

Tables Accessed

The package reads and writes through APPS synonyms. Core transactional tables are GMD_OPERATION_RESOURCES (the target of insert, update, and delete) and GMD_OPERATION_ACTIVITIES (validating the parent operation line). Master and reference data are validated against MTL_UNITS_OF_MEASURE (the relocated UOM master, via check_uom), CM_CMPT_MST (cost component classes), CM_ALYS_MST (cost analysis codes), GMD_OPERATIONS, CR_RSRC_MST and FM_ACTV_MST (resource and activity masters). PLITBLM is a standard OPM error/logging table used to record validation failures. The 2008 migration from sy_uoms_mst means any legacy customization referencing the old column or table will fail on current code lines.

Usage Notes

These procedures are typically invoked from the OPM operation and resource maintenance forms, from concurrent programs that bulk-load routing resources, and from custom PL/SQL that programmatically builds recipes or routings. Callers must supply a valid, enabled UOM to pass check_uom; otherwise the call fails with a validation error. Because the package raises and logs errors rather than silently defaulting, callers should wrap invocations in exception handlers and inspect the OPM error stack. On 12.1.1 and 12.2.2, invoke via the APPS synonym, never against the base schema, and avoid direct DML on GMD_OPERATION_RESOURCES to preserve the validations enforced here.