LQUA table — LQUA Warehouse Management Quant Table

Each row in LQUA is a quant: a specific quantity of one material (and, where relevant, one batch and one stock category or special stock indicator) physically located in one storage bin of one storage type in one warehouse number. It is the WM-side counterpart to inventory management stock tables such as MARD or MCHB, but expressed at bin granularity rather than plant/storage location granularity. Quants are created and consumed by confirmed transfer orders. A quant does not represent a movement; it represents a resting state of stock at a point in time. When the quantity in a bin reaches zero, the quant row is normally deleted rather than kept at zero, which matters when someone goes looking for history.

LQUA is client-dependent and can be large in an active warehouse, so never select on MATNR alone across all warehouse numbers. Lead with LGNUM, then LGTYP and LGPLA if the bin is known, then MATNR and CHARG. If chasing a specific stock category or special stock issue, add BESTQ and SOBKZ to the selection rather than filtering after extraction. Because zero-quantity quants are deleted, a missing row for a material in a bin is not evidence the material was never there; it only proves there is nothing there now. Cross-check VERME against GESME before assuming the full quantity is actually available, since the difference is stock already earmarked by open transfer order items.

Symptom: a picker reports the system shows stock in a bin but nothing is physically there, or a putaway confirmation seems to have vanished. Select LQUA on LGNUM, LGTYP, LGPLA, MATNR, restricted to that exact bin. If VERME is nonzero but EINME also carries a value, the quantity is still tied up in an unconfirmed transfer order rather than truly available; pull LTAP with the same warehouse/storage type/bin/material/batch to find the open item and its confirmation status before touching the quant directly.

LQUA continues to exist and function unchanged in shape for warehouse numbers still run on classic Warehouse Management inside S/4HANA. It is not the quant table for embedded or decentralized EWM, which SAP positions as the strategic path for new warehouse implementations and which maintains stock in its own separate quant structures. A project doing a WM-to-EWM migration needs to plan for the fact that LQUA data does not carry over automatically and has to be reconciled or converted as part of the migration.

Warehouse operations or logistics execution consultants own questions about LQUA content, since it reflects transfer order activity they configure and monitor. Basis or data teams should not be asked to adjust rows directly; discrepancies are resolved through physical inventory documents or transfer order cancellation, not table maintenance. Reporting teams building extracts should confirm with WM functional consultants which stock categories and special stock indicators are in scope before aggregating quantities.

LTAK and LTAP (transfer order header and items) are the transactions' underlying tables that create, change, and confirm quants, written by transfer order creation and confirmation. LAGP holds the bin master that every LQUA row references for bin attributes and blocking. MLGN and MLGT carry material master WM settings at warehouse and storage-type level that influence how quants are proposed and stored. T300 and T301 hold warehouse number and storage type control data consulted whenever quant behavior looks wrong.