JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 13 min read

Cover: SAP EWM Storage Type — the warehouse zone blueprint connecting physical layout to putaway and picking strategies

SAP EWM Storage Type

The Storage Type is the first configuration object defined in an SAP EWM warehouse — it divides the physical warehouse into functional zones (racking, floor storage, goods receipt zone, production staging, etc.) and controls how inventory moves into, within, and out of each zone. All downstream master data objects — Storage Sections, Storage Bins, Putaway and Picking Strategies, and Production Supply Areas — reference a Storage Type. Getting the Storage Type design right in Phase 1 is the most consequential structural decision in an EWM implementation.


Part 1: Storage Type — Core Concepts (All Modules)

1.1 What Is the Storage Type?

Hub-and-spoke diagram showing Storage Type at center, connected to Warehouse Number, Storage Section, Storage Bin, Putaway Strategy, Picking Strategy, and Production Supply Area

A Storage Type is a logical and physical classification of a storage area within a warehouse. It answers the question: “What kind of storage is this zone, and how does product move through it?” Each Storage Type belongs to exactly one Warehouse Number and carries its own set of movement control parameters — independently from any other Storage Type in the same warehouse.

AspectDetails
RoleClassifies a physical warehouse zone and controls all putaway, picking, and transfer movements within that zone
Modules using itEWM (primary — all warehouse execution), PP (Production Supply Area references Storage Type for production staging zones)
Transactions / ConfigSPRO: EWM → Master Data → Warehouse Structure → Define Storage Type (transaction code path); /SCWM/MBIN (Bin monitoring); /SCWM/MON (Warehouse Monitor)
Key Tables/SCWM/TLAGTYP (Storage Type definition), /SCWM/LAGTYP (Storage Type attributes), LGPLA (related bin table)
S/4HANA noteStorage Type configuration is managed exclusively in SPRO in both Embedded and Decentralized EWM. No Fiori app replaces SPRO for Storage Type definition. The data model is identical across Embedded Basic, Embedded Advanced, and Decentralized variants.

1.2 Storage Type Categories and Variants

Matrix comparing Storage Type categories: standard rack storage, floor storage, interim storage, goods receipt zone, goods issue zone, and production staging

Storage Types are differentiated by both their physical characteristic and their functional role in warehouse flow. A single warehouse typically contains four to ten Storage Types. Choosing the wrong category causes misrouted warehouse tasks and incorrect bin search results.

Storage Type CategoryTypical CodeUse CaseKey Behavior
Standard Rack Storage0001Fixed or random-bin shelving — bulk raw materials, finished goodsSupports both fixed and random bin assignment; Putaway and Picking strategies fully configurable
Floor Storage (Block Storage)0010Palletized bulk goods stored directly on floorNo bin structure required; single bin per pallet common; stack height control via EWM quant
Goods Receipt ZoneGR01Interim storage for inbound goods before putawayTypically one open bin per inbound delivery; goods moved to target Storage Type after verification
Goods Issue ZoneGI01Staging area for outbound goods before loadingShort-dwell interim type; bins often represent dock doors or staging lanes
Production Staging AreaPR01Components staged for PP/DS consumptionLinked to Production Supply Area; controlled replenishment from main storage
High-Bay / ASRSAUTOAutomated storage and retrieval systems (MFS-integrated)Requires MFS integration; Movement Types and PLC communication defined separately

Design principle: Define one Storage Type per distinct physical or operational zone. Avoid overloading a single Storage Type with incompatible movement behaviors — it makes strategy configuration impossible to maintain.


1.3 Organizational Levels and Data Hierarchy

Hierarchy tree diagram showing Warehouse Number → Storage Type → Storage Section → Storage Bin, with configuration scope annotations

Storage Type sits at the second level of the EWM warehouse structure. Every subordinate object — Section, Bin, Strategy — inherits the Storage Type as its parent reference.

Warehouse Number (e.g., WH01)
   │
   ├── Storage Type 0001 (Rack Storage)
   │      │
   │      ├── Storage Section A (Fast-mover zone)
   │      │      └── Storage Bins: A01-01-01, A01-01-02, ...
   │      │
   │      ├── Storage Section B (Slow-mover zone)
   │      │      └── Storage Bins: B01-01-01, ...
   │      │
   │      ├── Putaway Strategy (e.g., Next Empty Bin)
   │      └── Picking Strategy (e.g., FEFO)
   │
   ├── Storage Type GR01 (Goods Receipt Zone)
   │      └── Storage Section GR (single section)
   │             └── Storage Bins: GR-IN-01, GR-IN-02, ...
   │
   └── Storage Type AUTO (ASRS — MFS-integrated)
          └── Storage Section AUTO-A
                 └── Storage Bins: managed by MFS conveyor logic
