KNVV table — Customer Master Sales Area Data

One row in KNVV represents the sales-area-specific view of a customer: a unique combination of customer number, sales organization, distribution channel and division. This is the segment SAP populates when a customer is extended to a new sales area beyond the general data in KNA1. It carries everything a sales document needs that is not company-code or general-data related: order, delivery and billing blocks, the currency used for that sales area, incoterms, payment terms, the customer's pricing procedure assignment, customer group, sales district, shipping condition and account assignment group for revenue determination. A customer can exist in KNA1 with no corresponding KNVV row at all, in which case no sales order, delivery or billing document can reference that customer in that sales area.

Always restrict by MANDT implicitly and always select on KUNNR together with VKORG, VTWEG and SPART as a set, not KUNNR alone. Selecting on KUNNR alone returns one row per sales area the customer has ever been extended to, which is misleading if the incident is specific to one sales channel. The table is not as large as document tables like VBAP, but scanning it without the sales area key still returns noise across every division and channel a customer participates in. When comparing customers, restrict to the same VKORG/VTWEG/SPART combination before drawing any conclusion, since blocks and terms are set independently per sales area.

Symptom: order creation fails with a message that the customer is not defined for the sales area. Select KNVV where KUNNR equals the customer and VKORG, VTWEG, SPART equal the order's sales area. No row returned confirms the customer was never extended to that sales area, which is a master data gap, not a document error. If a row exists, check LOEVM for the deletion flag and AUFSD, LIFSD, FAKSD for active blocks before assuming the extension itself is faulty.

KNVV is retained in S/4HANA with its structure intact; sales area segment fields have not been restructured. Customer maintenance is done through the business partner transaction rather than the legacy customer transactions, but the sales area data entered there is still persisted into KNVV underneath. No functional replacement table exists for this segment; it remains the source for sales-area-specific customer attributes in both ECC and S/4HANA.

Sales area segment configuration and content is typically owned by the master data governance team in coordination with the SD functional consultant responsible for the affected sales organization. Company code segment questions belong to the finance/credit team against KNB1, not to the sales team. Order desk or business users raising a missing-extension incident should route it to master data governance rather than treating it as an order configuration defect.

KNA1 holds the general data shared across all sales areas; KNB1 holds company code data; KNVP holds partner functions per sales area; KNVI holds tax classification per sales area. VBAK is the sales document header that validates against the sales area extension in KNVV. Customer master maintenance, whether through the business partner transaction or legacy customer transactions, is what writes and updates KNVV.