LT22 — Display Transfer Orders List

LT22 displays a list of transfer orders in classic SAP Warehouse Management, selected by warehouse number, TO number range, material, movement type, storage type, or confirmation status. It is a pure reporting transaction: no data is created or changed here. The structural fact that causes most of the confusion is that LT22 does not display a single transfer order the way LT21 does; it always returns a list, even if the selection matches only one document. Consultants who type in a specific TO number expecting the detail screen instead get a one-line list and have to double-click into it to reach the same screen LT21 would have opened directly. LT22 exists to find transfer orders across a warehouse, not to inspect one already known.

LT22 is reached for during monitoring and triage rather than during the transactional flow of picking or putaway. A warehouse supervisor uses it to find all open, unconfirmed transfer orders for a storage type before a shift change, or to check whether a batch of TOs generated overnight by a wave or a background job actually got created. It is also the fallback when a delivery is stuck and the exact TO number is unknown: search by movement type and creation date instead. In EWM-based warehouses this monitoring role is taken over by the warehouse monitor; LT22 only applies where classic WM is still active. Fiori coverage for classic WM is limited, so this remains a SAP GUI-only tool in most landscapes.

Open LTAK in SE16N, filter on the warehouse number field and the confirmation status field, and add a date range on the creation date if the result set is large. To check whether a TO that LT22 still shows as open has actually been partially worked, join to LTAP on warehouse number and TO number and compare the requested quantity against the confirmed quantity; a mismatch there, rather than the header status, is usually what explains an apparently stuck TO.

Where classic Warehouse Management is still active on S/4HANA, LT22 behaves exactly as it did on ECC; there is no functional change and no dedicated Fiori replacement, since Fiori coverage for classic WM monitoring is thin. For warehouses migrated to embedded EWM, LT22 does not apply at all; the equivalent monitoring task is done through the EWM warehouse monitor, which is built on a different object model, not LTAK and LTAP.

This is a functional WM problem in essentially all cases; the transaction itself never fails technically, only the selection or the underlying data does. ABAP involvement is limited to custom selection variants or added authorization checks. A handover to the WM consultant should include the exact selection criteria used, the warehouse number, and whether the missing TOs are expected to be open, confirmed, or archived.

LT21 is the natural companion: use it once a specific TO number is known, LT22 to find that number in the first place. LT01 explains where the TO being searched for was created, LT12 and LT03 are where it gets confirmed, and LT23 is used to reprint a TO already found through LT22. Reading LT21 alongside this page clarifies why LT22 always drills into the same detail screen rather than having its own separate layout.