LS26 — LS26 Warehouse Stock Overview by Bin

LS26 displays warehouse stock at the level of storage bins and quants for a given warehouse number, with optional narrowing by storage type, storage bin, material or quant number. It queries the quant table directly along with the bin master, so what appears on screen is the physical WM stock position at the moment of query, not a cached report and not a forecast of pending movements. The structural fact that causes most confusion: LS26 is purely a display transaction. It has no update, adjustment or posting capability. Consultants under pressure during an incident often go looking in LS26 for a way to fix a wrong quantity, find nothing, and conclude the transaction is broken, when in fact the correction path runs through a completely different set of transactions.

Reached for whenever someone needs to see exactly what stock sits in which bin before creating a transfer order, before releasing a picking wave, or while investigating a reported stock difference between the warehouse and inventory management. It is also the first stop when reconciling against a stock comparison run, or before starting a physical inventory count on a storage type. Compared to LS24, which shows one material across the whole warehouse, LS26 is used when the question is bin-centric or storage-type-centric rather than material-centric, or when several materials in one area need to be seen together. In an EWM-managed warehouse this transaction has no equivalent value and the EWM stock monitor should be used instead.

In SE16 or SE16N, open LQUA and filter by warehouse number and material number, or by warehouse number, storage type and storage bin, to see the raw quant records LS26 is displaying. Sum the available quantity field across all matching rows rather than trusting a single line, since stock is often split across several bins. To prove a WM versus IM mismatch, take the same material and plant, find the storage location mapped to the warehouse number through the WM-to-IM assignment table, and compare the LQUA sum against the corresponding quantity in MARD. Also check the quant status and blocking fields on LQUA before concluding stock is genuinely missing.

LS26 still exists and behaves the same on S/4HANA wherever classic Lean WM or full WM is active, because it is still a direct read of the same quant table structure. Nothing about the selection logic or the display-only nature changed. Where a warehouse has been migrated to embedded or decentralized EWM, LS26 is not the tool to use; the EWM stock monitor or its Fiori equivalent replaces it, and running LS26 against an EWM-managed warehouse number will return nothing meaningful.

Functional WM or logistics consultant owns interpretation of what LS26 shows. Basis or interface teams get involved only when the discrepancy traces back to a failed queue or IDoc between a decentralized WM system and the ERP backend. A good handover includes the warehouse number, material, storage type and bin, a screenshot or export of the relevant LQUA lines, and any open transfer order numbers found on the same quant.

LS24 is the natural companion for a material-centric rather than bin-centric view across the whole warehouse. LT01 and LT10 are the transactions that actually move or correct stock once LS26 has identified where the problem sits. LT21, LT22 and LT23 are used to check open or pending transfer orders that explain why an available quantity differs from the total quantity shown. LX02 and LX03 support the broader reconciliation and physical inventory workflow that LS26 findings usually feed into.