Search Results wms_rule_pick_pkg1




Overview
Explore in AI Chat

Overview

WMS_RULE_PICK_PKG1 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, validated and present in both the 12.1.1 and 12.2.2 releases. It belongs to the Oracle Warehouse Management (WMS) module and supports the rules-based picking engine, which evaluates and executes picking strategies against outbound sales order and move order demand. The package is classified as OTHER in the ETRM API registry, meaning it is an internal implementation unit rather than a formally published open interface or public API.

The package operates as the execution layer beneath the rule engine. Whereas the WMS_RULE_PVT package defines the rule structures, validation logic, and attribute evaluation, WMS_RULE_PICK_PKG1 is responsible for the runtime lifecycle of a pick rule: opening the rule execution context, fetching candidate rules during evaluation, retrieving available inventory for each rule branch, and closing the execution context once rule processing completes. Because the four documented entry points are staged in an open–fetch–fetch–close pattern, the package behaves much like a controlled cursor or pl/sql-based result-set driver for the picking rule engine.

Key Procedures and Functions

Four documented procedures and functions constitute the package interface. Parameter lists are not published in the metadata and are therefore not reproduced here.

  • EXECUTE_OPEN_RULE — Initializes the rule execution context for a given picking operation. This is the entry point that prepares internal state before candidate rules are evaluated.
  • EXECUTE_FETCH_RULE — Retrieves the next applicable picking rule from the evaluated rule set, following the precedence and strategy defined in WMS rule setup. It drives iteration over candidate rules.
  • EXECUTE_FETCH_AVAILABLE_INV — Fetches inventory available for allocation under the currently active rule. This is the inventory-selection step of the picking engine and is central to producing recommendations of specific lots, subinventory locations, and LPNs.
  • EXECUTE_CLOSE_RULE — Releases the rule execution context and any related resources after rule processing or inventory fetching has completed.

Tables Accessed

The ETRM metadata for this object does not enumerate explicitly referenced tables via APPS synonyms. The documented dependency set is limited to sibling program units: WMS_RULE_PVT, the SYS STANDARD package, and the package itself (recursive reference through the package body). Inventory and rule data are therefore consumed primarily through delegated calls into WMS_RULE_PVT rather than through direct DML visible in the package metadata.

Functionally, the package operates over the WMS rule and strategy definitions, outbound demand and pick-slip data, and on-hand inventory with its locator, lot, and LPN attributes. These underlying tables are reached through the WMS_RULE_PVT layer, which supplies the rule attribute values and inventory-qualification predicates used by the fetch procedures.

Usage Notes

WMS_RULE_PICK_PKG1 is invoked indirectly rather than by user-facing code. It is referenced by WMS_RULE_PVT and by itself, and it references WMS_RULE_PVT, establishing a mutual implementation relationship between the rule engine's private package and this picking executor. Because the package is marked OTHER and has no published parameter documentation, it should not be called from custom code; attempting to do so risks breakage across patch levels and is unsupported.

In normal operation the package is driven by the picking process triggered when a sales order or move order is released for picking and the warehouse executes a rules-based picking strategy. The open–fetch–fetch–close sequence mirrors the standard cursor pattern and allows the engine to iterate rules and inventory without materializing all candidates at once. Diagnostics typically begin with WMS_RULE_PVT and the rule setup, since failures or empty results in WMS_RULE_PICK_PKG1 usually originate in rule definition, rule attribute values, or inventory availability rather than in the executor package itself.