LI11N — Enter Physical Inventory Count in WM
LI11N records physical inventory count results for classic Warehouse Management inventory documents. Enter the quantities actually counted in the warehouse, not the system quantity expected by SAP. The transaction belongs to classic LE-WM/Stock Room Management; an EWM-managed warehouse uses EWM physical-inventory processes instead.
Verified practitioner reference for LI11N — Enter Physical Inventory Count 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· 514 words
Esta página aún no está disponible en español.
Purpose
enter physical inventory count results for classic WM inventory records. 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
LI11N is typically used when warehouse staff have physically counted stock and the result must be recorded against the WM inventory document. 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
- Open the intended inventory record.
- Enter counts exactly as physically observed.
- Review zero-count and recount rules.
- Save and inspect calculated differences.
- Route significant differences for recount/approval before clearing.
Key data objects
These are the fields and objects most useful for explaining a LI11N result. Record them in incident evidence and test scripts.
- warehouse/inventory document — verify the exact value, validity/status, and relationship to this transaction's business object.
- storage bin — verify the exact value, validity/status, and relationship to this transaction's business object.
- material/stock — verify the exact value, validity/status, and relationship to this transaction's business object.
- count quantity — verify the exact value, validity/status, and relationship to this transaction's business object.
- recount/difference status — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a LI11N count by comparing the inventory document's system stock with the entered physical count for the same warehouse, bin, material, stock category, and count date. Record recount status and differences. After approval/clearing, verify the resulting warehouse stock and any required Inventory Management reconciliation.
ECC vs S/4HANA
SAP Help references LI11N for WM cycle-count/count-result entry and inventory processing. 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
- Entering system quantity instead of physical count to avoid a difference. Confirm the exact status and process ownership before applying a correction.
- Counting the wrong bin or stock category. Confirm the exact status and process ownership before applying a correction.
- Clearing differences before required recount. 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/li11nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.