Search Results p_rule_id

Overview

APPS.WMS_RULE_PUT_PKG1 is a Warehouse Management System (WMS) package body that serves as a dispatching layer for putaway rule evaluation in Oracle E-Business Suite. In the Oracle Warehouse Management module, putaway rules determine the destination subinventory and locator where received or manufactured inventory should be placed, based on user-defined rule criteria. Oracle EBS ships a family of seeded rule packages, each implementing a distinct algorithm (for example, rules that put away by item, by project, by lot, or by locator capacity constraints). WMS_RULE_PUT_PKG1 acts as a router that inspects the rule identifier passed by the caller and delegates execution to the appropriate rule-specific package.

The package is classified in the ETRM repository under the APPS schema with an API classification of OTHER. It exposes three documented entry points that mirror the classic cursor lifecycle: opening the rule cursor, fetching rows from it, and closing it. This separation allows the calling inventory or putaway engine to iterate over candidate destinations without materializing the entire result set at once, which is important when large numbers of locators or items are eligible.

Key Procedures and Functions

• EXECUTE_OPEN_RULE — Opens the putaway rule cursor. Based on the rule identifier supplied by the caller, it invokes the corresponding rule-specific implementation (such as WMS_RULE_7, WMS_RULE_8, WMS_RULE_9, WMS_RULE_10, or WMS_RULE_11) and returns a status result indicating success or failure. Contextual inputs describing the item, organization, transaction type, subinventory, locator, and project/task are passed through to the underlying rule so that the rule can filter candidate destinations correctly.
• EXECUTE_FETCH_RULE — Retrieves the next row from the previously opened cursor. The caller repeatedly invokes this procedure to walk through the ranked list of candidate putaway destinations until the cursor is exhausted.
• EXECUTE_CLOSE_RULE — Releases the cursor once putaway selection is complete, ensuring that session resources associated with the open cursor are freed.

The ETRM documentation lists these three procedures as the complete documented interface; the internal rule-specific packages are not exposed directly to callers of this dispatcher.

Tables Accessed

The supplied metadata does not enumerate the base tables accessed through APPS synonyms, and no table list is published for this package. By design, the package itself is a thin dispatch layer and performs little or no direct SQL; the underlying rule packages (WMS_RULE_7 through WMS_RULE_11 and their peers) are responsible for querying the WMS and inventory tables that hold item-subinventory-locator restrictions, locator capacity, and putaway rule definitions. Consumers should therefore treat the table footprint as inherited from the invoked rule rather than from this package body.

Usage Notes

WMS_RULE_PUT_PKG1 is not end-user facing. It is invoked from within the WMS putaway processing flow, typically triggered when the receiving or inventory transaction engine asks the system to suggest a destination locator. The open, fetch, and close triad aligns with a programmatic cursor loop: open once, fetch repeatedly until no rows remain, then close. Because the ETRM repository records that this package is referenced by one other package, callers should not reference it directly in custom extensions unless they replicate the identical cursor lifecycle; substituting a different call sequence can leave cursors open and consume session resources.

The term "open_curs" that led to this object corresponds to the EXECUTE_OPEN_RULE procedure, which is the documented entry point that opens the putaway cursor and hands control to the rule-specific package selected by the rule identifier. Customizations should extend rule coverage by creating or modifying rule-specific packages rather than altering the dispatcher, preserving upgrade safety across 12.1.1 and 12.2.2.