SAP Reference

KNA1

master Active

General Data in Customer Master

Identity

Module: SD · Sales & DistributionType: transparent

S/4HANA

Notes

Business Partner (BUT000) is the lead object in S/4HANA; KNA1 persists and is kept in sync via CVI. Create/update via Business Partner transactions

What the badges mean

Active

Active and unchanged in S/4HANA.

Deprecated

Still readable today, but no longer SAP's strategic path — plan around it.

Replaced

Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).

Migrating to IBP

Planning scope is moving from APO toward IBP.

Active (StRM) · Replaced (EWM)

Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.

Replaced · Compat View

Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.

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

KPI definitions

K-01OTIF — On Time In Full

Dashboard patterns

D-02OTIF / Customer Service

Cross-ERP guides

GuideMedallion Layer Contracts for ERP Data

GuideUnity Catalog Governance Patterns

Fields

46 fields · 2 key

46 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. 46 fields.
Key	Field	Description	Type	Length	References
Primary key	MANDT	Client	CLNT	3	T000
Primary key	KUNNR	Customer Number	CHAR	10
	LAND1	Country Key	CHAR	3	T005
	NAME1	Name 1	CHAR	35
	NAME2	Name 2	CHAR	35
	ORT01	City	CHAR	35
	PSTLZ	Postal Code	CHAR	10
	REGIO	Region (State, Province, County)	CHAR	3
	SORTL	Sort Field	CHAR	10
	STRAS	House Number and Street	CHAR	35
	TELF1	First Telephone Number	CHAR	16
	TELFX	Fax Number	CHAR	31
	XCPDK	Indicator: Is the Account a One-Time Account?	CHAR	1
	ADRNR	Address	CHAR	10
	MCOD1	Search Term for Matchcode Search	CHAR	25
	MCOD2	Search Term 2 for Matchcode Search	CHAR	25
	MCOD3	Search Term 3 for Matchcode Search	CHAR	25
	ANRED	Title	CHAR	15
	AUFSD	Order Block (Sales Area)	CHAR	2
	BAHNE	Express Train Station	CHAR	25
	BAHNS	Train Station	CHAR	25
	BBBNR	International location number (part 1)	NUMC	7
	BBSNR	International Location Number (Part 2)	NUMC	5
	BEGRU	Authorization Group	CHAR	4
	BRSCH	Industry Key	CHAR	4
	ERDAT	Date on Which Record Was Created	DATS	8
	ERNAM	Name of Person Who Created the Object	CHAR	12
	KTOKD	Customer Account Group	CHAR	4
	LIFNR	Account Number of Vendor or Creditor	CHAR	10	LFA1
	LIFSD	Central Delivery Block for the Customer	CHAR	2
	LOCCO	City Coordinates	CHAR	10
	LOEVM	Central Deletion Flag for Master Record	CHAR	1
	SPRAS	Language Key	LANG	1
	SPERR	Central Posting Block	CHAR	1
	STCD1	Tax Number 1	CHAR	16
	STCD2	Tax Number 2	CHAR	11
	STKZA	Indicator: Business Partner Is Subject to Equalization Tax	CHAR	1
	STKZU	Indicator: Liable for VAT?	CHAR	1
	STCEG	VAT Registration Number	CHAR	20
	KONZS	Group Key	CHAR	10
	VBUND	Company ID of Trading Partner	CHAR	6
	UMJAH	Year for Which Sales Are Given	NUMC	4
	UWAER	Currency of Sales Figure	CUKY	5	TCURC
	UMSA1	Annual Sales	CURR	15,2
	PERIV	Fiscal Year Variant (Company)	CHAR	2
	NIELS	Nielsen ID	CHAR	2

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

Query parameters

CatalogSchemaClient (MANDT)Customer (KUNNR)

Include optional filters (1)

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

-- ============================================================
-- Table  : KNA1 General Data in Customer Master
-- Purpose: Column-selected read of KNA1 — auto-generated from field metadata
-- Grain  : One row per KUNNR
-- 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
  c.MANDT AS "Client",
  c.KUNNR AS "Customer Number",
  c.LAND1 AS "Country Key",
  c.NAME1 AS "Name 1",
  c.NAME2 AS "Name 2",
  c.ORT01 AS "City",
  c.PSTLZ AS "Postal Code",
  c.REGIO AS "Region (State, Province, County)",
  c.SORTL AS "Sort Field",
  c.STRAS AS "House Number and Street",
  c.TELF1 AS "First Telephone Number",
  c.TELFX AS "Fax Number",
  c.XCPDK AS "Indicator: Is the Account a One-Time Account?",
  c.ADRNR AS "Address",
  c.MCOD1 AS "Search Term for Matchcode Search",
  c.MCOD2 AS "Search Term 2 for Matchcode Search",
  c.MCOD3 AS "Search Term 3 for Matchcode Search",
  c.ANRED AS "Title",
  c.AUFSD AS "Order Block (Sales Area)",
  c.BAHNE AS "Express Train Station",
  c.BAHNS AS "Train Station",
  c.BBBNR AS "International location number (part 1)",
  c.BBSNR AS "International Location Number (Part 2)",
  c.BEGRU AS "Authorization Group",
  c.BRSCH AS "Industry Key",
  c.ERDAT AS "Date on Which Record Was Created",
  c.ERNAM AS "Name of Person Who Created the Object",
  c.KTOKD AS "Customer Account Group",
  c.LIFNR AS "Account Number of Vendor or Creditor",
  c.LIFSD AS "Central Delivery Block for the Customer",
  c.LOCCO AS "City Coordinates",
  c.LOEVM AS "Central Deletion Flag for Master Record",
  c.SPRAS AS "Language Key",
  c.SPERR AS "Central Posting Block",
  c.STCD1 AS "Tax Number 1",
  c.STCD2 AS "Tax Number 2",
  c.STKZA AS "Indicator: Business Partner Is Subject to Equalization Tax",
  c.STKZU AS "Indicator: Liable for VAT?",
  c.STCEG AS "VAT Registration Number",
  c.KONZS AS "Group Key"
  -- … plus 6 more columns — full list in the Fields section above
FROM <catalog>.<schema>.kna1 c
WHERE
  c.MANDT = '<MANDT>'
  -- AND c.KUNNR = '<KUNNR>'
ORDER BY c.KUNNR;

Verified August 2026

More query patterns: XD01 XD02 XD03

Released CDS views over this table

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

I_CustomerCustomer master data — the released read model over KNA1, sourced from the Business Partner.

Relationships

Diagram of 1-hop neighbors — join details below.

Join details

VBAKKNA1foreign key · N:1
ON vbak.KUNNR = kna1.KUNNR
BSIDKNA1foreign key · N:1
ON bsid.KUNNR = kna1.KUNNR
BSADKNA1foreign key · N:1
ON bsad.KUNNR = kna1.KUNNR
KNB1KNA1foreign key · N:1
ON knb1.KUNNR = kna1.KUNNR
KNVVKNA1foreign key · N:1
ON knvv.KUNNR = kna1.KUNNR

KNA1

Fields

Boilerplate SQL

Released CDS views over this table

Relationships

Join details

Transaction Codes That Use This Table

Primary t-codes

Secondary t-codes

More Sales & Distribution tables