SAP transaction codeObjectLT23ModuleWM_EWM

LT23 — Display List of Transfer Order Items

LT23 displays a selectable list of transfer order items (LTAP records) across many transfer orders at once, rather than requiring a single TO number like LT21. It is used to reconcile open, unconfirmed TO quantity against physical bin stock, find TOs for a material or bin without knowing the TO number, and identify stuck items before running mass confirmation.

This page covers LT23, the classic WM list display for transfer order items, and how it differs structurally from single-TO display transactions. It focuses on the diagnostic use of the list: finding open TO quantity that explains a stock discrepancy, and the pitfalls of misreading item versus header status.

Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,088 words

Purpose

LT23 shows a list of transfer order items matching a selection, rather than opening one TO by number. The structural fact that explains most confusion is that a transfer order has two levels, header (LTAK) and item (LTAP), each carrying its own status. LT23 operates at item level, so it can pull together items from many different TO numbers, storage types, or materials in a single list. This is what makes it useful for reconciliation work: a consultant can ask 'what open TO quantity exists for this material in this storage type' without knowing which TO numbers to look at. LT21, by contrast, needs the TO number already in hand. LT23 is read-only; it cannot change a TO's status or content, only display it.

When it is used

Reached for when a stock discrepancy investigation needs to know how much quantity is currently tied up in open (unconfirmed) transfer orders for a material, bin, or storage type, before assuming a physical count problem. Also used to find the TO covering a specific delivery, storage unit, or door when the TO number itself is unknown, and before running mass confirmation (LT12) to see what is still outstanding and why. In a warehouse still running classic or decentralized WM, this is the everyday triage step before escalating a 'system shows stock but I cannot pick it' complaint. Not used for EWM-managed warehouses, which have their own monitors and do not populate the classic LTAK/LTAP tables.

How to use it in practice

  • Open LT23 and enter the warehouse number together with as many restricting fields as possible: material, plant, storage type, TO number range, date range, and status.
  • Execute and review the resulting list of TO items with quantity, source bin, destination bin, and confirmation status.
  • Sort or group the list by material or bin to compare against the stock overview for the same bin.
  • Double-click a line to jump into the single TO display (LT21) for full header and item detail when a line needs closer inspection.
  • Note which items are still open versus already confirmed before drawing any conclusion about locked stock.

Key data objects

  • LTAK - transfer order header: warehouse number, TO number, TO type, movement activity, creation and confirmation dates, overall header status.
  • LTAP - transfer order item: material, quantity, unit of measure, source storage type/bin, destination storage type/bin, confirmed quantity, item-level status.
  • LQUA - warehouse quant table, used alongside LT23 output to compare bin stock against open TO quantity for the same material and bin.
  • MKPF/MSEG - the underlying goods movement document, relevant when a TO item references a posted material document and the discrepancy needs tracing back to accounting.

How to prove it in the data

Run SE16 on LTAP filtered by warehouse number and material, restricted to items whose status field shows still open (not confirmed). Sum the open quantity per source or destination bin. Join to LTAK on the TO number to check the header-level status and creation date, since a header can show completed while an individual item remains open after a partial confirmation. Compare the summed open LTAP quantity for a bin against the quant quantity in LQUA for the same bin: the gap between the two is the quantity locked in transit that LT23 makes visible without opening each TO.

ECC vs S/4HANA

LT23 and the underlying LTAK/LTAP tables belong to classic and decentralized WM. On S/4HANA, warehouses converted to embedded EWM do not use these tables; open-item and warehouse task reconciliation there is done through EWM's own monitor and Fiori-based warehouse management apps rather than LT23. For warehouses still running classic Lean WM or decentralized WM on S/4HANA, LT23 behaves the same as on ECC with no functional change.

Common pitfalls and how to diagnose them

  • Selection too broad: omitting date range or storage type on a large warehouse returns a huge item list or times out; always restrict by storage type and a recent date window first, then widen only if the list is empty.
  • Open versus confirmed confusion: the list mixes items regardless of confirmation state unless explicitly filtered; summing all quantity without checking the status field double-counts stock that has already been put away or picked.
  • Header status does not equal item status: a TO header can show as completed while one item inside it is still open because of a partial confirmation or a split; reading only the header status and ignoring item status leads to the wrong conclusion about locked stock.
  • Wrong warehouse number entered: each plant and storage location combination maps to a specific warehouse number; entering the wrong one returns an empty or irrelevant list that looks like 'no open TOs' when the real answer is 'wrong selection'.
  • Interim or staging bins inflating the count: TO items sitting in interim putaway or goods-receipt staging storage types remain open far longer than normal picking TOs and can make the locked quantity look abnormally high; check the storage type category before treating this as an error.
  • Trying to fix from LT23: it is display-only. The reflex of trying to change quantity, bin, or status from this screen does nothing; the actual correction happens in LT21/LT02 for the TO itself or through the appropriate confirmation transaction.

Whose problem this is

Functional WM ownership: interpreting open TO quantity, deciding whether it explains a stock or availability discrepancy, and deciding which TOs need confirmation or cancellation. Basis involvement is rare, limited to selection screens timing out on large item tables, which points to archiving or index questions. A good handover states the warehouse number, material, storage type, and the specific open TO numbers found, not just 'stock looks wrong'.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tcodes/lt23ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.