LT21 — Display Transfer Order

LT21 displays one transfer order by TO number, pulling the header from LTAK and the item lines from LTAP. It is read-only: there is no create or change function hiding behind it, which is the first thing to check when someone reports that LT21 will not let them fix a quantity. The structural fact that explains most confusion is that LT21 shows the TO as it was written at creation and last confirmation, not the current live stock at the bin. If a quant referenced by the TO has since moved through another process, LT21 still shows the original bin and quantity captured on the TO item, and the screen will look correct even though the physical situation has changed underneath it.

LT21 sits downstream of TO creation (LT01, LT04, LT06) and upstream of or alongside confirmation (LT03, LT12). It is reached for mid-incident, when a specific TO number is already known from a delivery, a picking list, or a warehouse worker's complaint, and the question is simply what does this TO currently say. Consultants use LT21 instead of LT22 when the exact TO number is in hand; LT22 is for searching a population of TOs by warehouse, date, or status when the number is not known. It is also the first stop before deciding whether a correction needs LT02 (change), LT03 (confirm), or a cancellation, since none of those should be attempted blind.

In SE16, filter LTAK on the TO number and warehouse number to confirm the header exists and read its status field. Then filter LTAP on the same TO number to list all item splits and compare requested quantity against confirmed quantity per line, not just at header level. Take the quant number from LTAP and look it up in LQUA to see whether that quant still exists and still holds the same quantity at the same bin; a mismatch there, not a fault in LT21, explains why the display looks stale.

In S/4HANA, classic embedded WM keeps LT21 and the LTAK and LTAP tables unchanged for warehouses still managed under classic WM. For warehouses under decentralized or embedded EWM, LT21 and the LTAK and LTAP structure are not the relevant object at all; the equivalent unit of work is the warehouse task, viewed through the EWM warehouse monitor rather than through LT21. The choice between the two depends entirely on which management type the warehouse number is assigned to.

Functional WM territory in almost every case. ABAP involvement is limited to custom fields exposed on the item detail screen or authorization object issues. Basis is rarely involved except for TO archiving and restore questions. A good handover states the TO number, warehouse number, expected status, and a screenshot of the item detail screen showing requested versus confirmed quantity.

LT01, LT02, and LT03 cover the create, change, and confirm side of the same TO that LT21 only displays, and are the natural next stop once a discrepancy is confirmed. LT22 is the list-based sibling for when the TO number is not yet known. LT23 approaches the same data from the material side rather than the TO number side. LS24 and LS26, and LX02 and LX03, give the current physical bin and stock picture that LT21 itself cannot, which is essential for telling a stale TO display apart from a real stock problem.