Results for “wsh_pick_grouping_rules”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSH_PICK_GROUPING_RULES is a Shipping Execution (WSH) configuration table that stores user-defined pick release grouping rules. In Oracle EBS 12.1.1 and 12.2.2, these rules determine how the Pick Release process consolidates eligible sales order lines into picking batches and, ultimately, into move orders and pick slips. A grouping rule governs which order attributes — such as order number, subinventory, customer, ship-to location, carrier, shipment priority, trip stop, or delivery — must match before lines can be grouped into the same pick wave.

The table is owned by the WSH schema and is classified as VALID in the ETRM metadata. It contains 54 documented columns. The primary key is WSH_PICK_GROUPING_RULES_PK, defined on PICK_GROUPING_RULE_ID. Two unique indexes, WSH_PICK_GROUPING_RULES_U1 and WSH_PICK_GROUPING_RULES_U2, reinforce the surrogate key and enforce a business-key candidate on NAME (in combination with ZD_EDITION_NAME for editioning support in 12.2.2).

From a Data Vault modeling perspective, the heuristic classification is hub-leaning: the table behaves as a central reference or hub for grouping rule identities, with satellites such as WSH_PICKING_BATCHES and WSH_PICKING_RULES referencing it rather than being referenced by it.

Key Information Stored

The most significant columns capture the rule identity, its life-cycle, and the attribute-level grouping flags:

Common Use Cases and Queries

Shipping administrators define grouping rules to reduce pick-slip count, consolidate deliveries, or enforce carrier separation. A common query lists active rules and their grouping flags:

SELECT pick_grouping_rule_id, name, description,
       order_number_flag, customer_flag, carrier_flag
  FROM wsh.wsh_pick_grouping_rules
 WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE-1)
                          AND NVL(end_date_active, SYSDATE+1);

Reporting use cases include auditing which rules are assigned to picking batches, tracing how order lines were grouped, and identifying dormant or duplicated rules. A join to WSH_PICKING_BATCHES demonstrates rule utilization:

SELECT b.batch_id, b.pick_grouping_rule_id, r.name
  FROM wsh.wsh_picking_batches b, wsh.wsh_pick_grouping_rules r
 WHERE b.pick_grouping_rule_id = r.pick_grouping_rule_id;

Related Objects

The following objects reference WSH_PICK_GROUPING_RULES via foreign keys:

  • WSH_PICKING_BATCHES — joins on PICK_GROUPING_RULE_ID; identifies the rule governing each picking batch.
  • WSH_PICKING_RULES — joins on PICK_GROUPING_RULE_ID; ties picking rule definitions to grouping rules.
  • WSH_SHIPPING_PARAMETERS — joins on PICK_GROUPING_RULE_ID; holds the default grouping rule at the shipping parameter level.

These relationships establish WSH_PICK_GROUPING_RULES as a hub-like reference object within the WSH pick-release configuration model. Administrators should query it alongside WSH_PICKING_BATCHES and WSH_SHIPPING_PARAMETERS to fully trace how grouping behavior is applied at runtime.