In the WM scoping workshops with the key users, the Storage Section Search is often the one we deal with last. We quickly cover the Storage Type (the zone) and the Storage Bin Type (the bin dimension), but tier 2, the section, we let it drag on until Hypercare. That is a shame, because it is precisely this level that makes the strategy relevant to the business: this is where you separate the fast movers from the slow movers, the hazardous goods from the standard products.
SAP WM determines the putaway location through a cascade on three levels. The Storage Type frames the zone, the Storage Section refines the sub-zone inside the selected zone, the Storage Bin Type filters by physical capacity. This article covers tier 2: the T334B table, the Storage Section Search mechanism, and its integration in the cascade.
In this guide, I cover the role of the Storage Section in the cascade, the complete SPRO configuration (path + Storage Section Indicator + strategy screen with its 5 real columns), the activation at the Storage Type level, the assignment to the material master, a concrete end-to-end use case on the Goods Issue side, the standard SAP WM strategies, the move to SAP EWM Embedded, and an FAQ for the most frequent GSC questions.
Tier 1, the Storage Type Search, chooses the putaway zone. Tier 3, the Storage Bin Type Search, filters the bin by physical capacity. This article focuses on the central link, the one that makes the whole cascade relevant on the business side.
The role of the Storage Section in the warehouse
When the Storage Type is not enough to compartmentalize the warehouse, we divide it into subsets: the Storage Sections. A high rack zone can for example contain a fast movers section (close to the picking exit), a slow movers section (at the back of the zone), a hazardous goods section (with floor containment), a quarantine section (waiting for quality inspection).
When SAP has to place or remove a material from stock, it runs through the cascade: it starts by determining the Storage Type (the zone), then it looks for which Storage Section to run the fine search in. This is where the strategy becomes relevant to the business constraints: ABC, hazardous, perishable, turnover size.
Configuration of the strategy in SPRO
Off to the Customizing:
SPRO path:
Logistics Execution → Warehouse Management → Strategies → Activate Storage Section Search
First step: create a unique Storage Section Indicator for your specific need. This indicator must be linked to a precise warehouse and come with a short description. This is what will drive the rest, so frame it with your logistics team before touching SPRO.
Defining the search sequence
Once the indicator is created, we move on to the central screen of the strategy: the search sequence.
5 main columns structure the screen:
| Column | Role |
|---|---|
| Warehouse | Warehouse number for which the strategy is set up. |
| Storage Type | The Storage Type selected upstream by tier 1, inside which we are going to look for the section. |
| Storage Section Indicator | Indicator created in the previous step, the link with the material master. |
| Storage Class | Storage class (useful in particular for hazardous products and their segregation). |
| Water pollution | Water pollution class (environmental regulation for sensitive chemical products). |
For each line, you fill in the criteria that apply and the target Storage Section. SAP searches in the order of the sequence and keeps the first section where space is available. The cascade logic is similar to the batch determination in MM/PP, but applied at the warehouse sub-zone level.
On the product characteristics side (ABC, hazard, fragile, etc.), the join is made through the SAP classification system (CT04, CL01) on the master data side. If your site has already framed the classification, the Storage Section Search can rely on it to sort dynamically.
Activate the Storage Section Check at the Storage Type level
A critical step that is often forgotten on projects. For the Storage Section Search to trigger, it must be activated at the level of each Storage Type concerned.
SPRO path:
Logistics Execution → Warehouse Management → Master Data → Define Storage Type
This screen lets you tell SAP, for each Storage Type, whether it must look for a specific section during putaway, and whether the movement is allowed or not. You can also activate the consideration of the hazardous product criteria (Storage Class) and the water pollution, which are handled here in a cross-cutting way.
Assign the strategy to the material master
Once the strategy is configured, it must be assigned to each material concerned. The link is made in the Warehouse Management 1 view of the material master.
In the Storage strategies section, the Storage Section Indicator is to be filled in. It is used both for stock placement (putaway at goods receipt) and for stock removal (stock removal for shipping).
An important point that is often overlooked: the Storage Section Indicator always depends on the Storage Type Indicator. Always check both when you frame a material master. The Storage Type Indicator is read first (tier 1 cascade), it fixes the zone. The Storage Section Indicator comes second, inside that zone. If the Storage Type Indicator points to a zone where the Storage Section Check is not activated, your section setup does not apply.
Concrete use case: Goods Issue
This time, we take the angle of a stock removal, not a goods receipt. The Storage Section Search plays a key role in stock removal to direct the picking towards the right sub-zone.
Example material: its Storage Type Indicator points to the Storage Type INB, its Storage Section Indicator points to section 001. Here is how SAP runs the cascade in practice.
Step 1: we trigger the issue in MIGO (Goods Issue, movement 261 or 601 depending on the context).
Step 2: a Transfer Requirement (TR) is created in the background to drive the physical movement. We view the open TRs via LB10.
Step 3: we tick the TR and click TO in Foreground to see SAP’s decision in detail.
Step 4: in the Transfer Order preparation screen, SAP has run its cascade and automatically proposes:
- Selected storage type: INB (determined by tier 1)
- Selected storage section: 001 (determined by tier 2, the subject of this article)
- Available storage bin (determined by tier 3 if activated)
Step 5: we confirm and post the movement. The stock is rebalanced, the issue is recorded.
You can also check the physical bin selected via LS24 to make sure everything is consistent with your configuration. This check is useful in hypercare when a picker reports an unexpected behavior.
Placement and picking strategies in SAP WM
The Storage Section Search refines the storage zone. Once the section is selected, each Storage Type has its own placement and picking strategy. SAP delivers several standard strategies that you configure at the Storage Type level.
Stock Placement strategies (putaway)
- Fixed Bins: each material has an assigned bin.
- Open Storage: no notion of an individual bin.
- Addition to existing stock: top up an already occupied bin.
- Empty storage Bin: look for an empty bin.
- Pallets: optimized for pallets.
- Bulk Storage: mass storage, stackable pallets.
- Near Picking Bin: putaway close to the picking face.
Picking strategies (goods issue)
- FIFO: First In First Out.
- LIFO: Last In First Out.
- Partial pallet quantity: partial pallet first.
- Large/Small quantity: depending on the requested quantity.
- Expiration Date: sorting by shelf life date.
- Fixed Bin: picking from a fixed bin.
For sites with FIFO or shelf life management (typically food or pharma), the combination of Storage Section Search + Expiration Date picking strategy makes it possible to guarantee that the oldest piece goes out first, in the sub-zone defined by the section strategy. This is a case where the three tiers chain together to produce a precise and auditable business behavior.
The move to SAP EWM Embedded
SAP WM is at the end of its cycle. The official target for new projects and migrations is SAP EWM Embedded in S/4HANA. The conceptual cascade logic remains valid in EWM, but the implementation differs completely.
In EWM, the conceptual cascade remains valid but the implementation goes through a Storage Type Search Sequence mechanism, coupled with the Process-Oriented Storage Control (POSC) or the Layout-Oriented Storage Control. The notion of Storage Section still exists there as an organizational object, but the chaining of the putaway steps goes through the Warehouse Tasks and the Storage Process.
Note: for organizations that want to stay on the WM model under S/4HANA without switching to EWM, SAP offers the Stock Room Management module. It preserves the WM concepts (Storage Type, Section, Bin, tables T334B / T334P) while remaining supported under S/4HANA, useful for warehouses of moderate complexity where EWM would be oversized.
“Understanding the Storage Section Search means understanding where the warehouse manager places his business constraints. Tier 2 is the most business-oriented link of the cascade.”
FAQ: Storage Section Search SAP WM
What is the difference between Storage Type Search and Storage Section Search?
The Storage Type Search (tier 1, table T334T) chooses the putaway zone (high rack, bulk, picking shelves). The Storage Section Search (tier 2, table T334B) filters, inside the selected zone, by product characteristic (ABC, fast/slow movers, hazard). The two chain together in cascade and feed tier 3, the Storage Bin Type Search (T334P), which chooses the final physical location. Tier 1 answers “in which zone?”, tier 2 answers “in which sub-zone?”.
Where to configure the Storage Section Search in SPRO?
You activate it in the WM Customizing, via the Activate Storage Section Search entry (Strategies menu). There you first create a Storage Section Indicator for your need, then you define the sequence of candidate sections case by case with 5 columns (Warehouse, Storage Type, Storage Section Indicator, Storage Class, Water pollution). Do not forget the critical step: activate the Storage Section Check at the level of the Storage Type concerned via SPRO -> Master Data -> Define Storage Type.
What to do if my section strategy does not trigger?
Three causes cover the majority of cases in hypercare. Check in this order: (1) is the Storage Section Check activated at the level of the Storage Type selected by tier 1? (2) is the Storage Section Indicator properly filled in the Warehouse Management 1 view of the material master? (3) does the Warehouse + Storage Type + Storage Section Indicator combination really exist in the strategy sequence?
Which SAP table stores the Storage Section Search strategy?
The main table is T334B. It stores the sequence of candidate Storage Sections for each Warehouse + Storage Type + Storage Section Indicator combination. You can view it in SE16N or maintain it via SPRO. For tiers 1 and 3, the associated tables are T334T (Storage Type Search) and T334P (Storage Bin Type Search).
Can you use Storage Class and Water Pollution in the strategy?
Yes, these are two of the five columns of the Storage Section Search strategy screen. The Storage Class makes it possible to separate hazardous products (flammable, corrosive, etc.) into dedicated sections with floor containment or specific ventilation. The Water Pollution specifically handles chemical products that are sensitive to environmental regulation. This is useful on sites subject to ICPE standards in France or equivalents elsewhere in Europe.
Does Storage Section exist in SAP EWM Embedded?
Yes, the concept of Storage Section remains valid in EWM, but with a different mechanism from classic WM. The cascade translates technically into the Storage Type Search Sequence coupled with the Process-Oriented Storage Control (POSC) or Layout-Oriented. The unit of movement goes from the Transfer Order to the Warehouse Task. A WM to EWM Embedded migration is never a 1:1 mapping, it is a redesign of the putaway model.
How to link the Storage Section Search to the SAP classification?
The join is made at the material master level. If you use the classification system (characteristics CT04, classes CL01) to type your materials with ABC, hazard, or other business criteria, you can dynamically steer the Storage Section Indicator according to the characteristic values. See our guide to the classification system for the master data mechanics, and the combination with the WM strategy for the logistics side.
Conclusion: the Storage Section, the business link of the cascade
The Storage Section Search is tier 2 of the SAP WM cascade. It takes over from the Storage Type to refine the storage zone according to the business constraints: ABC, hazard, perishability, turnover. Without a correctly framed tier 2, tier 1 fixes the zone and tier 3 fixes the physical bin, but the relevance to the business stays partial.
The right reflex on a project: spend time upstream with the warehouse key users to identify the sub-zones that are really useful, frame their criteria (Storage Class if hazardous, Water Pollution if chemical, ABC for turnover), and activate the Storage Section Check on all the Storage Types concerned.
Three things to remember:
- The Storage Section Search is the business link of the cascade. Without it, tier 1 and tier 3 only cover the physical dimension.
- The activation of the Storage Section Check at the Storage Type level is the most frequent trap. Check this flag before any other debugging.
- EWM Embedded keeps the concept but with a different implementation (Storage Process + Storage Control). The migration is never a 1:1 mapping.
Keep reading
SAP WM 2 Step Picking: Optimize your order-picking processes
2-step picking cascade in SAP WM 2-step picking SAP WM: the full cascade From group creation to the dispatched delivery Step 0: Group creation VL06P (deliveries) or LT41 (transfer requirements)...
Michael A.
SAP WM storage type search: tier 1 putaway setup
On S/4HANA Supply Chain kickoffs, the end of SAP WM has become a recurring topic. And the discussion systematically drifts toward the putaway cascade. How does the Storage Type Search...
Michael A.
SAP WM storage bin type search: the complete guide (2026)
"My transfer order is going to the wrong bin, and we can't figure out why." If you work on an SAP WM project, you've definitely heard this sentence. Often during...
Michael A.
SAP EWM Master Data Integration: ERP Sync with CIF, ALE, DRF
Since the move to S/4HANA, the question "how do you synchronize data between SAP ERP and EWM" no longer has the same answer, and many projects still get it wrong...
Michael A.