LB10 — Display Negative Stocks in Warehouse Management

LB10 displays all storage bins in a warehouse number where the stock quantity in the quant table has gone negative. It is a monitoring report, not a posting transaction: it shows the problem but does not let the user correct it from the same screen. The structural fact that explains most confusion is that a negative quant is not automatically an error condition. Certain storage types, particularly interim or staging types used in two-step picking or automated conveyor processes, are explicitly configured to allow negative stock for short windows between a goods issue posting and the matching putaway or pick confirmation. LB10 will list those bins too, alongside genuine data problems, so the report cannot be read as a straight error list without knowing the storage type control settings first.

LB10 is reached for during period-end stock reconciliation between Inventory Management and Warehouse Management, during warehouse audits, or immediately after a batch of transfer order confirmations run through an RF or automated warehouse control system. It is also the first stop when a physical inventory count in the warehouse disagrees with the book quantity, or when a material shows blocked or unavailable stock that traces back to a bin nobody can locate physically. In embedded classic WM on S/4HANA it is still the standard entry point for this check; there is no Fiori app that replaces it for classic WM. In EWM environments the equivalent investigation runs through stock and quant monitoring apps rather than this transaction.

Open SE16 or SE16N on LQUA, filter on the warehouse number and restrict to the storage type or bin range under investigation, then sort or filter the quantity field to isolate negative values. For each negative quant found, note the material, stock category, and special stock indicator, then look up the same material and storage type combination on the material WM data table to confirm whether a negative stock indicator is set there. If it is not set, pull the transfer order items for that bin and material from the TO history table around the timestamp the quant last changed to identify the confirmation sequence that produced the negative balance.

Classic WM, and therefore LB10, remains available in S/4HANA when a warehouse is run under embedded classic WM rather than decentralized or embedded EWM. The transaction itself did not change functionally. For warehouses run on EWM there is no LB10; negative stock situations are instead surfaced through EWM's stock and quant monitoring tools, which work differently because EWM does not use the same quant table structure as classic WM.

This is a functional WM issue in the first instance. It becomes an ABAP concern only if a custom interface or enhancement is posting movements in the wrong order, and a Basis concern only if job scheduling or queue processing delays are causing the sequencing problem. A good handover includes the warehouse number, the specific bin and material, the quant's stock category, and the transfer order history showing the exact sequence of postings around the negative balance.

LB11 and LB12 belong to the same reporting family and are worth checking alongside LB10 since they cover related stock and bin status views in the same warehouse. LX02 and LX03 come into play once a negative quant needs resolving through a formal physical inventory count rather than a manual correction. LS26 gives a broader stock overview per storage bin and is useful for confirming whether a negative quant is an isolated case or part of a wider pattern in that storage type.