Org LevelTablePrimary FieldsNotes
Warehouse Number/SCWM/TWHSWarehouse Number, Description, AddressOne warehouse per physical site; all Storage Types belong to exactly one Warehouse Number
Storage Type/SCWM/TLAGTYPStorage Type code, Description, Movement Type Group, Strategy controlsDefined in SPRO; all strategy and movement controls are set here
Storage Section/SCWM/TLBSSection code, Storage Type reference, Sort sequenceOptional subdivision of a Storage Type; used by Putaway Strategy to target sub-zones
Storage Bin/SCWM/LGPLABin ID, Storage Type, Section, coordinates, max weight/volumePhysical unit of inventory; inherits Storage Type and Section

Key design decision: Decide whether to use Storage Sections within each Storage Type before creating any Bins. Adding or changing Sections after bin creation requires a Bin migration — a high-effort SPRO and data activity in a live warehouse.


1.4 Integration with Other Master Data Objects

Hub-and-spoke showing Storage Type at center connected to Storage Section, Putaway Strategy, Picking Strategy, Production Supply Area, Storage Bin, and Warehouse Product

Storage Type is the hub from which all Phase 1 Storage Control objects radiate. It is also the reference point for Phase 2 Basic Master objects that require a physical location.

ObjectRelationshipPractical Notes
Storage Section1:N child of Storage TypeMust reference a Storage Type at creation. Sections subdivide the physical zone for strategy targeting (e.g., fast-mover vs. slow-mover aisles within a rack area).
Putaway StrategyConfigured per Storage TypeStrategy parameters (Next Empty Bin, Fixed Bin, Addition to Existing Stock) are defined independently per Storage Type. The same strategy type can behave differently in different Storage Types based on the parameter set.
Picking StrategyConfigured per Storage TypeFIFO, FEFO, LIFO, and Fixed Bin strategies are set per Storage Type. FEFO requires batch management active on the Warehouse Product.
Storage Bin1:N child of Storage Type (via Section)Every Bin belongs to a Storage Type. Bin capacity (max weight, max volume, max quantity) constraints are enforced at the Storage Type level before individual bin checks.
Production Supply Area (PSA)References Storage TypePSA defines the physical staging area in a manufacturing zone. It references the Storage Type where components are replenished and consumed — critical for PP-EWM integration.
Warehouse ProductIndirect — via Putaway/Picking strategyWarehouse Product carries the Putaway/Picking Control Indicator, which is matched against the Storage Type strategy at runtime to determine which bin to use.

Part 2: EWM-Specific Field Details

2.0 Scope of EWM Ownership

Checklist showing EWM consultant ownership across Storage Type configuration sections: basic data, movement type control, stock management, capacity check, and strategy parameters

Data SectionEWM InvolvementNotes
Basic Data◎ OwnerStorage Type code, description, and general control flags
Movement Type Group◎ OwnerControls which warehouse movement types are permitted in this zone
Stock Removal / Putaway Control◎ OwnerUnit of measure for putaway/picking, partial pallet handling rules
Capacity Check◎ OwnerMax weight, max volume, max quants per bin — enforced at runtime
Search Strategy Parameters◎ OwnerWhich Putaway and Picking strategies apply, in which sequence
Negative Stock Control◎ OwnerWhether negative stock (goods issue before goods receipt) is allowed
Interim Storage Indicator◎ OwnerMarks the Storage Type as an interim zone (GR, GI, Difference) — changes bin assignment and stock transfer behavior
Mixed Storage Control◎ OwnerWhether different materials or batches may share a bin

Legend: ◎ = Owner / Critical


2.1 Basic Data

Checklist of key Basic Data fields: Storage Type code, Description, Warehouse Number, Storage Type Indicator, and general control flags

Basic Data defines the identity and top-level classification of the Storage Type. These fields are set once at go-live and rarely changed in a production system.

