SAP CVI synchronization diagnostics

Core idea

Customer-Vendor Integration (CVI) in S/4HANA keeps business partners aligned with customer and vendor master data. Most CVI incidents are not data corruption; they are configuration or timing mismatches. Before treating a missing customer or vendor as a master-data defect, confirm whether CVI is expected to create the object, which direction is configured, and whether the required BP role exists.

Common symptoms

• Business partner created but no corresponding customer or vendor was generated.
• Customer or vendor exists but the linked BP has different data or is missing.
• CVI creates duplicate business partners for the same customer or vendor.
• BP role assignment is missing or wrong after CVI synchronization.
• CVI synchronization log shows errors that are not immediately actionable.

Likely causes

• CVI not active for the BP grouping: the BP grouping used for the new BP is not configured for CVI synchronization.
• Direction mismatch: the synchronization direction is set to BP-to-customer but the customer was created first, or vice versa.
• Number range conflict: the BP number range overlaps with customer or vendor number ranges, causing collisions.
• Missing BP role: the BP was created without the FLCU00 (customer) or FLVN00 (vendor) role required for CVI.
• CVI mapping error: the field mapping between BP and customer/vendor is misconfigured or missing for a specific field.

Where to check in SAP

• FLBP1 / FLBP2 — business partner display to check roles and CVI link.
• XD03 / XK03 — customer/vendor display to check BP assignment.
• CVI_LINK — link table between BP and customer/vendor.
• CVI synchronization log — check for errors during synchronization.
• BP grouping configuration — check if CVI is active for the grouping.

Key tables / transactions / objects

• BUT000 / BUT001 — BP header and general data.
• CVI_LINK — CVI link table.
• KNA1 / KNB1 — customer master data.
• LFA1 / LFB1 — vendor master data.
• TBZ9A — BP role definitions.

Diagnostic workflow

1. Identify the BP number, customer number, or vendor number and the expected synchronization result.
2. Check FLBP1 for the BP roles (FLCU00 for customer, FLVN00 for vendor).
3. Check CVI_LINK for the relationship between BP and customer/vendor.
4. Check XD03/XK03 for the customer/vendor and verify the BP assignment.
5. Check the CVI synchronization log for errors during the last synchronization run.
6. Verify the BP grouping is configured for CVI and the synchronization direction is correct.

Typical fixes or next actions

• Activate CVI for the BP grouping if it was not configured.
• Add the missing BP role (FLCU00 or FLVN00) to enable synchronization.
• Correct the synchronization direction if BP and customer/vendor were created in the wrong order.
• Fix number range conflicts to prevent duplicate creation.
• Re-run CVI synchronization after correcting configuration or data issues.

What to capture first

Before routing the issue, capture: BP number, customer or vendor number, BP grouping, expected roles, actual result, CVI_LINK status, and any synchronization log error. If the BP was created manually, note the creation order; direction mismatches are common when a customer or vendor already exists before the BP.

Boundaries and non-goals

This page is a diagnostic frame, not a CVI configuration guide. It does not cover CVI setup, BP grouping design, or field mapping configuration. It does not replace SAP's CVI documentation.

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

Next diagnostic steps

• SAP Master Data Quality — use this for broader data quality signals and governance context.
• SAP Business Partner Replication Diagnostics — go here when BP data is replicated between systems.
• SAP Customer Master Replication Diagnostics — check this when the customer side is missing or wrong.
• SAP Vendor Master Replication Diagnostics — use this when the vendor side is missing or wrong.
• SAP BP Relationship Diagnostics — go here if the issue involves related BP roles or relationships.

Customer-vendor integration boundary

CVI is a bridge, not a cleanup tool. It will not repair a customer that was created before the BP, nor will it guess the right grouping if the BP was created without the FLCU00 or FLVN00 role. Fix the configuration and timing first; manual object creation usually creates more link breaks than it solves.

Practical checklist