LI20 — Clear Inventory Differences in WM
LI20 clears approved physical-inventory differences in classic Warehouse Management after count or recount processing. It should be used only after the discrepancy has been reviewed and accepted under inventory controls. Clearing a WM difference is part of a process; verify the corresponding Inventory Management effect and final stock reconciliation rather than treating LI20 as a generic stock-adjustment tool.
Verified practitioner reference for LI20 — Clear Inventory Differences in WM. The page covers the operational purpose, correct usage sequence, key data to capture, evidence-based diagnosis, S/4HANA context, frequent mistakes, ownership and related SAP objects.
Published 20 Sept 2026· 542 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
clear approved physical-inventory differences in classic WM after count/recount processing. The transaction should be understood as one point in the full operational process. Master data, status, validity dates and preceding execution steps often determine what can happen here, so preserve that context before changing the symptom.
When it is used
LI20 is typically used when a WM inventory document has an accepted difference that must update warehouse stock and proceed to IM reconciliation as designed. It is also useful in project testing and support reproduction because it exposes a concrete process state. In production, keep the initial selection narrow and separate display/analysis from actions that mass-change, count, clear or post.
How to use it in practice
- Review the final count and recount evidence.
- Confirm the difference is approved under inventory controls.
- Clear only the intended WM differences.
- Check the resulting WM status and any required IM follow-on step.
- Reconcile stock after difference posting.
Key data objects
These are the fields and objects most useful for explaining a LI20 result. Record them in incident evidence and test scripts.
- inventory document — verify the exact value, validity/status, and relationship to this transaction's business object.
- warehouse/bin — verify the exact value, validity/status, and relationship to this transaction's business object.
- difference quantity — verify the exact value, validity/status, and relationship to this transaction's business object.
- difference status — verify the exact value, validity/status, and relationship to this transaction's business object.
- follow-on IM posting — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a LI20 posting by documenting the inventory document, final count, approved difference, warehouse/bin/material, and difference status before clearing. After execution, verify the WM stock update and any required Inventory Management follow-on posting, then reconcile the final quantities. Investigate any remaining IM/WM difference rather than repeating the clearing step.
ECC vs S/4HANA
SAP Help references LI20 for clearing Warehouse Management physical-inventory differences. Where a classic component is legacy, the page explicitly keeps that context so readers do not mistake technical availability for SAP's strategic architecture for new implementations.
Common pitfalls and how to diagnose them
- Clearing uninvestigated differences to close inventory quickly. Confirm the exact status and process ownership before applying a correction.
- Assuming WM difference clearing automatically resolves every IM discrepancy. Confirm the exact status and process ownership before applying a correction.
- Processing the wrong inventory document/bin. Confirm the exact status and process ownership before applying a correction.
Whose problem this is
Primary ownership is the WM EWM team, with adjacent functional, technical, Security, or integration teams joining only where the evidence crosses component boundaries. Escalate with the exact object/document, organizational keys, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/li20ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.