XD03 — Display Customer Master Centrally
XD03 displays the customer master record across all three data levels at once: general data, company code (FI) data, and sales area data. It is read-only. The structural point that causes most confusion is that sales area data only exists for combinations the customer was explicitly extended to, so a customer visible in general data can still show an empty sales screen for a given sales org, distribution channel, and division.
This page covers XD03, the centralized display transaction for customer master data spanning general, company code, and sales area views. It focuses on why a customer can look incomplete or missing depending on which organizational combination is being checked, and how to confirm that in the underlying tables before escalating to master data maintenance.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,152 words
What it does
XD03 shows the customer master record in one screen flow instead of forcing a separate lookup for accounting data and sales data. It pulls general data (name, address, control data, tax numbers), company code data (reconciliation account, payment terms, dunning, correspondence), and sales area data (pricing group, shipping conditions, delivery plant, partner functions, output) depending on which company code and sales area is entered on the selection screen. It is strictly display, no lock is set, and no change document is written. The recurring source of confusion is that these three levels are not one record but three linked segments, each maintained separately, so the transaction can display a fully populated general segment while the sales area segment for the combination being queried simply does not exist yet.
When it is used
Reached for whenever an order, delivery, or billing document fails with a customer-related error and the question is whether the master data supports the transaction being attempted, not whether the master data exists at all. Used ahead of XD02 to see current values before requesting a change, and used instead of VD03 when the company code view is also needed, for example to check payment terms or dunning block alongside sales data. In S/4 systems with business partner-based master data, this is often the first stop even though the underlying maintenance now happens through the business partner transaction; XD03 is kept as the familiar read path for SD consultants who do not need the full BP screen.
How to use it
- Call XD03 and enter the customer number.
- Enter the company code if the FI view is needed; leave blank to skip it.
- Enter sales organization, distribution channel, and division if the sales view is needed.
- Select which screens to display (general data only, company code data, sales area data, or all) on the selection screen or via the menu.
- Press Enter to move through the screen sequence; each tab within a screen (control data, marketing, payment transactions, sales, shipping, billing, partner functions) can be navigated directly from the tab strip.
- Use the account group shown on the general screen to understand which fields are expected to be filled and which are suppressed by field status.
Key fields
- KNA1 - general customer data, one row per customer, address key, account group, central block flags
- KNB1 - company code data, payment terms, reconciliation account, dunning, central and company code level blocks
- KNVV - sales area data, one row per sales org / distribution channel / division combination, pricing group, delivery priority, sales block
- KNVP - partner functions per sales area, sold-to/ship-to/payer/bill-to assignments
- KNVI - tax classification per sales area and tax category
- ADRC - address data referenced by the address number stored on KNA1
How to prove it in the data
To confirm a customer is not extended to a sales area, run SE16 on KNVV filtering on KUNNV (customer), VKORG, VTWEG, SPART for the exact combination the failing document is using. No row means the sales view genuinely does not exist there, regardless of what XD03 general data shows. If a row exists but the document still fails, check the block fields on that same KNVV row (sales block) and cross-check KNB1 for a company code posting block, since XD03 can show both under different tabs and it is easy to read the wrong one.
ECC vs S/4HANA
XD03 still exists and behaves the same way in S/4HANA. The larger change is architectural: where customer/vendor integration to business partner is active, the actual master data lives on the business partner object and XD01/XD02/XD03 operate as a compatibility layer over it. Display and maintenance through the business partner transaction is the direction SAP has been pushing, and some S/4 systems restrict or redirect the classic customer transactions entirely. There is no dedicated Fiori app that simply replicates XD03; the nearest equivalent is the business partner display app or the classic BP transaction used in display mode.
Common pitfalls
- Customer not extended to sales area: order or quotation creation fails saying the customer is unknown for that sales org/channel/division even though the customer exists. XD03 with only the sales area fields filled in will either show blank sales screens or prompt to create them. Confirm with the KNVV check above before assuming the customer is missing entirely.
- Wrong company code or sales area entered: the most common false alarm. A large customer can have data in several company codes and several sales areas; checking XD03 against the wrong combination looks identical to missing data. Always re-enter the exact org values from the failing document.
- Blocking flags hidden on a non-obvious tab: central block sits on general data, sales block sits inside the sales area screen, posting block sits inside company code data. A consultant scanning only the general screen will miss a sales-level block and misdiagnose the failure as a pricing or partner determination issue.
- Field status suppresses fields, not deletes them: fields greyed out or absent on a given account group are configuration-driven, not evidence of corrupted or incomplete data. Before requesting a data fix, check whether the field is even relevant for that account group.
- One-time customer (CPD) account groups: most master fields are entered per document rather than stored on the master, so XD03 for a CPD customer will look sparse by design; this is not a data quality problem.
- Authorization-limited display: a user without authorization for a company code or sales area sees that screen skipped without an explicit error, which can be mistaken for the data not existing.
Whose problem this is
Functional master data ownership, split between SD (sales area data) and FI (company code data), with account group and field status configuration owned by whoever configured customer master. Not a Basis issue except for authorization checks. A good handover includes the customer number, the exact company code and sales org/distribution channel/division combination checked, and which tab was found empty or blocking.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/xd03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.