LX02 — Bin Status Report for Classic Warehouse Management

LX02 produces a bin-level view of a warehouse number: for a chosen storage type, storage section, or bin range, it lists every bin together with the quants currently assigned to it, the capacity consumed versus capacity available, and flags such as blocked, mixed-storage, or empty. The one fact that explains most confusion is that this is a live read against the current bin and quant tables at execution time, not a cached or batch-generated report. Two runs seconds apart can differ if transfer orders are confirmed in between. It is easy to mistake it for LS26, which reports stock by material across bins rather than by bin, and the two answer different questions even though both sit on top of the same underlying quant data.

Reached for whenever someone needs to know the physical occupancy of a warehouse area rather than the stock position of a material. Typical triggers: preparing a physical inventory count and needing to know which bins are empty and can be skipped, investigating why a putaway strategy keeps proposing full bins, checking whether a storage type's capacity master data is even maintained, or auditing mixed-storage violations after a layout change. In classic WM this is the standard tool; there is no comparable single-bin-capacity tcode in EWM, so a consultant working an EWM warehouse instead opens the Warehouse Monitor and drills into the bin node, or uses slotting and capacity check reports specific to EWM.

Pull LAGP filtered on warehouse number and storage type to get the bin list and its maintained capacity values. Separately pull LQUA on the same warehouse number and storage type, summing quantity by bin. Join the two on the bin coordinate field and compare summed quant quantity against the bin's capacity value from LAGP; a bin showing as overfilled on LX02 but with a blank or zero capacity value in LAGP indicates missing capacity master data rather than a genuine overflow. Cross-check any bin that looks empty on LX02 but has open lines in LTAP for that bin, which points at an unconfirmed transfer order still in flight.

Classic WM, and LX02 with it, continues to function unchanged for warehouses still running on classic WM inside S/4HANA; SAP positions EWM as the strategic warehouse solution but does not remove LX02 from existing classic WM installations. There is no Fiori app replacing LX02 in classic WM. In EWM there is no equivalent transaction code at all; bin occupancy and capacity are inspected through the Warehouse Monitor's bin and stock nodes instead, which work on a different data model entirely.

Functional WM territory. The report itself needs no configuration to run, but the capacity values it depends on are set up by the WM consultant during storage type and material master configuration. A clean handover includes the warehouse number, storage type, and bin range investigated, whether open transfer orders were checked, and whether capacity master data was confirmed as maintained before escalating a result as a genuine data problem.

LS24 is the natural drill-down from a suspicious bin line, showing the quant in full detail including batch and special stock status. LS26 answers the complementary question of where a given material sits across all bins, useful when LX02 shows an unexpected bin occupant. LT21 confirms whether an apparently empty or full bin is actually mid-movement on an open transfer order. LX03, the warehouse activity monitor, is the next stop when the bin-level picture from LX02 needs to be correlated against processing backlogs and exception queues across the warehouse.