Search Results wsh_pick_sequence_rules




Overview
Explore in AI Chat

Overview

The WSH_PICK_SEQUENCE_RULES table is a core data object within the Oracle E-Business Suite Shipping Execution (WSH) module. It serves as the master repository for defining the rules that govern the order in which delivery lines are sequenced and organized during the picking process. These rules are critical for warehouse operational efficiency, enabling businesses to configure picking strategies that optimize travel paths, batch similar items, or adhere to specific customer or carrier requirements. The table's primary role is to store the rule definitions that are subsequently assigned to picking batches or picking rules, thereby controlling the physical flow of goods from the warehouse floor.

Key Information Stored

The table's structure centers on a unique identifier for each rule definition. The primary key column, PICK_SEQUENCE_RULE_ID, is the essential field that uniquely identifies each sequencing rule record. While the provided ETRM metadata does not list all columns, the existence of foreign key relationships indicates this table stores the rule metadata that other transactional tables reference. Typical columns in such a configuration table would include fields for the rule name, description, effective dates, sequencing criteria (e.g., by item, location, delivery priority), and the associated organization. The PICK_SEQUENCE_RULE_ID is the critical link used by dependent transactional entities.

Common Use Cases and Queries

The primary use case is the creation and management of picking sequence strategies within the Shipping Execution setup. Administrators define rules here which are then applied during the creation of picking batches or picking rules. Common reporting and validation queries involve joining this table to its dependent transactional tables. A fundamental query retrieves all defined rules: SELECT PICK_SEQUENCE_RULE_ID, <other descriptive columns> FROM WSH.WSH_PICK_SEQUENCE_RULES WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE). Another critical query identifies which picking batches utilize a specific rule by joining to WSH_PICKING_BATCHES: SELECT BATCH_NAME, BATCH_ID FROM WSH.WSH_PICKING_BATCHES PB, WSH.WSH_PICK_SEQUENCE_RULES PSR WHERE PB.PICK_SEQUENCE_RULE_ID = PSR.PICK_SEQUENCE_RULE_ID AND PSR.PICK_SEQUENCE_RULE_ID = :RULE_ID.

Related Objects

As documented in the ETRM metadata, the WSH_PICK_SEQUENCE_RULES table has direct foreign key relationships with two primary transactional tables. First, the WSH_PICKING_BATCHES table references it via its PICK_SEQUENCE_RULE_ID column, linking a specific picking batch to the sequencing rule it should follow. Second, the WSH_PICKING_RULES table also references it via the same column, allowing picking rules to inherit a predefined sequencing strategy. This establishes WSH_PICK_SEQUENCE_RULES as a parent configuration table for these key operational entities. Other related objects would likely include associated views and the Oracle Forms or APIs used to maintain the table's data within the EBS user interface.