FieldDescriptionPractical Usage
Storage Type (Lgtyp)Four-character alphanumeric keyNaming convention matters: use a consistent code scheme (e.g., 0001–0099 for rack types, GR01 for goods receipt, GI01 for goods issue) across the project. Code changes after bin creation are not supported without data migration.
DescriptionFree-text labelUse a concise, location-accurate description that operators recognize on RF screens — the description appears in warehouse monitor and task displays.
Warehouse NumberParent warehouse referenceAssigned at creation and immutable. One Storage Type belongs to exactly one Warehouse Number. In multi-warehouse rollouts, replicate the Storage Type configuration per Warehouse Number — there is no cross-warehouse inheritance.
Storage Type IndicatorFunctional classification flagControls how EWM interprets the zone (standard storage, interim storage, work center, etc.). Setting this incorrectly causes incorrect bin search and stock management behavior. Consult SAP note 2196438 for the complete list of supported indicator values and their behavioral impact.
Allow Negative StockNegative stock permission flagPermit goods issue from a bin before the physical goods receipt is confirmed. Required for certain decoupled inbound-outbound scenarios (e.g., cross-docking). Should be restricted to interim Storage Types only — enabling on a standard rack Storage Type is a data governance risk.

2.2 Movement Type Group

Stack layered diagram grouping movement type groups: Inbound (GR, transfer-in), Outbound (GI, transfer-out), Internal transfer, and Difference posting

The Movement Type Group defines the set of EWM warehouse movement types that are valid for this Storage Type. It is the primary control that prevents unauthorized or incorrect stock movements into or out of a zone.

FieldDescriptionPractical Usage
Movement Type GroupMovement type set keyAssign a Movement Type Group that matches the operational role of this Storage Type. For example, a GR interim zone should permit only inbound movement types; a GI zone permits only outbound. Mixing movement types in the wrong zone causes incorrect SLED/batch determination at picking.
Allowed Stock TypesStock type permissions (unrestricted, inspection, blocked)Controls which stock type quants can be stored in this Storage Type. Goods Receipt zones typically allow unrestricted and quality inspection stock. Blocked stock zones allow only blocked.
Allow Transfer Orders Without TO ReferenceCreate WT without transfer order referenceEnable only for internal replenishment Storage Types. Enabling on a standard storage zone allows uncontrolled stock movements that bypass task monitoring.
Putaway BlockPutaway blocked indicatorTemporarily block all new putaway to this Storage Type — used during physical inventory or zone reorganization. Block is removed via SPRO or warehouse monitor without requiring a transport.
Stock Removal BlockPicking blocked indicatorTemporarily block all picking from this Storage Type. Use in conjunction with physical inventory counting or during zone restructuring.

2.3 Stock Removal / Putaway Control

Comparison grid showing putaway and stock removal control combinations: full pallet putaway, partial pallet, addition to existing stock, and mixed unit handling

Putaway and Stock Removal Control parameters determine how the system handles unit-of-measure transitions, partial pallets, and bin sharing at the point of movement execution.

FieldDescriptionPractical Usage
Unit of Measure for PutawayUoM used when placing stock into binsTypically Base Unit (EA, KG) or a warehouse-specific pallet unit. For high-bay storage, set to PAL to enforce full-pallet-only putaway — prevents partial pallet handling in automated racking.
Unit of Measure for Stock RemovalUoM used when removing stock from binsShould match the picking unit specified in Warehouse Product. Mismatches cause UoM conversion errors at task confirmation and require SPRO-level correction.
Putaway Quantity CheckEnforce maximum putaway quantityWhen active, the system rejects putaway tasks that would exceed the bin’s maximum quantity for the defined UoM. Activate for zone where capacity discipline is critical (e.g., freezer storage, hazmat).
Addition to Existing StockAllow adding to a partially filled binWhen enabled, the putaway strategy may direct stock to a bin that already contains the same material. Disable for storage zones where each bin must hold a single delivery unit (e.g., high-value serialized goods).
Mixed Batch StorageAllow multiple batches per binEnable only when mixing batches in one bin is operationally acceptable. For FEFO-controlled storage (food, pharma), mixed batch storage prevents accurate FEFO determination — always disable in such zones.
Two-Step PickingEnable two-step (wave) pickingWhen enabled, a staging step is introduced between bin removal and goods issue. Required for wave-based outbound processes in conjunction with the Wave Template. Impacts task type configuration.

2.4 Capacity Check

Checklist of capacity check fields: max weight, max volume, max number of quants, capacity utilization method, and check activation flag

Capacity Check settings define the physical constraints of bins in this Storage Type and control when the system rejects a putaway because a target bin would be overloaded.

