Results for “shipment_pri_sort”

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 by WSH_PICK_SEQUENCE_RULES_PK and repeated in unique index WSH_PICK_SEQUENCE_RULES_U1.
• NAME — the user-visible rule name; governed by unique index WSH_PICK_SEQUENCE_RULES_U2, making it the natural business-key candidate.
• DESCRIPTION — free-text explanation of the rule's purpose.
• ORDER_ID_PRIORITY and ORDER_ID_SORT — priority rank and ascending/descending sort direction applied to sales order number.
• INVOICE_VALUE_PRIORITY and INVOICE_VALUE_SORT — rank and direction applied to invoice value.
• SCHEDULE_DATE_PRIORITY and SCHEDULE_DATE_SORT — rank and direction applied to the scheduled ship date.
• SHIPMENT_PRI_PRIORITY and SHIPMENT_PRI_SORT — rank and direction applied to shipment priority.
• TRIP_STOP_DATE_PRIORITY and TRIP_STOP_DATE_SORT — rank and direction applied to trip stop date.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective dating that governs when the rule is usable.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–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_PARAMETERS on the same key to find the organization-level default.
• Audit reporting on LAST_UPDATE_DATE, LAST_UPDATED_BY, and REQUEST_ID to trace configuration changes.

Related Objects

• WSH_PICKING_BATCHES — references WSH_PICK_SEQUENCE_RULES.PICK_SEQUENCE_RULE_ID; ties a batch to its sequencing rule.
• WSH_PICKING_RULES — references PICK_SEQUENCE_RULE_ID; associates picking rules with a sequence definition.
• WSH_SHIPPING_PARAMETERS — references PICK_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_DETAILS consume the rule indirectly through picking batch processing.