Search Results wms_rule_1




Overview
Explore in AI Chat

Overview

WMS_RULE_1 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Within the Warehouse Management System (WMS) module, it functions as a low-level cursor utility package responsible for opening, fetching from, and closing SQL cursors that return warehouse rule and inventory-attribute data used during warehouse execution activities such as picking, put-away, and inventory querying. The package is classified as OTHER in the ETRM API classification scheme, indicating that it is an internal helper rather than a formally published public API. It is statically dependent on APPS.WMS_RULE_PVT, the private package that encapsulates the core warehouse rule evaluation logic, and on the SYS.STANDARD package that underpins all PL/SQL compilation units.

The ETRM metadata records the package object with status VALID, confirming that it is compiled and available in the database at the time of documentation. Because it exposes raw cursor operations rather than a clean business interface, WMS_RULE_1 should be regarded as an implementation detail of the warehouse rule engine rather than an entry point for integration development.

Key Procedures and Functions

The ETRM documentation lists four documented program units, all of which operate on PL/SQL cursor state:

  • OPEN_CURS — Opens the package's cursor, binding the driving query that selects the warehouse rule data set to be processed.
  • FETCH_ONE_ROW — Retrieves a single row from the opened cursor, allowing the caller to process rule or inventory records one at a time.
  • FETCH_AVAILABLE_ROWS — Retrieves the remaining available rows from the cursor, typically used when the caller needs to materialize the full result set rather than iterate row by row.
  • CLOSE_CURS — Closes the cursor and releases the associated session resources once processing is complete.

The metadata does not document parameter lists for these units, so their exact signatures must be confirmed by inspecting the package specification in the target environment. The naming and grouping of the four units indicates a traditional explicit-cursor pattern, in which the caller is responsible for the full open-fetch-close lifecycle.

Tables Accessed

The package reads from several core Oracle Inventory and Warehouse Management tables through APPS synonyms:

  • MTL_ITEM_LOCATIONS — Provides the warehouse location definition, including subinventory and locator segments used by rule evaluation.
  • MTL_SECONDARY_INVENTORIES — Supplies subinventory attributes that govern material storage and picking behaviour.
  • MTL_ONHAND_QUANTITIES_DETAIL — Holds detailed on-hand quantity records, supporting availability checks against the rule set.
  • MTL_LOT_NUMBERS — Provides lot-level identity and attribute data for lot-controlled items.
  • MTL_SERIAL_NUMBERS — Provides serial number records for serial-controlled items.
  • PLITBLM — The Oracle Forms PL/SQL table type, used internally to hold tabular data structures within the package.

No insert, update, or delete activity against these tables is documented; the package operates in a read-only capacity, assembling data for downstream consumption by the rule engine.

Usage Notes

WMS_RULE_1 is referenced by WMS_RULE_PICK_PKG1 and by itself, and it references WMS_RULE_PVT. This dependency chain places it inside the picking and rule-evaluation call stack, where it is invoked indirectly from warehouse execution flows, Oracle Forms-based WMS screens, and concurrent programs that require rule-driven inventory selection. Direct invocation from custom code is not recommended, because the absence of documented parameters and the internal nature of the package mean that its interface may change between patches or point releases. Developers who require warehouse rule functionality should route their logic through supported public APIs or through WMS_RULE_PVT, and should treat WMS_RULE_1 purely as a diagnostics and tracing target when investigating cursor-related performance or data-retrieval issues in warehouse execution.