Skip to content
SAP Reference

MKPF

transaction S/4HANA status: Replaced · Compat View

Compatibility view: the classic table name is redirected to a view over the new persistence

Header: Material Document

Notes

In S/4HANA replaced by MATDOC; exists as CDS compatibility view

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.
Used in the library

Fields

18 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.

18 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. 18 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3T000
Primary keyMBLNRNumber of Material DocumentCHAR10
Primary keyMJAHRMaterial Document YearNUMC4
VGARTTransaction/Event TypeCHAR2
BLARTDocument TypeCHAR2
BLAUMDocument Type of Revaluation DocumentCHAR2
BLDATDocument Date in DocumentDATS8
BUDATPosting Date in the DocumentDATS8
CPUDTDay On Which Accounting Document Was EnteredDATS8
CPUTMTime of EntryTIMS6
AEDATDate of Last ChangeDATS8
USNAMUser NameCHAR12
TCODE2Transaction CodeCHAR20
XBLNRReference Document NumberCHAR16
BKTXTDocument Header TextCHAR25
XABLNGoods Receipt/Issue Slip NumberCHAR10
LFSNRDelivery Note NumberCHAR16
FRBNRNumber of Bill of Lading at Time of Goods ReceiptCHAR16

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 MKPF 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  : MKPF Header: Material Document
-- Purpose: Column-selected read of MKPF — auto-generated from field metadata
-- Grain  : One row per MBLNR + MJAHR
-- 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.MBLNR  AS "Number of Material Document",
  h.MJAHR  AS "Material Document Year",
  h.VGART  AS "Transaction/Event Type",
  h.BLART  AS "Document Type",
  h.BLAUM  AS "Document Type of Revaluation Document",
  h.BLDAT  AS "Document Date in Document",
  h.BUDAT  AS "Posting Date in the Document",
  h.CPUDT  AS "Day On Which Accounting Document Was Entered",
  h.CPUTM  AS "Time of Entry",
  h.AEDAT  AS "Date of Last Change",
  h.USNAM  AS "User Name",
  h.TCODE2 AS "Transaction Code",
  h.XBLNR  AS "Reference Document Number",
  h.BKTXT  AS "Document Header Text",
  h.XABLN  AS "Goods Receipt/Issue Slip Number",
  h.LFSNR  AS "Delivery Note Number",
  h.FRBNR  AS "Number of Bill of Lading at Time of Goods Receipt"
FROM <catalog>.<schema>.mkpf h
WHERE
  h.MANDT = '<MANDT>'
ORDER BY h.MBLNR;

Verified August 2026

More query patterns: MB01 MB1A MB1B

Released CDS views over this table

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

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

  • MKPFMSEGheader item · 1:N
    ON mkpf.MBLNR = mseg.MBLNR

Transaction Codes That Use This Table

More Materials Management tables