CA Report Custom development ALV report

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

  • BP Maintain Business Partner. Shows a business partner and its roles one at a time; no list of unlinked records or missing roles.
  • XD03 Display Customer (Centrally). Shows customer master data; it does not check business partner links in bulk.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
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 PartnerCustomer-to-business partner linkCVI_CUST_LINK-CUSTOMER = KNA1-KUNNRECC + S/4
CVI_VEND_LINKAssignment Between Vendor and Business PartnerVendor-to-business partner linkCVI_VEND_LINK-VENDOR = LFA1-LIFNRECC + S/4
BUT000Business Partner: General DataBusiness partner: number, grouping, central block and archiving flagBUT000-PARTNER_GUID = CVI_CUST_LINK-PARTNER_GUID OR BUT000-PARTNER_GUID = CVI_VEND_LINK-PARTNER_GUIDECC + S/4
BUT100Business Partner RolesBusiness partner rolesBUT100-PARTNER = BUT000-PARTNERECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_KUNNRCustomerRange / multipleKNA1-KUNNRNo—
S_LIFNRVendorRange / multipleLFA1-LIFNRNo—
S_KTOKDCustomer account groupRange / multipleKNA1-KTOKDNo0001
S_KTOKKVendor account groupRange / multipleLFA1-KTOKKNoKRED
P_CUSTCheck customersCheckbox—NoX
P_VENDCheck vendorsCheckbox—NoX
P_DELAlso show deletion-flagged recordsCheckbox—NoX
P_ROLECheck expected BP rolesCheckbox—NoX

Output columns

#ColumnSource
1ObjectCalculated Customer or Vendor
2CustomerKNA1-KUNNR
3VendorLFA1-LIFNR
4NameCalculated KNA1-NAME1 or LFA1-NAME1
5Account groupCalculated KNA1-KTOKD or LFA1-KTOKK
6Business partnerBUT000-PARTNER
7BP groupingBUT000-BU_GROUP
8Existing BP roleBUT100-RLTYP
9BP central blockBUT000-XBLCK
10FindingCalculated No link / role missing / block-deletion inconsistent / deletion-flagged without link
11Proposed actionCalculated Proposal from the settings table by finding

Sample output

ObjectCustomerVendorNameAccount groupBusiness partnerBP groupingExisting BP roleBP central blockFindingProposed action
Customer100245Ege Gıda Dağıtım A.Ş.0001No business partner linked to the customerCreate the business partner through CVI synchronization
Vendor300118Marmara Ambalaj San. Ltd. Şti.KRED1000318BP02FLVN01Role FLVN00 (FI vendor) missingAdd the role and synchronize company code data
Customer100389Kuzey Yapı Malzemeleri Ltd. Şti.00011000402BP01FLCU01XBusiness partner centrally blocked, customer activeClarify the block decision with the master data owner
Customer100077Doğu Tekstil Tic. Ltd. Şti.0001Deletion-flagged without linkArchive or exclude before conversion
A view built with fictional sample data; not real system data.

How does the report work?

  1. The selected customers are read from KNA1 and left-joined with CVI_CUST_LINK; those without a link get the finding “no business partner”.
  2. The same is done for LFA1 and CVI_VEND_LINK.
  3. 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).
  4. 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).
  5. Deletion-flagged records without a link get the proposal “archive or exclude before conversion”; active ones without a link get “synchronize”.
  6. 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

CA Package Custom

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 …

5 components · v1.0

Related reports

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.

Related report: Customer/Vendor to Business Partner (CVI) Sync Check Report for S/4HANA Conversion