LTBK
transaction S/4HANA status: Active (StRM) · Replaced (EWM)S/4HANA status depends on deployment path: active with SAP Stock Room Management; replaced by EWM otherwise
Transfer Requirement Header
Classic LE-WM transfer requirements succeeded by EWM warehouse requests in S/4HANA, modeled in the cataloged /SCDL/ delivery-request tables. Still written under SAP Stock Room Management, the in-scope successor to classic LE-WM for simpler warehouses; the /SCDL/* mapping applies only on the EWM path.
What the badges mean
- S/4HANA status: Active
- Active and unchanged in S/4HANA.
- S/4HANA status: Deprecated
- Still readable today, but no longer SAP's strategic path — plan around it.
- S/4HANA status: Replaced
- Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
- S/4HANA status: Migrating to IBP
- Planning scope is moving from APO toward IBP.
- S/4HANA status: Active (StRM) · Replaced (EWM)
- Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
- S/4HANA status: Replaced · Compat View
- Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
- S/4HANA status: Active · Proxy View
- Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
- master
- Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
- Linked type codes
CLNT — the client key; filter it explicitly and carry it through every join.
NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.
DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.
CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.
LANG — a language key in a text table — one row per language.
Fields
3 fields · 3 key
The join key is all 3 key fields together — matching on any single one fans out. See composite keys in the quirks guide.
3 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | |
| Primary key | LGNUM | Warehouse Number | CHAR | 3 | |
| Primary key | TBNUM | Transfer Requirement Number | NUMC | 10 |
Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading LTBK on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
4 parameters not filled: <catalog>, <schema>, <MANDT>, <LGNUM>
-- ============================================================
-- Table : LTBK Transfer Requirement Header
-- Purpose: Column-selected read of LTBK — auto-generated from field metadata
-- Grain : One row per LGNUM + TBNUM
-- Notes : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
h.MANDT AS "Client",
h.LGNUM AS "Warehouse Number",
h.TBNUM AS "Transfer Requirement Number"
FROM <catalog>.<schema>.ltbk h
WHERE
h.MANDT = '<MANDT>'
-- AND h.LGNUM = '<LGNUM>'
ORDER BY h.LGNUM;Verified August 2026
Relationships
Diagram of 1-hop neighbors — join details below.
Join details
ON ltbk.TBNUM = ltbp.TBNUM
Transaction Codes That Use This Table
No t-code mappings populated for this table yet.