JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

June 27, 2026 · 12 min read

SAP EWM Picking Strategy

The Picking Strategy is the configuration object in SAP EWM that governs how the system selects storage bins during outbound warehouse order creation. It is defined at the Storage Type level in SPRO and determines the sort order in which the system searches candidate bins — whether by stock age (FIFO), expiry date (FEFO), fixed assignment, or quantity preference. Product-level overrides in the Warehouse Product Master let individual materials deviate from the Storage Type default, making the Picking Strategy a two-layer control mechanism that balances warehouse-wide rules with product-specific exceptions. This article covers strategy types, the organizational control hierarchy from Warehouse Number down to Batch, and the EWM-specific SPRO and master data fields that drive bin selection.

Part 1: Picking Strategy — Core Concepts (All Modules)#

1.1 What Is the Picking Strategy?#

A Picking Strategy is a rule set that instructs the warehouse management system which bin — among all bins holding eligible stock — to present first when fulfilling a goods issue request. Without a defined strategy, bin selection is arbitrary and can lead to aged stock accumulating, expired goods being shipped, or inefficient pick paths. The strategy translates business rules (stock rotation policy, safety stock logic, packaging preferences) into a deterministic bin-sort sequence that EWM applies automatically during warehouse order creation.

1.2 Picking Strategy Types#

The picking strategy type determines the primary sort criterion applied to candidate bins. Choosing the wrong type at blueprint time is costly: a FEFO strategy requires shelf-life data to be maintained on every batch, while Fixed Bin picking requires fixed bin assignments to exist in the Warehouse Product Master — gaps in either setup cause warehouse order creation to fail or fall back silently to less optimal bins.

Design principle: Establish the picking strategy type per Storage Type during blueprint. Changing from FIFO to FEFO after go-live requires retroactive batch SLED data backfill — a significant data migration effort.

1.3 Organizational Levels and Control Hierarchy#

The Picking Strategy operates across four organizational levels. The strategy is defined at the Storage Type level (SPRO), optionally overridden at the product level (Warehouse Product Master), and refined further by Batch characteristics when FEFO or shelf-life strategies are active. Understanding which level carries which control is essential when designing multi-temperature zone warehouses or facilities handling both fast-movers and batch-managed goods in the same storage area.

Warehouse Number (e.g., WH01)
   │
   └── Storage Type (e.g., 0001 — Rack Storage, 0010 — Bulk Floor)
          │   Defined in: SPRO → EWM → Storage Control → Define Storage Types
          │   Fields: Picking Strategy Code, Sort Sequence, Quantity Rounding
          │
          ├── Storage Section (e.g., A01 — Fast Movers, B01 — Slow Movers)
          │      Inherits Storage Type strategy; no independent override
          │
          ├── Warehouse Product (per product)
          │      Defined in: /SCWM/MAT1 → Warehousing tab
          │      Fields: Picking Strategy Override, Min. Remaining Shelf Life
          │      Overrides the Storage Type default for this product only
          │
          └── Batch (per stock unit)
                 Attributes: SLED/BBD, Batch Classification Characteristics
                 Used by FEFO / Shelf Life strategies for sort criterion value

Key design decision: In multi-Storage-Type warehouses (rack + bulk + cold storage), assign a distinct picking strategy to each Storage Type. Rely on product-level override only for exceptions — excessive product-level overrides become a maintenance burden.

1.4 Integration with Other Master Data Objects#

The Picking Strategy does not operate in isolation. It is the outbound counterpart to the Putaway Strategy and relies on several master data objects to function correctly. A misconfiguration in any of these connected objects causes the strategy to produce suboptimal bin selection or warehouse order creation errors.

Part 2: EWM-Specific Field Details#

2.0 Scope of EWM Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Strategy Configuration (Storage Type)#

The Strategy Configuration is defined entirely in SPRO under EWM → Storage Control → Define Storage Types. These settings apply warehouse-wide for all products stored in a given Storage Type unless overridden at the product level. This is the primary configuration object for Picking Strategy and must be finalized before warehouse testing begins.

2.2 Product-Level Picking Control#

The Warehouse Product Master (/SCWM/MAT1) provides a product-level picking override that takes precedence over the Storage Type strategy. This allows a single Storage Type to apply FIFO as the warehouse-wide default while specific batch-managed products use FEFO, without the cost of creating a dedicated Storage Type for each exception.

2.3 Batch Relevance Settings#

FEFO and Shelf Life picking strategies depend on accurate batch-level date data. These settings span both the Warehouse Product Master (configuration side) and the Batch Master (data side). EWM reads the batch date at warehouse order creation time — if the date is missing or incorrect, the strategy silently degrades or the warehouse order fails. Operational discipline around GR data entry is as important as the SPRO configuration.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction