XD01 — Create Customer Centrally

XD01 creates a new customer master record by walking through three data segments in sequence: general data (name, address, control data, shared across the client), company code data (reconciliation account, payment terms, dunning, tied to one company code), and sales area data (pricing procedure inputs, shipping conditions, billing schedules, tied to one combination of sales organization, distribution channel, and division). The structural fact that explains most confusion: these segments live in separate tables and are optional independently of each other. XD01 is a convenience wrapper, not a single atomic write. A customer can be saved with general data only, or general plus company code but no sales area, depending on which screens were completed and how the account group is configured to skip or require them. The customer then 'exists' for some purposes and not others.

XD01 is reached for at true customer onboarding, before the first sales order can be created against that customer, or during data load projects where a customer needs general, company code, and sales area data populated together. It is chosen over VD01 when company code (FI) data also needs to be created in the same pass rather than by the FI team separately. It is chosen over simply extending an existing customer (XD02) when the customer number does not exist at all yet. On S/4HANA with the business partner model active, this route may be technically retired or redirected in favor of the business partner creation transaction, with XD01 either blocked or running as a compatibility layer underneath it; check which model the client is on before assuming XD01 is the live path.

In SE16 on KNA1, filter by customer number to confirm the record exists at all and check the creation date and account group. If it exists there but a sales order rejects the customer, go to KNVV and filter by the same customer number plus the exact sales organization, distribution channel, and division from the order; a missing row there is the direct cause. Cross-check KNB1 by company code the same way if the failure is on billing or credit management rather than order entry, since those often read company code data instead of sales area data.

On systems running the business partner model, the customer master is technically a view onto the business partner record, and XD01 either runs as a compatibility wrapper calling business partner logic underneath or is deliberately blocked in favor of creating the business partner directly. Where it is blocked, the equivalent path is the business partner creation transaction with the customer role assigned, followed by the same three-segment data entry conceptually reorganized under business partner screens. Where XD01 still runs, the underlying tables (KNA1, KNB1, KNVV) are unchanged.

Functional ownership sits with SD or FI master data teams depending on which segment is at issue: SD for sales area and partner function problems, FI for company code and dunning problems. ABAP involvement is only needed if a custom master data check or enhancement is rejecting the save. A good handover includes the customer number, account group, the exact sales area or company code attempted, and the precise error message and screen.

XD02 and XD03 cover changing and displaying the same central record and are the natural next stops when a sales area needs adding to an existing customer rather than a new number. VD01, VD02, and VD03 are the sales-area-only equivalents, useful when company code data is owned by a separate FI team and should not be touched from the SD side. VA01 is the downstream test: after any XD01 extension, attempting a sales order in the exact sales area confirms the master data is actually usable, not just saved.