CVI_CUST_LINK table — Business Partner to Customer Link
CVI_CUST_LINK stores the technical relationship between a Business Partner and its synchronized customer master number. It is a key diagnostic table for Customer/Vendor Integration because it proves that the BP and customer representations are linked. A missing or inconsistent mapping can explain customer-role synchronization problems, but the link row alone does not prove that every customer segment is complete.
A consultant-focused reference for CVI_CUST_LINK covering its purpose, key fields, joins, safe query restrictions, proof steps, release context, ownership and recurring interpretation traps.
Published 20 Sept 2026· 695 words
What it stores
CVI_CUST_LINK stores the technical mapping between a Business Partner GUID and its synchronized customer master number. Each row must be interpreted using the complete technical key and the application process that writes it. A consultant should first establish whether the row represents current state, a dated master-data slice, a document item, a history event, an index entry or a compatibility representation. Organizational levels, validity dates, fiscal years, ledgers, languages, statuses and sequence numbers are part of the grain whenever those dimensions exist. The table should be read as evidence of application behavior, not as an isolated spreadsheet. Confirm the owning business object and configuration before deciding that a value is wrong.
Key fields
Customer-Vendor Integration customer-link records connect a Business Partner representation to its customer-side identity. GUID and number representations must be interpreted with the configured CVI model rather than assumed interchangeable.
- PARTNER_GUID — technical Business Partner GUID.
- CUSTOMER — linked customer number.
- BUT000 — resolves the BP identity.
- KNA1/KNB1/KNVV — provide synchronized customer segments.
- CVI synchronization logs and checks — determine whether the mapping is consistent.
How it joins the data model
Use the key fields and foreign-key relationships defined in the exact SAP release to connect BP and customer records. Do not equate customer number with BP number when separate number ranges or mappings are configured.
- PARTNER_GUID to BUT000-PARTNER_GUID
- CUSTOMER to KNA1-KUNNR
- CUSTOMER to KNB1 and KNVV for company-code and sales-area extensions
How to read it safely
If a BP exists but customer functions fail, inspect CVI synchronization and the required customer sales-area/company-code extensions. Resolve the application or synchronization error before attempting a manual link-table change.
How to prove it in the data
Take one reproducible example from the relevant SAP screen, report or application log. Record its full displayed key, organizational context, key date, language and status. Locate the matching CVI_CUST_LINK row using those values, then follow the documented parent and child joins without dropping key components. Compare the result using the same key date and ledger. When values differ, test for leading-zero conversion, multiple validity slices, inactive history, parallel ledgers, fiscal-year boundaries, archived data and asynchronous replication. Save the read-only evidence before escalating. If the row is wrong, reproduce the maintenance path in a non-production system and route the fix to the application owner rather than changing the table.
ECC vs S/4HANA
CVI_CUST_LINK is central to S/4HANA customer integration because Business Partner is the leading object. Use it with BP roles and customer tables to diagnose conversion or synchronization problems; repairs should follow CVI tools and supported consistency procedures rather than manual table updates.
Common pitfalls
- Selecting by one convenient identifier and silently mixing organizational units, years, ledgers, languages or validity periods.
- Joining on a partial key or descriptive value and creating duplicates that appear to be legitimate business rows.
- Ignoring inactive, deletion, reversal or status indicators and reporting retained history as current state.
- Assuming this table is authoritative without checking S/4HANA simplification, Business Partner synchronization, Universal Journal, MATDOC, CDS views or an external cloud source.
- Treating a missing row as proof that an event never occurred even though logging, replication, authorization and archiving scope can differ.
- Updating table rows directly instead of correcting data through the supported transaction, app, API or migration process.
Whose problem this is
Business Partner/CVI migration governance owns mapping policy, FI and SD own the relevant customer extensions, and integration specialists investigate link/synchronization errors with approved SAP tooling.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tables/cvi-cust-linkERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.