SAP Reference

T300

config S/4HANA status: Active

WM Warehouse Numbers

Notes

Enterprise-structure config for the warehouse number itself (assigned to a plant/storage location via T001L). Stays active on every S/4HANA warehouse path — EWM, decentralized EWM, or SAP Stock Room Management — since the number is what those paths are assigned onto, not an operational object any of them replace.

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.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Fields

3 fields · 2 key

3 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 3 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyLGNUMWarehouse Number / Warehouse ComplexCHAR3
REGKZRegion CodeCHAR3T646R

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 T300 on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <MANDT>, <LGNUM>

-- ============================================================
-- Table  : T300 WM Warehouse Numbers
-- Purpose: Column-selected read of T300 — auto-generated from field metadata
-- Grain  : One row per LGNUM
-- 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
  t.MANDT AS "Client",
  t.LGNUM AS "Warehouse Number / Warehouse Complex",
  t.REGKZ AS "Region Code"
FROM <catalog>.<schema>.t300 t
WHERE
  t.MANDT = '<MANDT>'
  -- AND t.LGNUM = '<LGNUM>'
ORDER BY t.LGNUM;

Verified August 2026

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • LTAKT300check table · N:1
    ON ltak.LGNUM = t300.LGNUM

Transaction Codes That Use This Table

No t-code mappings populated for this table yet.

Browse more WM tables

More Warehouse Management (Classic) tables