Search Results validate_quantities




Overview

APPS.WMS_PICKING_PKG is the core PL/SQL package body that underpins the Oracle Warehouse Management (WMS) picking engine in Oracle E-Business Suite 12.1.1 and 12.2.2. It encapsulates the business logic that drives task-level picking, including task retrieval, task sequencing, quantity validation, lot and serial number handling, and the splitting of pick tasks across material transaction, lot/serial, and LPN dimensions. The package operates against the WMS-driven picking model in which warehouse operators are directed to specific items, quantities, LPNs, and locations, and it coordinates the corresponding material transaction records that ultimately feed into inventory and order management. It is also responsible for cartonization and consolidation routines tied to LPN (license plate number) management.

The package is registered in ETRM with an API classification of OTHER, meaning it is not a published open interface but is widely consumed internally by WMS mobile and desktop flows. It is referenced by four other packages, reflecting its central role in the picking subsystem. The body retains internal state through global variables such as group sequence numbers, cartonization ID arrays, order number collections, and pick slip number collections, which are used to manage cluster picking and case picking scenarios.

Key Procedures and Functions

ETRM documents 24 procedures and functions. The primary ones relevant to picking task lifecycle and validation include:

Tables Accessed

The package reads and writes a focused set of inventory, WMS, and manufacturing tables via APPS synonyms:

Usage Notes

WMS_PICKING_PKG is invoked primarily from the WMS mobile picking UI (including RF and tablet flows) and from pick-confirm and task-execution forms. It is also called by the four dependent packages noted in ETRM and by custom extensions that need to validate pick quantities or split tasks programmatically. Because VALIDATE_QUANTITIES enforces quantity and UOM consistency, custom mobile or integration code that bypasses WMS UI should call it before committing a pick transaction to avoid inventory and order discrepancies. The debug tracing controlled by INV_DEBUG_TRACE (levels 0–2) is useful when diagnosing validation failures or task split behavior in production support scenarios involving 12.1.1 and 12.2.2 environments.