T300 table — Warehouse Number Definition Table

One row in T300 represents a single warehouse number, the top-level organizational unit of classic Warehouse Management. A warehouse number is a logical container that groups storage types, storage bins, and the transfer order and quant activity that happen inside a physical or virtual warehouse. T300 holds the warehouse number key itself and a small set of header-level control settings that apply across the whole warehouse, such as whether RF processing is active or how the warehouse behaves for certain global options. It does not hold storage type rules, bin capacities, or movement type control; those sit one or two levels down in tables keyed by LGNUM but owned by different config objects. T300 is deliberately thin: it exists to give every other WM table a valid key to point at.

T300 is tiny, typically a few dozen to a few hundred rows even in a large landscape, so selectivity is never the issue. Always filter by client first, then by LGNUM if a specific warehouse is in question; there is rarely a reason to read the whole table. The work in practice is never inside T300 itself but in the outward join: pull the warehouse number here, confirm the header settings, then chase the actual behavior into T301, T320, or the movement tables. Treat a T300 lookup as a five-second sanity check, not the destination of the investigation.

Symptom: RF users on warehouse number 100 report that mobile transactions are unavailable while desktop transfer orders work fine. Select T300 where LGNUM equals 100 and check the RF activation indicator. If it is switched off, the warehouse number was simply never enabled for RF and the fix is a configuration change, not a user authorization or device issue. This single-row lookup rules out an entire category of investigation in one query.

T300 continues to exist unchanged in S/4HANA for landscapes still running classic Warehouse Management, and the table structure has not been restructured into a CDS-only replacement. Where embedded EWM is in use, the classic WM warehouse number concept in T300 is separate from the EWM warehouse number and its own configuration objects; the two are not interchangeable and a warehouse number that exists in T300 has no automatic counterpart in EWM. New implementations on S/4HANA are steered toward EWM, so T300 is increasingly a migration-era or legacy-warehouse artifact rather than the primary configuration path.

The WM or EWM functional consultant owns warehouse number definition and any change to T300 header settings, since these are IMG-driven configuration entries, not master data maintained by warehouse staff. Basis is only involved if a client-dependent transport of the configuration is required. Any question about why a warehouse number behaves a certain way at the header level starts with the functional consultant who built the warehouse structuring, not with the operations team running transactions inside it.

T320 assigns plants and storage locations to the warehouse number defined here and is the table to check immediately after T300 when a goods movement fails to find its warehouse. T301 carries the storage type definitions that live inside a T300 warehouse number. LAGP, LQUA, and LEIN hold the bins, quants, and storage units created within that structure, and LTAK and LTAP hold the transfer order header and item records that move stock through it. All of these are maintained through the standard WM configuration and transaction set, not by editing T300 directly.