What a SAP customer master report shows
A SAP customer master report lists your customers with their general data (table KNA1), company code data (KNB1), sales area data (KNVV) and partner functions (KNVP), joined on the customer number. PostNow.ai ships it as Customer Master Sales 360 in its Report Library: open it in Excel, set filters such as sales organisation or country, and run.
SAP shows a customer one record at a time, spread over several screens and tables. A customer master report puts them side by side so you can review payment terms, sales areas, partners and reconciliation accounts across thousands of customers. This page covers reading and reporting customer master data. To create or change customers from Excel, see customer master upload (XD01); for ownership and governance of master data, see SAP master data management.
SAP customer master tables: KNA1, KNB1, KNVV, KNVP
The PostNow.ai customer master report reads the same customer master tables in SAP that XD03 displays. Each table holds one level of the customer, and its key tells you how many rows a customer has there.
| Table | Level and key | What it holds | Typical fields |
|---|---|---|---|
KNA1 | General data, one row per customer (KUNNR) | Name, address reference, country, tax numbers, account group, central blocks and deletion flag | NAME1, ORT01, LAND1, STCD1, KTOKD, ADRNR, LOEVM, ERDAT |
KNB1 | Company code data, one row per customer and company code (KUNNR, BUKRS) | Accounting view: reconciliation account, FI payment terms, payment methods, posting block | AKONT, ZTERM, ZWELS, SPERR, LOEVM |
KNVV | Sales area data, one row per customer and sales area (KUNNR, VKORG, VTWEG, SPART) | Sales view: customer group, sales office, sales payment terms, Incoterms, shipping conditions, order block | KDGRP, VKBUR, VKGRP, ZTERM, INCO1, VSBED, AUFSD |
KNVP | Partner functions, several rows per customer and sales area (key adds PARVW, PARZA) | Sold-to, ship-to, bill-to and payer assignments | PARVW, KUNN2 |
ADRC | Address, joined through KNA1-ADRNR | Full postal address, street, postal code, region | STREET, POST_CODE1, REGION |
TVKOT, TSPAT | Text tables, one row per language | Sales organisation and division names | VTEXT |
- Payment terms exist twice.
KNB1-ZTERMis the accounting term used for FI postings;KNVV-ZTERMis the sales term that sales orders copy. They can differ, so a report should say which one it shows. - Rows multiply by level. A customer with two sales areas and four partner functions per area produces eight rows once KNVV and KNVP are joined, and twice that if it is extended to two company codes. That is correct data, not duplicates.
- The customer number is stored with leading zeros.
KUNNRis ten characters with the ALPHA conversion, so customer 200371 is0000200371in the table. Excel lookups against an unpadded list fail silently. - Credit data lives elsewhere. Classic credit limits are in
KNKKper credit control area, not in the customer master tables above; see credit limit mass update (FD32).
Transactions to display customer master data
PostNow.ai gives you the list; SAP's customer master t-codes give you one record at a time. These are the transactions to display customer master data in SAP, and what each one is good for.
| Transaction or report | What it shows | Use it for |
|---|---|---|
| PostNow.ai: Customer Master Sales 360 | Every customer in your selection with general, sales area, partner and reconciliation account data, in Excel | Lists, reviews, audits, clean-up before a migration |
XD03 (ECC) | One customer centrally: general, company code and sales area views | Checking a single customer in full |
FD03 (ECC) | One customer: general and company code data | Accounting questions: reconciliation account, payment terms, dunning |
VD03 (ECC) | One customer: general and sales area data | Sales questions: customer group, shipping conditions, partners |
BP (S/4HANA) | The business partner with its customer roles | Displaying and maintaining customers in S/4HANA, where XD03 redirects to BP |
S_ALR_87012179 | Customer List (program RFDKVZ00), a standard FI list per company code | A quick accounting-side list with address and control data |
XD04 | Change documents for one customer | Who changed which field, and when |
SE16N / SQVI | One table, or a QuickViewer join you build yourself | Ad-hoc lists when you know the tables (next section) |
Is there one standard SAP customer master report? Not one that covers every view. S_ALR_87012179 is the closest standard list, and it comes from the accounting side, with selections by customer and company code. A list that combines sales area data, partner functions and the reconciliation account is a join you build in SQVI or SAP Query, or a ready-made report.
Change history sits in the change document tables CDHDR and CDPOS under object class DEBI, with the customer number as object ID. PostNow.ai's Change Documents / Audit Trail report in the Report Library reads those two tables, so you can filter on object class DEBI and list customer changes, with old and new values, for many customers at once.
What a customer master report should show
The PostNow.ai Customer Master Sales 360 report covers the sales-side columns most reviews start with. The table lists the columns a complete customer master report needs, the SAP field behind each, and where it comes from.
| Column | SAP field | Why it matters | In Customer Master Sales 360 |
|---|---|---|---|
| Customer, name, city, country | KNA1-KUNNR, NAME1, ORT01, LAND1 | Identifies the customer | Yes |
| Tax number 1 | KNA1-STCD1 | Duplicate checks and invoicing compliance | Yes |
| Customer classification | KNA1-KUKLA | ABC-style segmentation | Yes |
| Sales area | KNVV-VKORG, VTWEG, SPART | Where the customer may buy | Yes, with sales org and division names |
| Customer group, sales office, sales group | KNVV-KDGRP, VKBUR, VKGRP | Pricing, reporting and responsibility | Yes |
| Sales payment terms, Incoterms, shipping conditions | KNVV-ZTERM, INCO1, VSBED | Copied into every sales order | Yes |
| Partner function and partner number | KNVP-PARVW, KUNN2 | Which ship-to, bill-to and payer an order gets | Yes |
| Reconciliation account | KNB1-AKONT | The G/L account receivables post to | Yes |
| Account group | KNA1-KTOKD | Number range and field status of the customer | Add in the SAP Query builder |
| Blocks and deletion flags | KNA1-AUFSD, KNA1-LOEVM, KNB1-SPERR, KNVV-AUFSD | Customers you should not sell to or post for | Add in the SAP Query builder |
| FI payment terms | KNB1-ZTERM | Due dates of FI invoices | Add in the SAP Query builder |
To add the missing columns, a designer opens the report in the PostNow.ai SAP Query builder, adds the fields, and saves the result under My Reports, so the extended version is one click away next time.
Building it yourself: SE16N and SQVI
PostNow.ai replaces a routine that most SD and AR teams know well: export several tables from SE16N, then match them in Excel. Here is what each SAP tool does and where it gets hard.
- SE16N shows one table at a time. Export
KNA1,KNVVandKNB1separately, then join them in Excel with lookups on the padded customer number. It needs table display authorization (S_TABU_DISorS_TABU_NAM), which many business users do not have. - SQVI QuickViewer joins tables in a small graphical editor and exports through the ALV list. A QuickViewer is stored for the user who built it; to share a query with a team, SAP Query (
SQ01) with a user group is the route. - Text tables need a language.
TVKOTandTSPAThold one row per language, so a self-built join must restrictSPRASor each customer row repeats once per language. - Join type decides who is missing. An inner join from
KNA1toKNVVdrops customers with no sales area, such as accounting-only customers. Use a left outer join if they belong on the list.
For the general options to get SAP data into a spreadsheet (ALV export, SE16N, SQVI, SAP Query), see how to export SAP data to Excel.
The PostNow.ai Customer Master Sales 360 report
PostNow.ai ships the customer master report ready-made in its Report Library, so nobody has to build the joins. Customer Master Sales 360 reads KNA1, KNVV, KNVP, KNB1, TVKOT and TSPAT, joined on the customer number and, for partner functions, on the full sales area.
1. Open the report from the Report Library
In the PostNow.ai pane in Excel, open the Report Library and pick Customer Master Sales 360 from the SD reports. Designers and operators can both run library reports.
2. Set the filters
The report opens on the Filters step with ten range filters: customer, sales organisation, distribution channel, division, sales office, customer group, country, city, partner function and created on. Leave a filter empty to include everything.
3. Run
PostNow.ai reads the six tables through the SAP connection on your own computer and returns one grid with readable column headers such as Sales Org Name, Recon Account and Partner Function. With the sales area filters empty, customers without sales area or company code data stay on the list, because the joins are left outer joins.
4. Read the analytics
Four figures sit above the data: Customers, Sales orgs, Countries and Missing payment terms (customers whose sales area payment terms are blank). Three charts show customers by country, by sales organisation and by customer group.
5. Download to Excel
Choose Data only (formatted table with report header, filters and frozen header row), Data + Analytics (adds a dashboard sheet with KPI tiles and native Excel charts) or Data + Analytics + Pivot (adds a PivotTable and PivotChart with slicers), into a new workbook or a new sheet.
6. Re-run when you need fresh data
The Re-run this query button reads SAP again with the same filters. Save the report under My Reports to reopen it with your filters next month.
Duplicate Customers. The same library has a Duplicate Customers report. It groups KNA1 by customer name, tax number 1 and country and counts the customer numbers in each group; a count above 1 is a likely duplicate to review. Cleaning those up is covered in SAP data quality best practices. For credit limits, risk category and credit block per credit control area, use Credit Management 360, which reads KNKA and KNKK.
Once the customer list is right, the order-to-cash report (order, delivery and billing per order) follows each customer's orders through to the invoice, and the sales order report in Excel lists their open and completed orders with schedule lines and status.
Worked example: customers with no payment terms in sales org 1010
PostNow.ai answers this in one run. Before a pricing project, the SD team wants every customer in sales organisation 1010, channel 10 whose sales area has no payment terms, because sales orders for them start without terms.
- Open Customer Master Sales 360 and set Sales Org =
1010, Distr Channel =10and Partner Function =AG, the internal key of the sold-to (an English logon shows it as SP). The partner filter keeps one partner row per sales area, so ship-to and payer rows do not multiply the list. - Run. The Missing payment terms figure shows how many customers have an empty
KNVV-ZTERM. - Sort the Payment Terms column so the blanks come first. Customer
0000200371, for example, shows sales org1010, customer group01and reconciliation account140000, with no payment terms. - Download with Data + Analytics and send the sheet to the team that owns customer data. They correct the terms in VD02 on ECC or in BP on S/4HANA.
- Next week, open the saved report and re-run it. The figure should be zero.
Filters: sales area, account group, blocks
In PostNow.ai, the ten filters of Customer Master Sales 360 decide how many rows you get, so set them for the question you are asking.
- Sales area. Sales Org, Distr Channel and Division together pick one
KNVVrow per customer. Leave them open to see every sales area a customer is extended to. - Partner function.
KNVPstores internal keys:AGsold-to,WEship-to,REbill-to,RGpayer. Filter onWEto list every ship-to assigned to each sold-to. - Created On. A date range on
KNA1-ERDATgives a monthly list of new customers for review. - Country, city, customer group, sales office. Narrow the list to one territory or team.
- Account group and blocks. To select on
KTOKD,LOEVMor the order blockAUFSD, a designer adds the field in the SAP Query builder and saves the report; blocked and flagged customers then filter in or out like any other range.
Customer master in S/4HANA: Business Partner
PostNow.ai runs the same customer master report on ECC and S/4HANA, because S/4HANA still keeps the customer tables. What changes is where customers are maintained.
- BP is the master of record. In S/4HANA, customers are business partners with customer roles, maintained in transaction
BP(SAP Note 2265093, the Business Partner simplification item).XD03and the other customer transactions redirect toBP. - CVI keeps the customer tables filled. Customer/vendor integration writes each customer role to
KNA1,KNB1andKNVV, so reports on those tables keep working. - BP number and customer number can differ. The link is table
CVI_CUST_LINK, and the business partner's general data is inBUT000. Check your number range setup before you match a BP list against a customer list.
Creating and changing customers as business partners from Excel is covered in SAP Business Partner mass upload.