LX03 — Warehouse Stock Overview Report

LX03 is the warehouse stock overview report in classic Warehouse Management. It reads quant records and presents them aggregated by storage type, storage section, storage bin, material, batch or stock category for a chosen warehouse number. The structural fact that explains most confusion around it: LX03 is a display and analysis layer only. It has no update logic of its own. Consultants new to WM sometimes expect to correct a wrong bin quantity from this screen, or double-click a line expecting a change dialog. Nothing happens, because there is nothing to change here. The actual stock lives in the quant table, and it only moves through a transfer order, a posting change, or a physical inventory adjustment. LX03 exists to let someone see that stock, sliced different ways, before deciding what movement transaction to run against it.

LX03 gets pulled up whenever someone needs a broader view than a single bin: preparing a cycle count, investigating a reported discrepancy between physical count and system stock, checking capacity utilization across a storage type before a putaway run, or supporting an audit that asks for stock by material across the whole warehouse. It sits alongside LS24 and LS26, which give narrower single-bin or single-storage-type views; a consultant reaches for LX03 when the question spans multiple bins or storage types at once rather than one specific location. It is a classic WM transaction. If the storage location in question is managed by an EWM-decentralized or embedded warehouse rather than classic WM, LX03 will show nothing useful, because the quant data lives in the EWM stack instead.

To confirm what LX03 is showing, go to SE16 on LQUA and filter by warehouse number, storage type, and material. Compare the quantity field against the line LX03 displays for the same combination. If the report appears to be missing stock, check LAGP for the same bin to see whether a blocking indicator or empty-bin flag is set, and check whether the special stock indicator or stock category on the LX03 selection screen excludes quality inspection or blocked stock by default.

LX03 continues to function on S/4HANA for warehouses still run under classic WM. Nothing structural changes in the transaction itself. For warehouses migrated to embedded or decentralized EWM, the equivalent stock overview lives in a different report and Fiori app native to the EWM stack, and LX03 will not reflect that warehouse's stock at all. The first check on any S/4HANA system where LX03 looks wrong is whether the warehouse number in question is still classic WM or has already moved to EWM.

This is a functional WM problem in almost every case. Basis involvement is limited to authorization object assignment when users report restricted visibility. ABAP involvement only comes up if a custom selection variant or downstream interface has been built on top of the report. A good handover states the warehouse number, storage type or bin range checked, the expected versus actual quant quantity, and whether any transfer order is open against the bin in question.

LS24 and LS26 are the natural next stops for narrowing a discrepancy down to a single bin or storage type once LX03 has flagged something worth investigating. LX02 covers bin status rather than quant content and is useful when the question is about bin availability rather than stock quantity. LT21 and LT22 help trace whether an open, unconfirmed transfer order explains a quantity that looks wrong in LX03. LB10 is worth checking when the suspicion is that an open transfer requirement, rather than a data error, accounts for the discrepancy.