LTBK table — Transfer Requirement Header Table

A transfer requirement is a request to move stock within a warehouse number before a physical transfer order is created and confirmed. LTBK holds the header: warehouse number, movement type, requirement date and time, and the user or process that generated it. Transfer requirements are typically created automatically when a goods receipt or goods issue is posted in Inventory Management for a storage location under warehouse management, and the relevant movement type is configured for two-step processing (requirement first, transfer order second) rather than immediate transfer order creation. They can also be created manually for internal warehouse moves. Until a transfer order is created and confirmed against it, the stock referenced by the requirement sits in an interim area, logically requested to move but not yet physically relocated.

Always restrict by MANDT and LGNUM first; a warehouse number can carry a large volume of historical requirements if the site does not archive. TBNUM is the most selective field once known, typically obtained from a goods movement document or from the item table LTBP rather than guessed. Do not scan LTBK by date range alone across all warehouse numbers in a productive client; the table can be large in high-throughput sites and an unrestricted date-only selection is expensive. If chasing a specific material movement, go through LTBP first to filter by material or plant-relevant fields, then pull the matching TBNUM back into LTBK for the header context.

Symptom: a goods receipt posted but the material has not appeared in the final storage bin. Selection: query LTBP for the material and warehouse number to find the TBNUM, then read LTBK for that TBNUM to confirm the requirement exists and check its creation date and movement type. If a matching transfer order is not found in LTAK/LTAP for the same TBNUM, the requirement is still open and the stock is sitting in the interim area, not lost.

LTBK is part of classic Warehouse Management, which remains technically available in S/4HANA for sites that have not migrated to embedded or decentralized EWM. Its structure has not materially changed. SAP's strategic direction for new warehouse implementations is EWM, where this table has no equivalent; warehouse requests and tasks replace the transfer requirement and transfer order model entirely. No compatibility CDS view mapping LTBK data forward into an EWM structure should be assumed to exist.

The warehouse or logistics execution functional consultant owns configuration questions about which movement types generate a transfer requirement versus an immediate transfer order. Inventory management or MM functional consultants get involved when the trigger is a goods movement posting rather than a manual warehouse transfer. Basis is only relevant if the table's size is driving an archiving or performance conversation.

LTBP holds the item lines belonging to each LTBK header. LTAK and LTAP are the transfer order header and item created to fulfil a requirement, written by the standard transfer order creation transaction. LAGP and LQUA reflect the physical bin and quant state once the transfer order is confirmed. T300 and T301 are warehouse number and storage type customizing tables referenced when validating why a requirement was routed to a particular interim storage type.