Customer/Vendor to Business Partner (CVI) Sync Check Report for S/4HANA Conversion
Short answer: A custom ALV report that lists, before and after an S/4HANA conversion, customers and vendors not linked to a business partner, linked ones missing an expected BP role, and those whose deletion or block flags are inconsistent with the business partner. Before running the synchronization, the project team sees by account group what needs cleaning and what should be archived.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
The synchronization cockpit (MDS_LOAD_COCKPIT) shows errors of a synchronization run and the pre-conversion checks give the number of unmatched records; but neither lists all customers and vendors for link, role and block/deletion consistency in one list with account group and a proposed action. BP and XD03 show records one by one. The custom report produces the cleanup work list directly.
Who uses it? S/4HANA conversion project teams, master data management, and FI and SD/MM master data owners.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| KNA1Customer Master (General Section) | Customer general data: name, account group, deletion and block flags | — | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor general data: name, account group, deletion and block flags | — | ECC + S/4 |
| CVI_CUST_LINKAssignment Between Customer and Business Partner | Customer-to-business partner link | CVI_CUST_LINK-CUSTOMER = KNA1-KUNNR | ECC + S/4 |
| CVI_VEND_LINKAssignment Between Vendor and Business Partner | Vendor-to-business partner link | CVI_VEND_LINK-VENDOR = LFA1-LIFNR | ECC + S/4 |
| BUT000Business Partner: General Data | Business partner: number, grouping, central block and archiving flag | BUT000-PARTNER_GUID = CVI_CUST_LINK-PARTNER_GUID OR BUT000-PARTNER_GUID = CVI_VEND_LINK-PARTNER_GUID | ECC + S/4 |
| BUT100Business Partner Roles | Business partner roles | BUT100-PARTNER = BUT000-PARTNER | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_KUNNR | Customer | Range / multiple | KNA1-KUNNR | No | — |
| S_LIFNR | Vendor | Range / multiple | LFA1-LIFNR | No | — |
| S_KTOKD | Customer account group | Range / multiple | KNA1-KTOKD | No | 0001 |
| S_KTOKK | Vendor account group | Range / multiple | LFA1-KTOKK | No | KRED |
| P_CUST | Check customers | Checkbox | — | No | X |
| P_VEND | Check vendors | Checkbox | — | No | X |
| P_DEL | Also show deletion-flagged records | Checkbox | — | No | X |
| P_ROLE | Check expected BP roles | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Object | Calculated Customer or Vendor |
| 2 | Customer | KNA1-KUNNR |
| 3 | Vendor | LFA1-LIFNR |
| 4 | Name | Calculated KNA1-NAME1 or LFA1-NAME1 |
| 5 | Account group | Calculated KNA1-KTOKD or LFA1-KTOKK |
| 6 | Business partner | BUT000-PARTNER |
| 7 | BP grouping | BUT000-BU_GROUP |
| 8 | Existing BP role | BUT100-RLTYP |
| 9 | BP central block | BUT000-XBLCK |
| 10 | Finding | Calculated No link / role missing / block-deletion inconsistent / deletion-flagged without link |
| 11 | Proposed action | Calculated Proposal from the settings table by finding |
Sample output
| Object | Customer | Vendor | Name | Account group | Business partner | BP grouping | Existing BP role | BP central block | Finding | Proposed action |
|---|---|---|---|---|---|---|---|---|---|---|
| Customer | 100245 | Ege Gıda Dağıtım A.Ş. | 0001 | No business partner linked to the customer | Create the business partner through CVI synchronization | |||||
| Vendor | 300118 | Marmara Ambalaj San. Ltd. Şti. | KRED | 1000318 | BP02 | FLVN01 | Role FLVN00 (FI vendor) missing | Add the role and synchronize company code data | ||
| Customer | 100389 | Kuzey Yapı Malzemeleri Ltd. Şti. | 0001 | 1000402 | BP01 | FLCU01 | X | Business partner centrally blocked, customer active | Clarify the block decision with the master data owner | |
| Customer | 100077 | Doğu Tekstil Tic. Ltd. Şti. | 0001 | Deletion-flagged without link | Archive or exclude before conversion |
How does the report work?
- The selected customers are read from KNA1 and left-joined with CVI_CUST_LINK; those without a link get the finding “no business partner”.
- The same is done for LFA1 and CVI_VEND_LINK.
- For linked records, BUT000 is read through PARTNER_GUID; the roles in BUT100 are compared with the roles expected for the account group (settings table; e.g. FLCU00/FLCU01 for customers, FLVN00/FLVN01 for vendors).
- Consistency: the customer/vendor deletion flag (LOEVM) or central block (SPERR) is compared with the business partner’s archiving flag (XDELE) and central block (XBLCK).
- Deletion-flagged records without a link get the proposal “archive or exclude before conversion”; active ones without a link get “synchronize”.
- The result is given in ALV with subtotals by finding type and account group; double-clicking a record opens XD03/XK03 or BP.
Performance notes
Customers and vendors can number in the hundreds of thousands; read the link tables once and search them in sorted internal tables. Run the role check only for linked records. The report runs a few times during the project; run it in the background split by account group.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking a record opens XD03/XK03, double-clicking the business partner opens BP.
- Export to Excel
- Runs as a background job
Authorization objects
- F_KNA1_GENDisplay customer general data
- F_LFA1_GENDisplay vendor general data
- B_BUPA_GRPDisplay by business partner grouping
Frequently asked questions
Does the report run on ECC, before the conversion?
Yes, that is its main use. The CVI link tables also exist in ECC 6.0; it runs before CVI is activated and synchronization starts, and between synchronization rounds. After the conversion it can still be used on S/4HANA as a check.
How do you define which roles are expected?
Expected roles are kept per account group in a settings table and aligned with the project's CVI customizing. For example, a customer with company code data needs the FI customer role, and one with sales area data needs the customer role.
Does the report create missing business partners itself?
No. Business partners should be created with the standard synchronization cockpit; the report shows the state of each record and what needs cleaning first.
Packages that include this solution
S/4HANA Conversion Readiness Pack
A five-component pack that finds the master data and finance inconsistencies to clean up before a system conversion from ECC to S/4HANA: business …
Related reports
Duplicate Business Partner Detection Report (Name, Tax Number, Address)
A custom ALV report that finds cases where the same customer or vendor was created under more than one business partner number, using the tax number, …
Mass Block and Archiving Flag for Inactive Business Partners
A custom background program that finds business partners with no accounting posting, sales order or purchase order for a given period and sets a …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.