VD01 — VD01 — Create Customer Sales-Area Data (ECC; redirects to BP in S/4HANA)
VD01 is the classic ECC transaction for creating customer general and sales-area data without creating the company-code accounting view. In SAP S/4HANA, SAP redirects VD01 to transaction BP; customer master data is created through Business Partner customer roles and synchronized to customer views by Customer/Vendor Integration.
VD01 is the SD-restricted customer creation transaction, writing general and sales-area data but deliberately excluding the accounting (company code) view. This page covers the split-view structure that causes most of the confusion, the tables the save actually populates, and the diagnostic sequence for the classic symptom: a customer that works in VA01 but blocks at billing or credit check.
Published 20 Sept 2026· 1,175 words
Esta página ainda não está disponível em português.
Purpose
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.
When it is used
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.
How to use it in practice
- Call VD01 and enter the account group, sales organization, distribution channel, and division; optionally supply a reference customer to copy from.
- On the general data screen, enter address, search terms, and communication data (skipped entirely if the customer already exists and only a new sales area is being added).
- Move through the sales area tabs: sales (currency, price group, customer statistics group), shipping (shipping conditions, delivery priority), billing (payment terms, tax classification via KNVI), and partner functions.
- Confirm partner functions are complete for the sales area - sold-to is mandatory, others default from the account group but should be checked.
- Save. The system assigns an internal or external number depending on the account group's number range; note the number for handover if company code data still needs to be added separately.
Key data objects
- KNA1 - general data: one row per customer, name, address, country, account group, VAT registration; created if it did not already exist.
- KNVV - sales area data: one row per customer/sales org/distribution channel/division combination; holds pricing, shipping, and billing control fields used by VA01 pricing and delivery determination.
- KNVP - partner functions per sales area: links sold-to, ship-to, payer, and bill-to numbers to the sales area combination.
- KNVI - tax classification per sales area and departure country, read during pricing tax determination.
- KNB1 - company code data is NOT written by VD01; its absence is the source of most downstream errors.
How to prove it in the data
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.
ECC vs S/4HANA
SAP's S/4HANA 2025 simplification list states that VD01, VD02 and VD03 are not available as separate customer-master user interfaces and are redirected to BP. Use Business Partner roles such as FLCU00/FLCU01 for current S/4HANA customer maintenance. VD01 remains useful as an ECC search term and migration reference.
Common pitfalls and how to diagnose them
- Missing company code data: the customer processes fine through order creation and delivery but fails at billing release, automatic credit check, or FI posting with an incomplete master data error. Check KNB1 first before investigating pricing or delivery logic; this is the single most common false lead in VD01-related tickets.
- Duplicate customer creation: because VD01 allows sales staff to create a new customer number even when the business partner already exists centrally, duplicate KNA1 records with slightly different address data are common. Search by name and address (or matching/duplicate check tools if active) before assuming a new number is genuinely needed.
- Wrong account group: determines the number range, field status, and which partner functions are mandatory. A customer created under the wrong account group may be missing fields the sales document needs later; the fix is not to edit the existing record's account group (not changeable) but to create it correctly and archive the wrong one.
- Reference-copy contamination: copying from a reference customer carries over tax classification, partner functions, or pricing group values that are wrong for the new customer's actual region or business, causing silent pricing or tax determination errors that surface much later in billing.
- Sales area combination missing for pricing: if a condition record (maintained via VK11) is set up for a sales area that was never actually created for this customer in KNVV, pricing in VA01 fails with a missing sales area error that looks like a condition record problem but is actually a master data gap.
- Silent segregation-of-duty gap: using VD01 specifically to bypass a slower FI-owned creation process produces no system error at save time; the failure only appears downstream at credit check or billing release, well after the sales order was created, making root cause harder to trace back to the original master data gap.
Whose problem this is
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.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/vd01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.