LTBP table — Transfer Requirement Item Table LTBP

One row in LTBP represents one item of a transfer requirement (Transportbedarf) inside classic Warehouse Management. A transfer requirement is a demand for a warehouse movement that has been recognized by an upstream process, such as a goods receipt, a delivery, a reservation for production, or a physical inventory adjustment, but where the actual bin-to-bin movement has not yet been carried out. LTBP carries the requirement quantity, the material, plant and storage location involved, and pointers back to the source document that generated the demand. It exists specifically for warehouse setups where the movement is not converted immediately into a transfer order, giving planners or an interim process a chance to review, consolidate or release requirements before the pick or putaway is actually triggered.

MANDT is the client field as usual. TBNUM is the most selective single field and should be used whenever a specific requirement is known; when working from a business symptom, restrict on LGNUM plus MATNR or LGNUM plus a date range on the header first, because LTBP has no reliable date field of its own for filtering. The table is typically smaller than LTAP or LTAK because only a subset of movements go through the two-step requirement-then-order process; a full-table scan is rarely necessary if the warehouse and material are known. Do not filter on ANFME alone to find open demand, since ANFME is the original requirement quantity and says nothing about how much has already been converted into a transfer order.

Symptom: a production backflush posted the goods movement in inventory management but the material is not showing up as putaway in the expected bin. Select LTBP where MATNR equals the material, WERKS and LGNUM equal the plant and warehouse, and RSNUM equals the reservation number from the production order if known. Take the ANFME on the resulting row, then check LTAP for items where TBNUM and TBPOS match this row to see how much has already been converted into a transfer order, and check LTBK-STATUS on the header to confirm the requirement itself has not already been closed.

LTBP is a classic Warehouse Management table and continues to exist unchanged on S/4HANA for warehouses still operated with LE-WM, including embedded scenarios. No compatibility CDS view is known to replace it. For warehouses migrated to decentralized EWM, the transfer requirement concept as stored here does not apply, since EWM uses its own warehouse task and warehouse order structures; a question framed around LTBP for an EWM-managed warehouse number is almost always a misunderstanding of which WM variant is in use, not a data problem.

A WM functional consultant owns questions about whether the transfer requirement step is even configured for the movement type in question, since that determines if LTBP should have a row at all. Warehouse operations should be consulted before treating a missing or unclosed row as a technical fault, since the business process may simply not route through this step. ABAP support is needed only for custom reports that join LTBP directly rather than using standard requirement lists.

LTBK is the transfer requirement header, always joined on TBNUM to check status before drawing conclusions from an LTBP item. LTAK and LTAP hold the transfer orders eventually created to satisfy the requirement, and are the tables to net against ANFME for true open quantity. MLGN and MLGT provide the warehouse-specific material master data referenced during requirement processing. T320 confirms the plant and storage location are correctly assigned to the warehouse number. Transactions in the classic WM transfer requirement family are used to create, change and display these documents.