SAP vendor master replication diagnostics

Core idea

Vendor master replication moves supplier data through ALE, CVI, or MDG. The failures that matter most are missing purchasing organization or company code data, duplicate vendors in the target, and bank or tax details that differ between source and target. The diagnostic job is to separate replication model gaps from CVI synchronization gaps from key mapping gaps.

Common symptoms

• Vendor created in source system but missing in target system.
• Vendor exists in target but purchasing organization or company code data is missing.
• Target system creates duplicate vendor instead of updating existing one.
• CVI synchronization creates a business partner but the vendor link is broken.
• Vendor bank details or tax number differ between source and target.

Likely causes

• Replication model filter: the vendor account group or organizational unit is excluded from replication.
• CVI synchronization failure: the customer-vendor integration (CVI) did not create or link the BP correctly.
• Key mapping missing: the source vendor number is not mapped to the target system, causing a new vendor to be created.
• Organizational data filter: the replication sends general data but filters out purchasing organization or company code data.
• 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

• XK01 / XK02 / XK03 — vendor 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 vendor number mapping.

Key tables / transactions / objects

• LFA1 — vendor general data.
• LFB1 — vendor company code data.
• LFM1 — vendor purchasing organization data.
• BUT000 / BUT001 — BP header (if CVI is used).
• CVI_LINK — CVI link table between BP and vendor.

Diagnostic workflow

1. Identify the vendor number, source system, target system, and the expected versus actual result.
2. Check the replication log or IDoc status to confirm the vendor was selected and sent.
3. Verify the vendor exists in the target system (XK03) 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 vendor maps to the correct target vendor.
6. Compare organizational data (company code, purchasing org) between source and target.

Typical fixes or next actions

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

What to capture first

Before routing the issue, capture: vendor 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

• Vendor data is missing or wrong in downstream procurement, finance, or payment systems.
• Replication failures affect a strategic supplier or multiple purchasing organizations.
• A duplicate vendor was created and needs merging with procurement and finance approval.
• The issue involves payment terms, bank details, tax number, or purchasing organization data with compliance risk.

Boundaries and non-goals

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

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