T301 table — Storage Type Master Table (WM)

One row represents one storage type defined within one warehouse number. A storage type is the organizational division of a physical warehouse - high rack area, bulk storage, fixed bin area, goods receipt zone - and every storage bin, quant, and transfer order line ultimately points back to one. T301 stores the storage type key together with the warehouse number it belongs to, plus the control indicators that govern how that storage type behaves during putaway and stock removal: whether capacity is checked, whether negative stock is tolerated, how it participates in placement and removal strategies. It is master configuration data, set up once when the warehouse is designed and touched rarely afterward, unlike LTAP or LQUA which accumulate rows continuously through daily operation.

Always restrict by MANDT and LGNUM first. The table is small - a warehouse rarely has more than a few dozen storage types configured - so a full scan for one warehouse number causes no performance concern. The risk is not performance, it is interpretation: nothing in T301 tells you how much stock, how many bins, or how much activity exists in a storage type. That information sits in LAGP and LQUA. Reading T301 answers 'does this storage type exist and how is it configured', never 'is this storage type busy'.

Symptom: transfer order creation fails to find a target storage type for a material during putaway. Select T301 by LGNUM to list every storage type configured for that warehouse, then cross-check the candidate LGTYP against LAGP filtered on the same LGNUM and LGTYP. If the storage type exists in T301 but returns zero rows in LAGP, the storage type is defined in configuration but no bins were ever created in it - the putaway strategy is pointing at an empty shelf, not a missing configuration entry.

The table structure is unchanged in S/4HANA for warehouses still run on classic embedded Warehouse Management, since it is definitional configuration and there was no functional reason to restructure it. For warehouses migrated to Extended Warehouse Management, the storage type concept is represented in EWM's own configuration structures under its own warehouse number concept, and T301 is simply not read for those warehouses at all - it remains relevant only on the classic WM side built on T300.

Configuration ownership sits with the WM or logistics execution consultant who designed the warehouse layout. Basis and security have no stake in this table's content. Any change to a storage type definition or its control indicators is a customizing change and should move through the normal transport and impact review, checked against active placement and removal strategies before activation.

The companion text table carries the storage type description by language. T300 and T320 sit above T301 in the structure, defining the warehouse number itself and its assignment to plant and storage location. Downstream operational tables LAGP, LQUA, LEIN, LTAK and LTAP consume the LGTYP values defined here, and the strategy tables keyed by LGBKZ decide how putaway and removal logic move stock across the storage types T301 defines.