SAP SD Customer Master Sales Area Load Worksheet
The customer master has three layers: general, company code and sales area. SD owns the last one. This worksheet gathers the sales area data for each customer so the load file is complete before cutover.
| Customer no. | Name | Sales org | Dist. channel | Division | Shipping condition | Delivering plant | Incoterms | Incoterms location | Payment terms | Currency | Cust. pricing procedure | Acct assignment group | Tax class | Credit limit | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sales area data lives in table KNVV, one row per customer and sales area. Partner functions are held in KNVP and tax data in KNVI. Credit limits are held in credit management and shown here for planning only. In S/4HANA customers are maintained through business partners.
Need a customer data quality check before cutover?
Optional: ask Netray about read-only checks on legacy customer data.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Enter one row per customer and sales area. If a customer buys through two sales organisations, create two rows. Pick the shipping condition, delivering plant, incoterms and payment terms from your own reference lists. Export to Excel and send the sheet to the customers' account managers for confirmation before it goes to your load tool.
What each field drives
The shipping condition and loading group determine the shipping point. Incoterms and their location print on order confirmations and invoices, and drive export documents. Payment terms feed due date and cash discount. The customer pricing procedure and the sales document pricing procedure together select the pricing procedure. The account assignment group decides which revenue account is found in billing.
- Shipping condition and plant set the shipping point
- Customer pricing procedure helps pick the procedure
- Account assignment group drives revenue accounts
- Tax classification drives the tax code in billing
Reviewing the sheet
Filter by sales org and confirm every row has a delivering plant, incoterms and payment terms. Missing values will either stop order entry or default silently, and silent defaults create wrong invoices. Check currency against the sales organisation and credit limit against the credit control area. Compare the number of rows to the number of active customers per sales area in the legacy system.
Common mistakes
Teams migrate general data but forget sales area data, copy all customers into every sales area, leave account assignment group blank, or load incoterms that conflict with the shipping condition. Another trap is partner functions: each ship-to needs its own master record and a link in the sold-to. Test a handful of customers through VA01 before loading all of them.
Frequently Asked Questions
Which table stores customer sales area data?
Table KNVV holds one row per customer, sales organisation, distribution channel and division. General data is in KNA1, company code data in KNB1 and partner functions in KNVP.
Do I need a row for every division?
Only if your configuration requires it. Many companies use a common division for master data and handle product divisions in the material master and document. Check your sales area design.
How does S/4HANA change customer creation?
In S/4HANA the business partner transaction BP is the leading entry point, and customer roles are added to the partner. Customer data is still stored for SD use, but loads normally use the migration cockpit or APIs.
Is the credit limit part of the sales area data?
No. Credit limits live in credit management, either in the classic credit control area setup or in SAP Credit Management. The column here is for planning and approval during data collection.
For migrations, Netray can compare legacy customer data with the target structure and flag missing or inconsistent sales area fields, read-only.
Related Tools
SAP SD Partner Determination Design Template
Document your partner functions, partner determination procedures and sources per document level, then export a design page for review.
SAPSAP SD Condition Record Load Worksheet
Prepare price and discount condition records row by row, check the per-unit value and export to Excel for LSMW, migration cockpit or manual VK11 entry.
SAPSAP SD Copy Control Design Worksheet
Plan every copy control path in your order to cash flow: source document, target document, item category, copy requirements and pricing type.
SAPSAP SD Transaction Codes Reference
A searchable list of common SAP sales and distribution transaction codes, grouped by process area, for daily use and onboarding.