LS24 — Display Warehouse Stock of Material (WM)
LS24 is a classic WM display transaction that lists the quants of a given material across all storage types and bins in a warehouse number. It reads the quant table directly and shows quantity, unit, stock category, and location, but it is read-only: it cannot correct, delete, or move a quant. Corrections require a transfer order or posting change transaction instead.
This page covers LS24, the classic Warehouse Management transaction used to display a material's quant-level stock across storage types and bins in a given warehouse number. It focuses on where LS24 sits versus LS26, LX03 and MMBE, and on diagnosing the most common cause of confusion: quant stock not matching plant stock or expected location because of open transfer orders or missing warehouse-level material data.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,148 words
Purpose
LS24 displays the warehouse stock of a single material, selected by warehouse number and optionally plant, storage location, storage type and bin range. It reads the quant table and returns one line per quant: storage type, bin, quantity, base unit, stock category, and special stock indicator where relevant. The one fact that explains most confusion around it is that LS24 shows quant-level, storage-bin stock, not plant-level inventory: a material can show correct total stock in MMBE while LS24 shows zero in the storage type someone expected, because the stock physically sits in an interim or staging storage type waiting on an open transfer order. LS24 is display only. There is no update, no posting, and no way to correct a quant from this screen.
When it is used
LS24 gets used whenever someone needs to confirm where a material's stock physically sits inside a warehouse: during a stock discrepancy investigation, before deactivating or deleting a storage bin, before running a posting change, or while chasing a goods movement that appears to have posted at plant level but not moved as expected in WM. It is the natural first stop when a business user reports a material as missing from a bin or a picking location. Consultants reach for LS26 instead when the starting point is a storage type or a specific bin rather than a material, and reach for LX03 when the question is about bin utilization or capacity rather than a single material's stock. LS24 only exists in classic WM; it has no role in decentralized or embedded EWM processes.
How to use it in practice
- Call transaction LS24.
- Enter the warehouse number and the material number; plant is usually required to resolve the material's warehouse view.
- Optionally restrict by storage type or storage bin range if the search needs to be narrowed; leave blank for a full picture across the warehouse.
- Execute and review the resulting list: one line per quant, showing storage type, bin, quantity, unit, and stock category.
- Double click a line to see quant detail including batch, quant number, and creation date.
- Cross check any unexpected line against open transfer orders (LB10, LT23) or plant stock (MMBE) before concluding the data is wrong.
Key data objects
- LQUA - the quant table itself: warehouse number, storage type, storage bin, material, quantity, unit, stock category, and batch. This is what LS24 actually displays.
- MLGN - material master data at warehouse number level, controlling whether the material is even set up for WM in that warehouse.
- MLGT - material master data at storage type level, controlling replenishment quantities and storage unit type restrictions per storage type.
- LAGP - storage bin master data, giving bin type, capacity and status used to interpret why a quant sits where it does.
How to prove it in the data
Open SE16N on table LQUA, filter on LGNUM (warehouse number) and MATNR (material). Sum the VERME (available quantity) field across all returned lines and compare it to the plant stock shown in MMBE for the same material and plant. If the LQUA total is lower than MMBE, check table LTAK/LTAP for open transfer orders against the same material and warehouse number; the gap usually sits in an interim storage type awaiting confirmation. If MLGN has no entry for the material and warehouse number combination, LS24 will return nothing at all regardless of physical stock.
ECC vs S/4HANA
LS24 is unchanged on S/4HANA where classic WM is still in use; the transaction, its selection screen, and the underlying quant table behave the same as on ECC. There is no dedicated Fiori app replacing it, since it is a backend diagnostic display rather than a business process step. Where embedded or decentralized EWM has been implemented instead of classic WM, LS24 has no equivalent and no relevance at all; stock visibility in that landscape comes from EWM's own monitor and stock overview tools.
Common pitfalls and how to diagnose them
- Quant missing but plant stock exists: MMBE shows stock, LS24 shows none in the expected storage type. Check LB10 for open transfer orders first; the stock is very likely sitting in a goods receipt or interim storage type waiting on putaway confirmation, not actually lost.
- Material not found at all: LS24 returns an empty list because the material was never extended to that warehouse number. This is a master data gap in MLGN/MLGT, fixed in the material master's warehouse management view, not an LS24 problem.
- Stock fragmented across many small quants: batch management or storage unit type settings force separate quants that look like an error but are simply how the material is configured. Confirm against the storage type's quant management indicator before treating it as a defect.
- Selection screen too narrow: entering a specific storage type or bin range and getting a false negative because the stock actually sits in a different storage type that was excluded from the selection. Rerun with the storage type and bin fields blank before concluding stock is missing.
- Attempting to correct stock from LS24 itself: because the transaction only displays, there is no way to adjust or delete a quant here. The correct route is a posting change without transfer order, or a standard transfer order, run through the appropriate WM transaction, not a manual table edit.
Whose problem this is
This is a functional WM issue, owned by the logistics or warehouse management consultant, not Basis or ABAP, unless the selection screen itself has been modified by custom code. A good handover includes the warehouse number, material, plant, the exact selection parameters used, a screenshot or extract of the resulting quant list, and, if a discrepancy is suspected, the matching MMBE and LB10 output for comparison.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ls24ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.