Search Results wms_rule_8




Overview
Explore in AI Chat

Overview

WMS_RULE_8 is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, residing in the Warehouse Management System (WMS) module. It belongs to the WMS_RULE_* family of packages, which implement the rule engine that the warehouse management application uses to resolve item, location, and inventory attribute combinations at runtime. WMS_RULE_8 specifically encapsulates a cursor-based rule-evaluation routine, as indicated by its three documented program units: OPEN_CURS, FETCH_ONE_ROW, and CLOSE_CURS. The object is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Its API classification is OTHER, meaning it is an internal support package rather than a published, supported public API. Business functions served include supporting warehouse execution logic such as allocation, picking, putaway, and inventory attribute resolution, where the WMS rule engine must query item master and inventory location data to determine a valid rule outcome for a given transaction context.

Key Procedures and Functions

The package body exposes a small, tightly focused interface of three program units, all consistent with a server-side cursor processing pattern:

  • OPEN_CURS — Opens the cursor that drives rule evaluation. It is responsible for establishing the query context, including binding the parameters that identify the item, subinventory, locator, and rule-relevant attributes for the current evaluation. Because it is paired with FETCH_ONE_ROW and CLOSE_CURS, this unit performs the cursor open only; it does not return the full result set.
  • FETCH_ONE_ROW — Retrieves a single row from the already opened cursor. The singular naming indicates that the rule logic expects at most one matching row per invocation, matching the typical WMS rule behavior of resolving exactly one applicable rule for a transaction context. This unit applies the rule result to the calling process.
  • CLOSE_CURS — Closes the cursor opened by OPEN_CURS and releases associated resources. It completes the open-fetch-close lifecycle and is typically executed in the same session and transaction scope as the preceding two calls.

No parameter lists are documented in the available metadata; behavior is inferred from the naming convention and the package's dependency set. The package is private-facing and is not itself referenced by any other database object, which confirms its role as a leaf-level implementation package invoked directly by WMS rule processing code such as WMS_RULE_PVT.

Tables Accessed

WMS_RULE_8 reads from five inventory and item master tables through APPS synonyms:

  • MTL_SYSTEM_ITEMS — Supplies item master attributes used to qualify which rule applies to the item in context.
  • MTL_ITEM_LOCATIONS — Provides item-to-location assignments and locator attributes relevant to rule evaluation.
  • MTL_ITEM_SUB_INVENTORIES — Supplies item-to-subinventory assignments that constrain valid rule matches.
  • MTL_SECONDARY_INVENTORIES — Provides subinventory attributes, including the secondary inventories that may affect rule matching.
  • MTL_SECONDARY_LOCATORS — Provides locator-level attributes used when rules resolve to secondary locator positions.

In addition to the base tables, the package depends on WMS_PARAMETER_PVT, WMS_RULE_PVT, WMS_TRX_DETAILS_TMP_V, and on itself for internal recursion or shared private logic. WMS_PARAMETER_PVT likely supplies warehouse-level parameter values used as inputs to the rule, while WMS_TRX_DETAILS_TMP_V provides the transaction detail rows against which rules are evaluated. The dependency on WMS_RULE_PVT confirms that the public rule-evaluation layer delegates to this package.

Usage Notes

WMS_RULE_8 is an internal, non-public package. It is not referenced by any database object and should not be called directly from custom code. It is instead invoked indirectly through WMS_RULE_PVT, which the WMS user interface, mobile receiving and picking pages, and warehouse execution concurrent programs call when a rule must be resolved. Because the package is documented as VALID, it is compiled and available for the rule engine in the supported releases. Customizations should avoid modifying this package; site-specific rule logic belongs in user-defined rule packages referenced by the WMS rule engine configuration, not in APPS.WMS_RULE_8. Any diagnostic tracing of rule resolution may reference this object in the call stack, but direct dependency on it is not supported and may break on patching or upgrade.