queryviz
tables/relationship path
open in builder
T002
SPRAS
KNA1
KUNNR
TVKO
VKORG
KNVP

KNVP

customer master - partner functions per sales area
sd13f · 7k · 6r
Unchanged in S/4
KNVP stores customer-level partner function assignments: which business partners play which roles (sold-to, ship-to, bill-to, payer, sales rep, etc.) for each customer in each sales area. In S/4HANA, KNVP is retained as a compatibility table. In the full Business Partner model, partner functions are managed through BP relationships (BUT021), but KNVP continues to be populated for SD document partner determination.
key differences:
  • •KNVP structure unchanged in S/4HANA and continues to be used for SD partner determination in all SD transactions
  • •In the strategic S/4 BP model, KNVP data is derived from BP relationship (BUT021) records
  • •KNA1.KUNNR = KNVP.KUNNR relationship is preserved — KNA1 continues as a compatibility view in S/4

fields (13)

fieldtypelengthkeydescription
KUNNRchar10pkcustomer number (sold-to party)
MANDTclnt3pkclient
PARVWchar2pkpartner function (ag=sold-to, we=ship-to, re=bill-to, rg=payer, sp=sales rep)
PARZAnumc3pksequential number for partner function (allows multiple partners per function)
SPARTchar2pkdivision
VKORGchar4pksales organization
VTWEGchar2pkdistribution channel
DEFPAchar1default partner flag (x=this is the default partner for this function)
KNREFchar30customer description of partner (plant, storage location)
KUNN2char10customer number of partner (the partner assigned to this function)
LIFNRchar10vendor number
PARNRnumc10number of contact person
PERNRnumc8personnel number

relationships (6)

configuration

reference to config tables

references
TVKO
VKORGVKORG
N:1
TSPA
SPARTSPART
N:1
TPAR
PARVWPARVW
N:1
TVTW
VTWEGVTWEG
N:1
master lookup

reference to master data

references
KNA1
KUNNRKUNNR
N:1
LFA1
LIFNRLIFNR
N:1
queryviz.iobuy me a coffee
s/4 migrationpricingcompareaboutcontactprivacyterms