SAP WM and EWM Warehouse Tables Reference
When you debug a stuck transfer order or build a stock report, the first question is which table holds the data. This reference lists the classic WM tables, the shared delivery and handling unit tables, and the main EWM tables, with a one-line description each.
| System | Table | What it holds | Typical key fields |
|---|---|---|---|
WM | T300 | Warehouse numbers | MANDT, LGNUM |
WM | T301 | Storage types | MANDT, LGNUM, LGTYP |
WM | T302 | Storage sections | MANDT, LGNUM, LGTYP, LBERS |
WM | T320 | Assignment of plant and IM storage location to a warehouse number | MANDT, WERKS, LGORT |
WM | T331 | Storage type control (putaway and removal strategy settings per storage type) | MANDT, LGNUM, LGTYP |
WM | LAGP | Storage bin master data | MANDT, LGNUM, LGTYP, LGPLA |
WM | LQUA | Quants (stock per bin, material, batch, special stock) | MANDT, LGNUM, LQNUM |
WM | LEIN | Storage units (pallets and containers managed in WM) | MANDT, LGNUM, LENUM |
WM | MLGN | Material master data per warehouse number | MANDT, MATNR, LGNUM |
WM | MLGT | Material master data per storage type | MANDT, MATNR, LGNUM, LGTYP |
WM | LTAK | Transfer order header | MANDT, LGNUM, TANUM |
WM | LTAP | Transfer order items | MANDT, LGNUM, TANUM, TAPOS |
WM | LTBK | Transfer requirement header | MANDT, LGNUM, TBNUM |
WM | LTBP | Transfer requirement items | MANDT, LGNUM, TBNUM, TBPOS |
WM | LINV | Physical inventory record for WM bins | MANDT, IVNUM |
Shared | LIKP | Delivery header (SD and LE) | MANDT, VBELN |
Shared | LIPS | Delivery items | MANDT, VBELN, POSNR |
Shared | VEKP | Handling unit header | MANDT, VENUM |
Shared | VEPO | Handling unit items | MANDT, VENUM, VEPOS |
Shared | MARD | Stock by plant and storage location (inventory management) | MANDT, MATNR, WERKS, LGORT |
EWM | /SCWM/ORDIM_O | Open warehouse tasks | Warehouse number, task number |
EWM | /SCWM/ORDIM_C | Confirmed warehouse tasks | Warehouse number, task number |
EWM | /SCWM/WHO | Warehouse orders (groups of warehouse tasks assigned to a resource) | Warehouse number, warehouse order |
EWM | /SCWM/QUAN | Quants (stock per bin, product, batch, owner) | Warehouse number, quant ID |
EWM | /SCWM/LAGP | Storage bin master data | Warehouse number, storage bin |
EWM | /SCWM/HUHDR | Handling unit header | Warehouse number, HU ID |
EWM | /SCWM/WAVEHDR | Wave header | Warehouse number, wave number |
EWM | /SCWM/WAVEITM | Wave items (warehouse request items assigned to a wave) | Warehouse number, wave number, item |
EWM | /SCDL/DB_PROCH_I | Inbound delivery header (delivery processing in EWM) | Document ID |
EWM | /SCDL/DB_PROCH_O | Outbound delivery order header (delivery processing in EWM) | Document ID |
Descriptions are paraphrased. Key fields are the typical ones; always confirm exact field names and keys for your release in SE11 or SE16N before writing code. EWM table structures differ between embedded EWM in S/4HANA and decentralized EWM.
Ask your SAP warehouse data in plain language
Optional: a short call on connecting a read-only assistant to your WM or EWM data, on your own servers.
Optional. The tool and every export work without this. No spam.
How to use the table list
Type a table name or a word such as quant, wave or handling unit into the search box to filter rows. The System column tells you whether the table belongs to classic Warehouse Management (WM), to Extended Warehouse Management (EWM) or is shared with SD and logistics execution. Export to Excel if you want to paste the list into a technical specification or a data migration plan. Use SE16N for a quick look at contents, but remember that large tables such as LQUA and LTAP should always be filtered by warehouse number.
WM versus EWM data models
Classic WM is built around the transfer order (LTAK and LTAP), the quant (LQUA) and the storage bin (LAGP). EWM replaces the transfer order with warehouse tasks and warehouse orders, keeps stock as quants in its own tables and uses delivery processing from the SCDL framework. A frequent mistake in migration projects is assuming a one to one table mapping. A WM transfer order item becomes a warehouse task, but the grouping of tasks into warehouse orders is new and has no WM equivalent.
- WM stock: LQUA, with LAGP for bins
- EWM stock: /SCWM/QUAN, with /SCWM/LAGP for bins
- WM movement: LTAK and LTAP
- EWM movement: /SCWM/ORDIM_O and /SCWM/ORDIM_C
Reading the results and common mistakes
Open and confirmed documents are split in EWM: a warehouse task lives in ORDIM_O until it is confirmed and then moves to ORDIM_C. If you report on throughput, read both tables. In WM, an unconfirmed transfer order item has the confirmation indicator PQUIT blank in LTAP, while confirmed items carry an X. Another common mistake is joining LQUA to MARD without allowing for stock that is in transit or posted in interim storage types such as 902 and 904 style bins, which causes small differences against inventory management.
Frequently Asked Questions
Which table shows current stock in a WM bin?
LQUA holds quants, one row per material, batch and special stock combination in a bin. LAGP holds the bin itself, with its capacity and blocking indicators. Join the two on warehouse number, storage type and bin to see what is stored where.
Where do I find open warehouse tasks in EWM?
Open warehouse tasks sit in /SCWM/ORDIM_O and move to /SCWM/ORDIM_C when confirmed. Warehouse orders that group tasks for a resource are in /SCWM/WHO. The warehouse monitor, transaction /SCWM/MON, reads all of these for you.
Can I use SE16N on these tables in production?
Technically yes if you have the authorisation, but many companies restrict it. Prefer a standard report, the warehouse monitor or an approved ABAP report. Always filter by warehouse number to avoid long running queries.
Are the tables the same in S/4HANA?
Classic WM tables still exist in S/4HANA but WM is on the path to being replaced by embedded EWM. Embedded EWM uses the /SCWM/ tables in the same system. Check the simplification list for your target release.
If you want to ask your warehouse data questions in plain language instead of writing joins across these tables, Netray can connect a read-only assistant to your SAP data on your own infrastructure.
Related Tools
SAP WM and EWM Transaction Codes Reference
Look up the transaction code you need for transfer orders, bins, stock reports, physical inventory and the EWM monitor.
SAPSAP WM to EWM Terminology Map
See what each classic WM object is called in EWM and what changes in behaviour, in one searchable table.
SAPSAP WM Open Transfer Order ABAP SELECT Generator
Fill in the warehouse number, storage types and age and get a ready ABAP report for unconfirmed transfer orders.
SAPSAP WM Bin Stock LQUA ABAP Report Generator
Build an ABAP query on LQUA that lists stock by bin, flags old stock and counts quants per bin.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)