Results for “wsh_pick_sequence_rules”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WSH.WSH_PICK_SEQUENCE_RULES is a Shipping Execution (WSH) configuration table that defines the ordering logic used to sequence pick confirmations within picking batches and picking rules. Each row represents a named pick sequence rule that determines how eligible delivery details are sorted before warehouse staff execute a pick. The table supplies the priority and sort direction for a defined set of sequencing attributes, allowing organizations to control which material is released to the floor first based on business drivers such as order urgency, invoice value, scheduled ship date, shipment priority, or trip stop date.
Because the table is referenced by foreign keys from multiple independent parents — WSH_PICKING_BATCHES, WSH_PICKING_RULES, and WSH_SHIPPING_PARAMETERS — its structure is most consistent with a hub-leaning entity in a Data Vault model. Under that heuristic classification, PICK_SEQUENCE_RULE_ID functions as a durable business key, while descriptive and audit attributes would be modeled as satellite data. This classification is a modeling suggestion derived from the foreign key topology rather than a documented Oracle construct.
Key Information Stored
The documented physical schema contains 40 columns. The most significant are:
PICK_SEQUENCE_RULE_ID— surrogate primary key, enforced byWSH_PICK_SEQUENCE_RULES_PKand repeated in unique indexWSH_PICK_SEQUENCE_RULES_U1.NAME— the user-visible rule name; governed by unique indexWSH_PICK_SEQUENCE_RULES_U2, making it the natural business-key candidate.DESCRIPTION— free-text explanation of the rule's purpose.ORDER_ID_PRIORITYandORDER_ID_SORT— priority rank and ascending/descending sort direction applied to sales order number.INVOICE_VALUE_PRIORITYandINVOICE_VALUE_SORT— rank and direction applied to invoice value.SCHEDULE_DATE_PRIORITYandSCHEDULE_DATE_SORT— rank and direction applied to the scheduled ship date.SHIPMENT_PRI_PRIORITYandSHIPMENT_PRI_SORT— rank and direction applied to shipment priority.TRIP_STOP_DATE_PRIORITYandTRIP_STOP_DATE_SORT— rank and direction applied to trip stop date.START_DATE_ACTIVEandEND_DATE_ACTIVE— effective dating that governs when the rule is usable.ATTRIBUTE_CATEGORYandATTRIBUTE1–ATTRIBUTE15— DFF/extension columns for customer-specific configuration.
Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus concurrent program columns (PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) provide auditing lineage.
Common Use Cases and Queries
Typical reporting includes listing active rules and their attribute priorities, identifying which batches or picking rules use a given sequence rule, and auditing changes to priority configuration over time.
- Active rule lookup:
SELECT pick_sequence_rule_id, name, description FROM wsh_pick_sequence_rules WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE); - Rule-to-batch usage: join
WSH_PICKING_BATCHES b ON b.pick_sequence_rule_id = r.pick_sequence_rule_id. - Rule-to-picking-rule usage: join
WSH_PICKING_RULES p ON p.pick_sequence_rule_id = r.pick_sequence_rule_id. - Default rule reference: join
WSH_SHIPPING_PARAMETERSon the same key to find the organization-level default. - Audit reporting on
LAST_UPDATE_DATE,LAST_UPDATED_BY, andREQUEST_IDto trace configuration changes.
Related Objects
WSH_PICKING_BATCHES— referencesWSH_PICK_SEQUENCE_RULES.PICK_SEQUENCE_RULE_ID; ties a batch to its sequencing rule.WSH_PICKING_RULES— referencesPICK_SEQUENCE_RULE_ID; associates picking rules with a sequence definition.WSH_SHIPPING_PARAMETERS— referencesPICK_SEQUENCE_RULE_ID; stores the default pick sequence rule at the parameter level.WSH_PICK_SEQUENCE_RULES_PK/U1/U2— primary and unique indexes enforcing key and name uniqueness.- Related WSH tables such as
WSH_DELIVERY_DETAILSconsume the rule indirectly through picking batch processing.
-
Pick Sequence Rules
-
Pick Sequence Rules
-
APPS.WSHBV_PICK_SEQUENCE_RULES·↳ WSH_PICK_SEQUENCE_RULES·Explore WSH module →
-
APPS.WSHBV_PICK_SEQUENCE_RULES·↳ WSH_PICK_SEQUENCE_RULES·Explore WSH module →
-
Full BIS Business View for Pick Sequence Rules.
APPS.WSHFV_PICK_SEQUENCE_RULES·↳ WSH_PICK_SEQUENCE_RULES·Explore WSH module →
-
Full BIS Business View for Pick Sequence Rules.
APPS.WSHFV_PICK_SEQUENCE_RULES·↳ WSH_PICK_SEQUENCE_RULES·Explore WSH module →
-
View: WSHFV_PICKING_RULES 12.2.2
Full BIS Business View for Picking Rules.
APPS.WSHFV_PICKING_RULES·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ MTL_ITEM_LOCATIONS·Explore WSH module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
View: WSHFV_PICKING_RULES 12.1.1
Full BIS Business View for Picking Rules.
APPS.WSHFV_PICKING_RULES·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ MTL_ITEM_LOCATIONS·Explore WSH module →
-
View: WSHFV_PICKING_BATCHES 12.2.2
Full BIS Business View for Picking Batches.
APPS.WSHFV_PICKING_BATCHES·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ MTL_ITEM_LOCATIONS·Explore WSH module →
-
View: WSHFV_PICKING_BATCHES 12.1.1
Full BIS Business View for Picking Batches.
APPS.WSHFV_PICKING_BATCHES·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·↳ MTL_ITEM_LOCATIONS·Explore WSH module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
View: WSH_PICKING_RULES_V 12.2.2
APPS.WSH_PICKING_RULES_V·↳ FND_PROFILE·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HR_GENERAL·Explore WSH module →
-
View: WSH_PICKING_BATCHES_V 12.2.2
/* Bug: 1924581 , HR_LOCATION changes made on 8/15/01
APPS.WSH_PICKING_BATCHES_V·↳ HR_ALL_ORGANIZATION_UNITS_TL·↳ HZ_CUST_ACCOUNTS·↳ HZ_PARTIES·Explore WSH module →