Search Results wsh_picking_rules_pk

Overview

The WSH_PICKING_RULES table is a core data object within the Oracle E-Business Suite Shipping Execution (WSH) module. It functions as the master repository for defining picking rules, which are critical business logic components that govern how inventory is selected and allocated for shipment during the order fulfillment process. These rules determine the sequence in which order lines are picked and how they are grouped together into discrete picking tasks or waves, directly impacting warehouse operational efficiency. The table's primary role is to store the configuration of these rules, which are then referenced by the shipping engine when releasing sales orders or other demand sources to the warehouse for picking.

Key Information Stored

The table's central identifier is the PICKING_RULE_ID, which serves as the primary key. The most critical data points stored are the foreign keys that link a specific picking rule to its constituent logic components. As per the provided metadata, these are the PICK_GROUPING_RULE_ID and the PICK_SEQUENCE_RULE_ID. The PICK_GROUPING_RULE_ID references a rule that defines how order lines should be consolidated (e.g., by order, by ship-to location, by carrier), while the PICK_SEQUENCE_RULE_ID references a rule that defines the physical sequence for picking (e.g., by item, location, or route). The table likely contains additional descriptive and control columns such as a NAME, DESCRIPTION, ENABLED_FLAG, and CREATION_DATE, which are standard for configuration entities in Oracle EBS.

Common Use Cases and Queries

The primary use case is the setup and maintenance of picking strategies within the Shipping Execution module. Administrators define rules in this table to automate and standardize warehouse operations. For reporting and troubleshooting, common queries involve joining this table to its referenced rule tables to understand the full composition of a picking rule. A typical SQL pattern would retrieve all active picking rules with their associated grouping and sequencing logic:

• SELECT pr.picking_rule_id, pr.name, pgr.name as grouping_rule, psr.name as sequence_rule FROM wsh_picking_rules pr, wsh_pick_grouping_rules pgr, wsh_pick_sequence_rules psr WHERE pr.pick_grouping_rule_id = pgr.pick_grouping_rule_id AND pr.pick_sequence_rule_id = psr.pick_sequence_rule_id AND pr.enabled_flag = 'Y';

Another critical use case is diagnosing issues with pick release, where a developer might trace the PICKING_RULE_ID assigned to a sales order line or delivery detail back to its definition in this table.

Related Objects

The WSH_PICKING_RULES table has defined foreign key relationships with two other configuration tables, as documented in the ETRM metadata. These relationships are fundamental to its purpose:

• WSH_PICK_GROUPING_RULES: Linked via WSH_PICKING_RULES.PICK_GROUPING_RULE_ID. This table stores the definitions for how picks are grouped or batched.
• WSH_PICK_SEQUENCE_RULES: Linked via WSH_PICKING_RULES.PICK_SEQUENCE_RULE_ID. This table stores the definitions for the physical pick walk sequence.

Furthermore, the PICKING_RULE_ID from this table is referenced by various transactional entities in shipping, such as delivery details (WSH_DELIVERY_DETAILS) or pick slips, to record which rule was applied during the release process. The primary key constraint WSH_PICKING_RULES_PK ensures the uniqueness of each rule definition.