LI01N — Create Physical Inventory Record in WM
LI01N starts a classic Warehouse Management physical-inventory process by creating inventory records for selected warehouse bins or stock. It belongs to the classic LE-WM/Stock Room Management model, not EWM. Before creating records, confirm the warehouse architecture and inventory scope so the same stock is not already covered by another open physical-inventory document.
Verified practitioner reference for LI01N — Create Physical Inventory Record 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· 548 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
create a classic Warehouse Management physical-inventory document/record for storage-bin stock counting. 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
LI01N is typically used when a classic WM warehouse starts a physical inventory process for selected bins or stock. 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
- Confirm the warehouse uses classic WM physical inventory.
- Define the inventory scope and date.
- Create the inventory record for the intended bins/stock.
- Freeze/control movements according to the configured inventory process.
- Proceed to count entry and difference clearing through the related WM transactions.
Key data objects
These are the fields and objects most useful for explaining a LI01N result. Record them in incident evidence and test scripts.
- warehouse number — verify the exact value, validity/status, and relationship to this transaction's business object.
- storage type/bin — verify the exact value, validity/status, and relationship to this transaction's business object.
- inventory method/date — verify the exact value, validity/status, and relationship to this transaction's business object.
- inventory document — verify the exact value, validity/status, and relationship to this transaction's business object.
- stock/count scope — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a LI01N inventory setup by recording warehouse number, storage type/bin, inventory method/date, and the generated inventory document. Verify which quant or bin stock is included and whether movements are controlled as required. Continue through count entry and difference processing, then reconcile the final warehouse and Inventory Management stock.
ECC vs S/4HANA
LI01N belongs to classic WM physical-inventory processing; S/4HANA warehouse architecture should be confirmed before using it as a new design reference. 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
- Creating overlapping inventory records for the same stock. Confirm the exact status and process ownership before applying a correction.
- Counting while uncontrolled warehouse movements continue. Confirm the exact status and process ownership before applying a correction.
- Using classic WM physical-inventory transactions in EWM. 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/li01nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.