LT01 — Create Transfer Order (Classic WM)

LT01 creates a transfer order in classic Warehouse Management, the document that instructs a warehouse worker to move stock from a source storage bin to a destination storage bin. The transaction accepts two very different entry modes on the same initial screen: with reference to a preceding document (delivery, production order, posting change notice, transfer requirement) or without any reference at all for a direct bin-to-bin move. Most of the confusion around LT01 traces back to this fork - the fields that appear, the way source and destination are proposed, and what happens on save differ completely depending on which mode was chosen. A TO created without reference never updates a delivery status; a TO created with reference to a delivery will, once confirmed, drive goods issue or putaway for that delivery.

LT01 is reached for manual, ad-hoc, or exception-driven transfer order creation. In a normal delivery-driven putaway or picking flow, TOs are usually generated automatically by a background job or through collective creation; LT01 gets used when that automatic step failed, when a picker needs a TO right now and cannot wait for the batch job, or when stock needs to move for a reason that has nothing to do with a delivery - cycle count correction, replenishment, quality block relocation. It also gets used in training and testing because it exposes every field the system considers when proposing a source or destination bin. There is no Fiori equivalent because this is classic WM; if the site runs embedded or decentralized EWM, warehouse task creation happens through different EWM-specific transactions entirely and LT01 does not apply there.

Use SE16 on LTAK filtered by warehouse number and creation date to locate the transfer order, and note the TO number. Pull the matching item lines from LTAP on that TO number to see the requested quantity against the confirmed quantity, and the source and destination storage type and bin that were actually recorded, not just proposed. Cross check those bins against LQUA for the same material and storage type to see whether stock is actually sitting where the TO claims; a mismatch usually means the TO was created but never confirmed, or got confirmed against a different bin than the one proposed.

On S/4HANA, LT01 and the rest of classic WM remain fully functional for warehouses that have not moved to EWM; nothing about the transaction's screen logic or bin proposal behavior changed. SAP's strategic direction is embedded EWM, and for warehouses running EWM the transfer order concept is replaced entirely by warehouse tasks and warehouse orders created through EWM-specific transactions and apps; LT01 has no role there. There is no Fiori replacement for LT01 within classic WM itself.

This is a functional WM problem in nearly every case - storage type strategy, bin assignment, or movement type configuration. ABAP involvement is needed only if a custom user exit or enhancement overrides the standard storage type or quantity proposal logic. Basis is relevant only for print output or RF device issues tied to TO printing. A good handover includes the TO number, the reference document, and the exact storage type and bin combination expected versus what was actually proposed.

LT02 is the natural next stop for changing bin assignment or quantity on a TO that LT01 already created but got wrong. LT03 handles the delivery-specific version of the same creation logic, and LT10 handles collective creation across many deliveries at once, both worth knowing before assuming LT01 is the only entry point. LT21 through LT23 display and list existing TOs, useful for checking whether one already exists before creating a duplicate. LX02 and LX03 give bin status and stock overviews to verify capacity and stock before trusting what LT01 proposed.