Results for “task_priority”

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

Overview

WSH_PICKING_RULES is the Shipping Execution (WSH) master table that defines the configurable picking rules used by Oracle EBS Warehouse Management and Shipping to control how material is selected, grouped, sequenced, and confirmed during outbound picking. Each row represents one named picking rule that the application evaluates when it generates pick waves, releases move orders, or auto-creates deliveries. The rule can be scoped by order type, customer, ship-to location, ship method, carrier, subinventory, locator, item, zone, and date range, allowing a single table to drive highly granular picking behavior for the enterprise.

Within the Shipping Execution model, WSH_PICKING_RULES acts as the central policy definition referenced by pick release, pick confirm, task planning, and delivery creation logic. The ETRM metadata's heuristic Data Vault classification is link, which suggests the table is best modeled as a relationship entity connecting order, inventory, and shipping attributes rather than as a pure reference hub.

Key Information Stored

The surrogate primary key is PICKING_RULE_ID, enforced by the WSH_PICKING_RULES_PK constraint. Two unique indexes exist: WSH_PICKING_RULES_U1 on PICKING_RULE_ID and WSH_PICKING_RULES_U2 on NAME, making NAME the documented business-key candidate that users recognize when selecting a rule in the shipping UI.

• NAME – human-readable rule identifier (unique).
• ORDER_TYPE_ID – restricts the rule to an order type (FK to SO_ORDER_TYPES_115_ALL).
• CUSTOMER_ID, SHIP_TO_LOCATION_ID, SHIP_METHOD_CODE, CARRIER_ID – shipping and customer scoping attributes.
• ORGANIZATION_ID – inventory organization the rule applies to.
• PICK_FROM_SUBINVENTORY, PICK_FROM_LOCATOR_ID, SUBINVENTORY – controls the source inventory location for picking.
• DEFAULT_STAGE_SUBINVENTORY, DEFAULT_STAGE_LOCATOR_ID – target staging location.
• PICK_GROUPING_RULE_ID – FK to WSH_PICK_GROUPING_RULES, defines grouping behavior.
• PICK_SEQUENCE_RULE_ID – FK to WSH_PICK_SEQUENCE_RULES, defines pick ordering.
• SHIP_CONFIRM_RULE_ID – FK to WSH_SHIP_CONFIRM_RULES, the ship-confirm policy.
• ZONE_ID – FK to WMS_ZONES_B, restricting picking to a zone.
• AUTO_PICK_CONFIRM_FLAG, AUTOCREATE_DELIVERY_FLAG, AUTOPACK_FLAG, PARTIAL_ALLOWED_FLAG, BACKORDERS_ONLY_FLAG – behavioral switches governing automation.
• START_DATE_ACTIVE / END_DATE_ACTIVE – effective dating for the rule.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY – standard audit columns plus 15 ATTRIBUTE flexfields.

Common Use Cases and Queries

The most frequent reporting need is to resolve a picking_rule_id returned by pick release or move-order interfaces back to a meaningful rule name and its scoping attributes.

Look up a rule by its primary key:

• SELECT picking_rule_id, name, organization_id, auto_pick_confirm_flag, autocreate_delivery_flag FROM wsh_picking_rules WHERE picking_rule_id = :p_rule_id;

Find active rules per organization:

• SELECT p.picking_rule_id, p.name, g.name grouping_rule, s.name sequence_rule FROM wsh_picking_rules p, wsh_pick_grouping_rules g, wsh_pick_sequence_rules s WHERE p.pick_grouping_rule_id = g.pick_grouping_rule_id AND p.pick_sequence_rule_id = s.pick_sequence_rule_id AND p.organization_id = :org_id AND SYSDATE BETWEEN p.start_date_active AND NVL(p.end_date_active, SYSDATE+1);

Typical scenarios include auditing which automation flags are enabled across rules, tracing pick-release performance by grouping/sequence rule, validating effective-date gaps, and reviewing ship-confirm assignments via WSH_SHIP_CONFIRM_RULES.

Related Objects

• WSH_PICK_GROUPING_RULES – joined via PICK_GROUPING_RULE_ID; controls how picks are consolidated.
• WSH_PICK_SEQUENCE_RULES – joined via PICK_SEQUENCE_RULE_ID; defines pick path ordering.
• WSH_SHIP_CONFIRM_RULES – joined via SHIP_CONFIRM_RULE_ID; governs ship-confirm behavior.
• SO_ORDER_TYPES_115_ALL – joined via ORDER_TYPE_ID; supplies order-type context.
• WMS_ZONES_B – joined via ZONE_ID; defines zone-level picking restrictions.
• WSH_DELIVERY_ASSIGNMENT_RULES / WSH_TRIP_STOPS – downstream consumers of picking/delivery automation flags.
• Pick Release and Pick Confirm concurrent programs – the primary runtime consumers that read this table to drive picking logic.