LEIN table — Storage Unit Header Table in Classic WM

Each row in LEIN represents one storage unit in classic WM: a physical handling unit such as a pallet, container or tote that has been placed into a warehouse and given a storage unit number (LENUM). The row records where that unit currently sits, expressed as warehouse number, storage type and storage bin. LEIN is a pure location and identity record for the unit itself. It does not carry the material, batch or quantity inside the unit; that detail sits in the quant table, which references the storage unit number. A storage unit can hold multiple quants if it is mixed, so LEIN and the quant table are in a one-to-many relationship. Storage units are created, moved and dissolved through transfer order processing, and LEIN is updated at confirmation, not at creation of the transfer order request.

Always restrict on MANDT and LGNUM first; a shared client with several warehouse numbers turns a bin-level query into a full table scan otherwise. LENUM is the most selective field when a specific unit is under investigation and should be used directly if known rather than derived through bin or type filters. Do not attempt to select on LGPLA alone across the whole client; bin codes repeat across storage types and warehouse numbers, so a bin-only filter returns unrelated units in other warehouses. If tracing a business complaint about a missing pallet, start from the storage unit number if the user has it, and only fall back to storage type and bin range when the number is unknown.

Symptom: a warehouse operator reports that a storage unit shown as available in the interleaving screen cannot be found in the bin. Take the storage unit number from the complaint and select LEIN on MANDT, LGNUM, LENUM. Compare the LGTYP and LGPLA returned against the physical location searched. If LEIN shows a different bin, the physical move happened without a confirmed transfer order, so the next step is LTAP filtered on that LENUM to find the last movement and its confirmation status, not a correction directly on LEIN.

LEIN remains part of the classic Warehouse Management data model on S/4HANA for customers who continue to run decentralized or classic WM rather than migrating to embedded EWM. It has not been replaced by a compatibility view in the way some MM or SD tables have, because classic WM itself continues to operate on its original table structure where it is still active. Where a warehouse has been converted to embedded EWM, storage unit data moves to the EWM storage unit model entirely and LEIN is no longer the relevant table for that warehouse number.

Warehouse operations or logistics execution consultants own questions about what LEIN shows, since it reflects transfer order confirmation results rather than a standalone master data set. Basis or data teams should not be asked to correct LEIN directly; any correction has to run through a WM transaction that also updates the quant and bin occupancy records consistently.

LTAK and LTAP are the transfer order header and item tables that create and move the storage units recorded in LEIN, written by transfer order creation and confirmation transactions. LQUA holds the quantity and material detail inside each storage unit. LAGP is the storage bin master that LEIN's location fields resolve against. T300, T301 and T320 hold the warehouse, storage type and organizational assignment configuration that LEIN's keys depend on.