FieldDescriptionPractical Usage
Activate Capacity CheckMaster switch for capacity enforcementWhen off, no capacity constraint is evaluated at putaway — bins can receive unlimited stock regardless of weight/volume. Activate for storage zones with structural or equipment constraints (racking load limits, refrigerated zone).
Max Weight per BinMaximum allowable weight in kgDerived from the racking specification or floor load limit. Coordinate with facility management during design. The value here is the default for all bins in this Storage Type — individual bins can override in /SCWM/LS01.
Max Volume per BinMaximum allowable volume in m³Set for zone where volume (not weight) is the binding constraint — e.g., a dry goods zone with high-density small items.
Max Number of QuantsMaximum distinct stock lines per binA quant represents one unique combination of material + batch + stock type + owner. Limiting quants per bin controls search time at picking. For rack storage, 1–3 quants per bin is a common design target; unlimited quants are typical only for floor storage.
Capacity Utilization MethodHow remaining capacity is calculatedMethod 1: check only weight; Method 2: check weight and volume; Method 3: check weight, volume, and quant count. Choose based on which constraint is binding for the zone.

2.5 Search Strategy Parameters

Hierarchy tree diagram showing Storage Type strategy assignment: Putaway Strategy sequence, Picking Strategy sequence, and fallback behavior

Search Strategy Parameters link the Storage Type to the Putaway and Picking Strategy objects defined in Phase 1. They control the sequence in which strategies are evaluated at runtime.

FieldDescriptionPractical Usage
Putaway StrategyPrimary putaway strategy codeReferences a Putaway Strategy object (EWM-A03-03). The strategy determines which bin the system proposes when a warehouse task is created for goods receipt into this Storage Type. Common choices: P1 (Next Empty Bin), P2 (Fixed Bin), P3 (Addition to Existing Stock), P4 (Open Storage).
Picking StrategyPrimary picking strategy codeReferences a Picking Strategy object (EWM-A03-04). FEFO (First Expired First Out), FIFO (First In First Out), LIFO, and Fixed Bin are the standard options. FEFO requires batch management and SLED (Shelf Life Expiration Date) data active on the Warehouse Product.
Strategy SequenceFallback strategy orderWhen the primary strategy finds no valid bin, EWM evaluates the next strategy in the sequence. Define a fallback (e.g., Next Empty Bin as fallback after Fixed Bin) to avoid task creation failures during exceptions.
Putaway Control IndicatorFilters applicable Putaway ControlMatches the Putaway Control Indicator on the Warehouse Product. Only Warehouse Products with a matching indicator are subject to the Storage Type’s primary putaway strategy — others fall through to the fallback. Design the control indicator scheme in conjunction with Warehouse Product master data design.
Stock Removal Control IndicatorFilters applicable Picking ControlSame principle as Putaway Control Indicator but for the picking strategy. Misalignment between the Storage Type indicator and the Warehouse Product indicator is the most common root cause of “no bin found” errors at picking task creation.

L1) Big Picture

IDCategoryTitle
ewm-001OverviewWhat is SAP EWM?

L2-A) Master Data

IDCategoryTitle
ewm-a01OverviewSAP EWM Master Data: Overview, Hierarchy & Relationships
ewm-a02-01Master DataSAP EWM Material Master
ewm-a03-01Master DataSAP EWM Storage Type 📍
ewm-a03-02Master DataSAP EWM Storage Section
ewm-a03-03Master DataSAP EWM Putaway Strategy
ewm-a03-04Master DataSAP EWM Picking Strategy
ewm-a04-02Master DataSAP EWM Storage Bin
ewm-a04-03Master DataSAP EWM Fixed Storage Bin
ewm-a04-04Master DataSAP EWM Production Supply Area
ewm-a04-05Master DataSAP EWM Packaging Specification
ewm-a04-06Master DataSAP EWM User
ewm-a05-01Master DataSAP EWM Wave Template
ewm-a06-01Master DataSAP EWM Resource
ewm-a07-01Master DataSAP EWM Inspection Type
ewm-a08-01Master DataSAP EWM Batch Master
ewm-a08-02Master DataSAP EWM Batch Characteristics
ewm-a09-01Master DataSAP EWM RF Environment
ewm-a09-02Master DataSAP EWM RF Logical Transaction
ewm-a09-03Master DataSAP EWM RF Menu
ewm-a09-04Master DataSAP EWM RF Profile
ewm-a09-05Master DataSAP EWM RF Queue
ewm-a09-06Master DataSAP EWM RF Presentation Device
ewm-a10-01Master DataSAP EWM PLC
ewm-a10-02Master DataSAP EWM Communication Point

L2-B) Transaction

IDCategoryTitle
ewm-b01OverviewSAP EWM Transactions: Process Flow, Hierarchy & Relationships