CA Report Custom development ALV report

Duplicate Business Partner Detection Report (Name, Tax Number, Address)

Short answer: 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, a name comparison that normalizes Turkish characters and legal form suffixes, the address and the phone number. Likely duplicates are grouped with a match score and reason, so the master data team can quickly decide which record to keep.

Estimated effort
M · 5–7 working days
System
ECC and S/4HANA
Tables
5
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

The duplicate check in transaction BP only runs when a new record is created and needs the address search service to be set up separately; it does not scan thousands of existing records and list the duplicates. Spelling differences such as "Atlas Ambalaj A.Ş." and "ATLAS AMBALAJ SANAYİ TİC. AŞ" stay separate records in the standard search. The custom report scans the whole master data, compares normalized names and returns duplicate groups with a score.

Who uses it? Master data management teams, accounting and purchasing master data owners, S/4HANA conversion projects.

Closest standard alternatives

  • BP Maintain Business Partner. Can check for duplicates when a new record is created (needs the address search service); it does not scan existing records in bulk.

Tables used

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

TableRoleJoinSystem
BUT000Business Partner: General DataBusiness partner general data: type, grouping, name, creation (driving table)—ECC + S/4
DFKKBPTAXNUMTax Numbers for Business PartnerTax numbers; the strongest match criterionDFKKBPTAXNUM-PARTNER = BUT000-PARTNERECC + S/4
BUT020Business Partner AddressesAddress number of the business partnerBUT020-PARTNER = BUT000-PARTNERECC + S/4
ADRCAddresses (Business Address Services)Postal code, city, street and phoneADRC-ADDRNUMBER = BUT020-ADDRNUMBERECC + S/4
BUT100Business Partner RolesBusiness partner roles (customer, vendor)BUT100-PARTNER = BUT000-PARTNERECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_PARTNRBusiness partnerRange / multipleBUT000-PARTNERNo—
S_BUGRPGroupingRange / multipleBUT000-BU_GROUPNoBP01, BP02
S_TYPEPartner category (1 person, 2 organization)Range / multipleBUT000-TYPENo2
S_CRDATCreated onRange / multipleBUT000-CRDATNo—
S_CNTRYCountryRange / multipleADRC-COUNTRYNoTR
S_RLTYPRoleRange / multipleBUT100-RLTYPNoFLCU01, FLVN01
P_SCOREMinimum match scoreSingle value—Yes60
P_TAXONTax number matches onlyCheckbox—No—

Output columns

#ColumnSource
1Duplicate groupCalculated Group number given to records that match each other
2Business partnerBUT000-PARTNER
3NameBUT000-NAME_ORG1
4GroupingBUT000-BU_GROUP
5Tax numberDFKKBPTAXNUM-TAXNUM
6CityADRC-CITY1
7Postal codeADRC-POST_CODE1
8StreetADRC-STREET
9PhoneADRC-TEL_NUMBER
10RolesCalculated List of BUT100-RLTYP values
11Created onBUT000-CRDAT
12Created byBUT000-CRUSR
13Match scoreCalculated Tax no 100, name 60, similar name 40, address 30, phone 20 (best pair)
14Match reasonCalculated Criteria that make up the score

Sample output

Duplicate groupBusiness partnerNameGroupingTax numberCityPostal codeStreetPhoneRolesCreated onCreated byMatch scoreMatch reason
11000245Atlas Ambalaj San. ve Tic. A.Ş.BP021234567890İstanbul34775Ataşehir Bulvarı 120216 555 01 01FLCU01, FLVN0103/14/2019MDVERI01160Tax no + name
11000981ATLAS AMBALAJ SANAYİ TİCARET AŞBP021234567890İstanbul34775Ataşehir Blv. No:120216 555 01 01FLVN0107/02/2025SATINALMA03160Tax no + name
21001302Ege Kimya Ltd. Şti.BP029876543210İzmir35410Gaziemir Sanayi Sitesi 40232 444 20 20FLCU0111/20/2021MDVERI02110Name + address + phone
21001877EGE KIMYA LIMITEDBP029876543201İzmir35410Gaziemir San. Sit. 40232 444 20 20FLCU0102/09/2026SATIS05110Name + address + phone
A view built with fictional sample data; not real system data.

How does the report work?

  1. Business partners in the selection are read from BUT000 (type, grouping, creation date); records flagged for archiving (XDELE) are skipped.
  2. Name normalization: NAME_ORG1 (for persons NAME_FIRST + NAME_LAST) is converted to upper case, Turkish characters are folded (İ→I, Ş→S, Ğ→G, Ü→U, Ö→O, Ç→C), legal form suffixes (A.Ş., AŞ, LTD. ŞTİ., SAN. TİC. and so on), punctuation and spaces are removed.
  3. Tax numbers are read from DFKKBPTAXNUM; the same tax type and number is a strong match.
  4. The standard address is read from ADRC through BUT020: postal code, city, normalized street and phone.
  5. Score: same tax number 100, same normalized name 60, name similarity above the threshold 40, same postal code and street 30, same phone 20. Pairs above the score threshold are merged into duplicate groups.
  6. Roles (customer, vendor and so on) are added from BUT100, so it can be checked which record has open items or documents. The result is listed per group in ALV.

Performance notes

Run the name similarity comparison not over all pairs but within blocks that share the postal code, the city or the same normalized name prefix. On systems with hundreds of thousands of partners, run the report in the background; on a HANA database, fuzzy search can be used for name similarity.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document Double-clicking the partner number opens BP in display mode.
  • Export to Excel
  • Runs as a background job

Authorization objects

  • B_BUPA_GRPDisplay authorization by business partner grouping
  • B_BUPA_RLTDisplay authorization by business partner role

Frequently asked questions

Does the report merge duplicate records?

No, it only lists them. The master data team decides which record to keep; the other one is blocked or flagged for archiving. For records with open items, accounting has to clean up first.

Does this report work on ECC too?

Yes, on ECC systems that use business partners it works with the same tables. For ECC systems that still keep customer and vendor master data in KNA1/LFA1, the same logic can be adapted to those tables; this is often requested as a clean-up before an S/4HANA conversion.

How is name similarity measured?

The edit distance (Levenshtein) between the normalized names is calculated and converted into a percentage similarity based on length. The default threshold is 85% and can be changed on the selection screen.

Packages that include this solution

CA Package Custom

Business Partner Master Data Quality Pack

A four-component pack for keeping customer and vendor master data clean: mass business partner creation from Excel with a duplicate check, duplicate …

4 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: Duplicate Business Partner Detection Report (Name, Tax Number, Address)