Skip to content
SAP Reference

MATDOC

transaction S/4HANA status: Active

Material Document (S/4HANA)

Identity
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

22 fields · 7 key

22 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. 22 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyKEY1Split GUID Part 1RAW4
Primary keyKEY2Split GUID Part 2RAW4
Primary keyKEY3Split GUID Part 3RAW5
Primary keyKEY4Split GUID Part 4RAW1
Primary keyKEY5Split GUID Part 5RAW1
Primary keyKEY6Split GUID Part 6RAW1
MBLNRNumber of Material DocumentCHAR10
MJAHRMaterial Document YearNUMC4
ZEILEItem in Material DocumentNUMC4
LINE_IDUnique Line IDINT410
PARENT_IDParent Line IDINT410
BWARTMovement TypeCHAR3T156
MATNRMaterial NumberCHAR18 / 40MARA
WERKSPlantCHAR4T001W
LGORTStorage LocationCHAR4T001L
CHARGBatch NumberCHAR10
MENGEQuantityQUAN13,3
SHKZGDebit/Credit IndicatorCHAR1
BUDATPosting Date in the DocumentDATS8
BLDATDocument Date in DocumentDATS8
SOBKZSpecial Stock IndicatorCHAR1T148

Lengths shown as ECC / S/4HANA where the extended material number applies.

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

Query parameters

3 parameters not filled: <catalog>, <schema>, <MANDT>

-- ============================================================
-- Table  : MATDOC Material Document (S/4HANA)
-- Purpose: Column-selected read of MATDOC — auto-generated from field metadata
-- Grain  : One row per KEY1 + KEY2 + KEY3 + KEY4 + KEY5 + KEY6
-- 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
  m.MANDT     AS "Client",
  m.KEY1      AS "Split GUID Part 1",
  m.KEY2      AS "Split GUID Part 2",
  m.KEY3      AS "Split GUID Part 3",
  m.KEY4      AS "Split GUID Part 4",
  m.KEY5      AS "Split GUID Part 5",
  m.KEY6      AS "Split GUID Part 6",
  m.MBLNR     AS "Number of Material Document",
  m.MJAHR     AS "Material Document Year",
  m.ZEILE     AS "Item in Material Document",
  m.LINE_ID   AS "Unique Line ID",
  m.PARENT_ID AS "Parent Line ID",
  m.BWART     AS "Movement Type",
  m.MATNR     AS "Material Number",
  m.WERKS     AS "Plant",
  m.LGORT     AS "Storage Location",
  m.CHARG     AS "Batch Number",
  m.MENGE     AS "Quantity",
  m.SHKZG     AS "Debit/Credit Indicator",
  m.BUDAT     AS "Posting Date in the Document",
  m.BLDAT     AS "Document Date in Document",
  m.SOBKZ     AS "Special Stock Indicator"
FROM <catalog>.<schema>.matdoc m
WHERE
  m.MANDT = '<MANDT>'
ORDER BY m.KEY1;

Verified August 2026

Released CDS views over this table

Released SAP standard VDM views that read over MATDOC. Prefer these over classic-table reads on S/4HANA where available.

Relationships

Diagram of 1-hop neighbors — join details below.

Transaction Codes That Use This Table

No t-code mappings populated for this table yet.

Browse more MM tables

More Materials Management tables