LT04 — Create Transfer Order from Transfer Requirement
LT04 creates a classic Warehouse Management transfer order with reference to a transfer requirement. It turns warehouse movement demand into executable bin-level work under the classic LE-WM/Stock Room Management model. Validate the transfer requirement and stock-removal/placement strategy before overriding proposed bins, and do not apply this transaction to an EWM-managed warehouse.
Verified practitioner reference for LT04 — Create Transfer Order from Transfer Requirement. 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· 541 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
create a classic WM transfer order with reference to an existing transfer requirement. 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
LT04 is typically used when a transfer requirement represents the warehouse movement demand and must be converted into executable bin-to-bin work. 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 relevant transfer requirement.
- Confirm warehouse, material and quantity.
- Review source/destination data proposed by WM strategies.
- Create the transfer order.
- Confirm execution and verify the requirement is processed as expected.
Key data objects
These are the fields and objects most useful for explaining a LT04 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.
- transfer requirement — verify the exact value, validity/status, and relationship to this transaction's business object.
- material/quantity — verify the exact value, validity/status, and relationship to this transaction's business object.
- source/destination bin — verify the exact value, validity/status, and relationship to this transaction's business object.
- transfer-order number/status — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove an LT04 flow by opening the source transfer requirement, recording material, quantity, warehouse number, and movement context, then linking it to the created transfer order. Verify source/destination bins and final confirmation status. If the requirement remains open, determine whether the transfer order covered the full quantity or whether another open item remains.
ECC vs S/4HANA
SAP Help identifies LT04 as Create Transfer Order from TR and references it in Warehouse Management documentation. 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 duplicate transfer orders for the same open requirement. Confirm the exact status and process ownership before applying a correction.
- Overriding storage strategies without operational justification. Confirm the exact status and process ownership before applying a correction.
- Using classic WM transactions for an EWM-managed location. 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/lt04ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.