VD01 — Create Customer Master, Sales View Only

VD01 creates a customer master record scoped to sales: general data (name, address, communication) and sales area data (sales organization, distribution channel, division level settings such as pricing procedure inputs, order block, shipping conditions, and partner functions). It does not create or touch company code data at all - there is no screen for it in this transaction. The one structural fact that explains most confusion: SAP customer master is split into three independent views (general, company code, sales), each maintained by a different transaction or screen set, and VD01 guarantees only two of the three. A customer built purely through VD01 exists for sales purposes but has no accounting representation until someone separately maintains the company code view.

VD01 sits at the front of the order-to-cash chain, before any sales document can reference the customer as sold-to, ship-to, payer, or bill-to for a given sales area. It is reached for in organizations where SD and FI master data ownership are split - sales administration extends a customer into a new sales org or distribution channel without waiting on the accounting team, or a sandbox/test customer is needed quickly with no accounting relevance. In S/4HANA landscapes with Business Partner as the leading object, most production creation now goes through the BP transaction with a customer role, or a Fiori master data app; VD01 is still used for quick checks, legacy processes, or systems where full BP/CVI rollout has not happened.

In SE16 or SE16N, check KNA1 by customer number to confirm the general record and account group exist. Then check KNVV filtered on the same customer number plus sales organization, distribution channel, and division to confirm the sales area combination was actually saved - a missing row here is the reason a sales document rejects the customer or partner determination fails. Finally check KNB1 for the same customer and company code; if no row exists, the customer is sales-complete but accounting-incomplete, which explains billing release or credit management failures.

VD01 still exists and functions on S/4HANA, writing to the same underlying tables, but SAP's direction is Business Partner as the single leading object for customer and vendor data, synchronized through customer-vendor integration. Where CVI is active and enforced, VD01 usage may be restricted or redirected, and the recommended creation path is the BP transaction with a customer role or a Fiori master data application. Where CVI synchronization is not configured correctly, a customer created through VD01 can end up without a corresponding business partner record, causing errors in processes that expect BP data.

Functional SD or master data team owns account group configuration, field status groups, and partner determination setup; this is not a Basis issue unless authorization objects are blocking the transaction. A clean handover to FI or the master data team includes the customer number, the sales area combination created, the account group used, explicit confirmation of whether a company code view exists, and CVI/BP sync status on S/4HANA.

XD01 is the centralized creation transaction covering general, company code, and sales views in one pass, and is the transaction to compare against when a VD01-created customer is missing accounting data. VD02 and VD03 are the corresponding change and display transactions for the sales view once the customer exists. VK11 is worth reviewing alongside VD01 when pricing fails, since condition records depend on the sales area combination that VD01 establishes in KNVV. VOV8 is relevant when the sales document type's partner determination or account group requirements do not match what VD01 produced.