tables/relationship path

open in builder

TSPA

SPART

T001L

LGORT

TVKO

KUNNR

KNA1

KUNNR

KNVK

customer master - contact persons

sd19f · 3k · 1r

Replaced by BUT021

KNVK stored customer contact persons in ECC — a dedicated table for individual contacts at customer organizations (name, phone, department, function). In S/4HANA, contact persons are modeled as Business Partners with a relationship to the customer BP. KNVK is replaced by BUT021 where a contact person BP is related to the customer BP via relationship type CRMH01 (contact person). KNVK data is migrated to BUT000/BUT021 during S/4HANA conversion. The transaction VD02/XD02 contact tab still works in S/4 but writes to the BP model.

key differences:

•KNVK stored contact persons as sub-records of KNA1; in S/4HANA each contact person is a full Business Partner (BUT000) in their own right
•KNVK was customer-specific; BUT021 handles contact relationships for both customers and vendors uniformly
•Contact person communication data (phone, email) moves from KNVK fields to BP communication infotypes (BUT054, ADR6)
•KNVK had no time-dependency; BUT021 is fully time-dependent (DATE_FROM/DATE_TO) enabling relationship history tracking
•Custom code or BAPIs reading KNVK for contact lookups must be rewritten to query BUT021 + BUT000

fields (19)

field	type	length	key	description
`KUNNR`	char	10	pk	customer number
`MANDT`	clnt	3	pk	client
`PARNR`	char	10	pk	contact person number (sequential identifier)
`ABTNR`	char	4		department number at customer
`ABTPA`	char	12		contact person's department at customer
`ADRND`	char	10		business address
`ADRNP`	char	10		home address
`ANRED`	char	4		salutation (0001=mr., 0002=ms., 0003=company)
`NAME1`	char	35		last name of contact person
`NAMEV`	char	35		first name of contact person
`ORT01`	char	35		city
`PAFKT`	char	2		function of contact person (e.g., 01=purchasing, 02=finance, 03=management)
`PARGE`	char	1		partner's gender
`PARVO`	char	1		partner's authority
`PAVIP`	char	1		vip partner
`SMTPADR`	char	241		email address
`TELF1`	char	16		telephone number (primary)
`TELFX`	char	31		fax number
`UEPAR`	numc	10		higher-level partner

relationships (1)

master lookup

reference to master data

references

KNA1

KUNNRKUNNR

N:1

queryviz

tables/relationship path

SPART

LGORT

KUNNR

KUNNR

KNVK

customer master - contact persons

sd19f · 3k · 1r

Replaced by BUT021

key differences:

•KNVK stored contact persons as sub-records of KNA1; in S/4HANA each contact person is a full Business Partner (BUT000) in their own right
•KNVK was customer-specific; BUT021 handles contact relationships for both customers and vendors uniformly
•Contact person communication data (phone, email) moves from KNVK fields to BP communication infotypes (BUT054, ADR6)
•KNVK had no time-dependency; BUT021 is fully time-dependent (DATE_FROM/DATE_TO) enabling relationship history tracking
•Custom code or BAPIs reading KNVK for contact lookups must be rewritten to query BUT021 + BUT000

fields (19)

field	type	length	key	description
`KUNNR`	char	10	pk	customer number
`MANDT`	clnt	3	pk	client
`PARNR`	char	10	pk	contact person number (sequential identifier)
`ABTNR`	char	4		department number at customer
`ABTPA`	char	12		contact person's department at customer
`ADRND`	char	10		business address
`ADRNP`	char	10		home address
`ANRED`	char	4		salutation (0001=mr., 0002=ms., 0003=company)
`NAME1`	char	35		last name of contact person
`NAMEV`	char	35		first name of contact person
`ORT01`	char	35		city
`PAFKT`	char	2		function of contact person (e.g., 01=purchasing, 02=finance, 03=management)
`PARGE`	char	1		partner's gender
`PARVO`	char	1		partner's authority
`PAVIP`	char	1		vip partner
`SMTPADR`	char	241		email address
`TELF1`	char	16		telephone number (primary)
`TELFX`	char	31		fax number
`UEPAR`	numc	10		higher-level partner

relationships (1)

master lookup

reference to master data

references

KNA1

KUNNRKUNNR

N:1

KNVK | SD table