LT03 — Create Transfer Order for Delivery
LT03 creates a classic Warehouse Management transfer order with reference to an outbound delivery. It converts delivery-related warehouse demand into bin-level picking work in a classic LE-WM/Stock Room Management warehouse. Do not use it as an EWM warehouse-task transaction; in EWM-managed locations, warehouse execution follows the EWM object model.
Verified practitioner reference for LT03 — Create Transfer Order for Delivery. 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· 568 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
create a classic Warehouse Management transfer order with reference to a delivery for picking or goods-movement execution. 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
LT03 is typically used when an ECC or classic WM warehouse needs a transfer order to move delivery-related stock between bins. 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 classic WM is the active warehouse solution for the storage location.
- Enter the delivery and warehouse number.
- Review proposed source bins and quantities.
- Create the transfer order and capture its number.
- Confirm the transfer order through the appropriate WM confirmation process.
Key data objects
These are the fields and objects most useful for explaining a LT03 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.
- delivery — verify the exact value, validity/status, and relationship to this transaction's business object.
- source/destination storage type/bin — 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.
- transfer-order status — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove an LT03 flow by linking the delivery to the created transfer order and its items, then checking source bin, destination/interim storage type, material, quantity, and confirmation status. Compare the delivery picking status after confirmation. If no transfer order is created, inspect delivery relevance, WM organizational assignment, and existing open warehouse work first.
ECC vs S/4HANA
SAP Help explicitly references LT03 as Create Transfer Order for Delivery. Classic WM is a legacy warehouse solution; S/4HANA programs should confirm whether Stock Room Management or EWM is the target architecture. 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
- Using LT03 in an EWM-managed warehouse. Confirm the exact status and process ownership before applying a correction.
- Creating a second transfer order when open picking already exists. Confirm the exact status and process ownership before applying a correction.
- Overriding source bins without understanding stock-removal strategy. 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/lt03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.