SAP customer master replication diagnostics

Core idea

Customer master replication moves customer data through ALE, CVI, or MDG. The failures that matter most are missing sales area or company code data, duplicate customers in the target, and CVI links that look connected but carry different data. The diagnostic job is to separate replication model gaps from CVI synchronization gaps from key mapping gaps.

Common symptoms

• Customer created in source system but missing in target system.
• Customer exists in target but sales area or company code data is missing.
• Target system creates duplicate customer instead of updating existing one.
• CVI synchronization creates a business partner but the customer link is broken.
• Customer partner functions or tax classification differ between source and target.

Likely causes

• Replication model filter: the customer account group or sales area is excluded from replication.
• CVI synchronization failure: the customer-vendor integration did not create or link the BP correctly.
• Key mapping missing: the source customer number is not mapped to the target system, causing a new customer to be created.
• Sales area filter: the replication sends general data but filters out specific sales organizations or distribution channels.
• Target number range issue: the target system number range is exhausted or configured for external numbering while the source uses internal.

Where to check in SAP

• XD01 / XD02 / XD03 — customer master display in target system.
• WE02 — IDoc status if ALE replication is used.
• FLBP1 / FLBP2 — business partner display if CVI is involved.
• MDG replication log — if MDG is the source.
• Key mapping tables — source-to-target customer number mapping.

Key tables / transactions / objects

• KNA1 — customer general data.
• KNB1 — customer company code data.
• KNVV — customer sales area data.
• BUT000 / BUT001 — BP header (if CVI is used).
• CVI_LINK — CVI link table between BP and customer.

Diagnostic workflow

1. Identify the customer number, source system, target system, and the expected versus actual result.
2. Check the replication log or IDoc status to confirm the customer was selected and sent.
3. Verify the customer exists in the target system (XD03) and check which views are present.
4. If CVI is used, check FLBP1 for the linked BP and verify the CVI_LINK table.
5. Check key mapping to confirm the source customer maps to the correct target customer.
6. Compare sales area and company code data between source and target.

Typical fixes or next actions

• Update the replication model to include the missing account group or sales area.
• Create or correct key mapping between source and target customer numbers.
• Fix CVI synchronization issues by re-running CVI synchronization or correcting the BP link.
• Extend the customer to the missing sales area or company code in the target system.
• Adjust target number ranges if they conflict with the source numbering.

What to capture first

Before routing the issue, capture: customer number, source and target systems, expected versus actual views, replication model, and any IDoc or CVI error. If CVI is involved, include the BP number and the CVI_LINK status. These facts separate a replication problem from a BP-link problem.

Escalation signals

• Customer data is missing or wrong in downstream sales, billing, or service systems.
• Replication failures affect a key account, distribution channel, or sales organization.
• A duplicate customer was created and needs merging with approval from sales and finance.
• The issue involves tax classification, credit segment, or partner function changes beyond standard support scope.

Boundaries and non-goals

This page is a diagnostic frame, not a customer replication configuration guide. It does not cover CVI setup, replication model design, or customer account group configuration. It does not replace SAP's customer master documentation.

This is not official SAP documentation and not a replacement for system-specific analysis.