CA Program Custom development Enhancement

Business Partner Save Checks for IBAN, Tax Number and Mandatory Fields

Short answer: A development that checks, when a customer or supplier business partner is saved, the consistency of IBAN and bank details, the country-specific format of the tax number and the company's mandatory fields. Incorrect or incomplete master data is stopped before it is saved; rules are kept in a setup table by role, grouping and country.

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

Why is the standard not enough?

The standard BP transaction checks the general structure of the IBAN and the length of the tax number for some countries; it does not check the check digit of the local tax ID, whether the IBAN matches the bank key and account number, or whether the same IBAN or tax number is already used by another business partner. Field status settings can make a field mandatory, but rules that depend on role and country, such as 'tax office mandatory for domestic suppliers', cannot be set up.

Who uses it? Master data teams, receivables and payables accounting, internal control and business partner/CVI consultants.

Closest standard alternatives

  • BP Maintain Business Partner. Business partner maintenance; checks the general IBAN structure but not the local tax number check digit, bank consistency or mandatory fields by role and country.
  • SPRO Customizing - Edit Project. Field status settings can make fields mandatory by grouping; country-dependent rules and duplicate checks cannot be set up.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
BUT000Business Partner: General DataBusiness partner general data, grouping and categoryReadECC + S/4
BUT0BKBusiness Partner Bank DetailsBank details and IBANReadECC + S/4
TIBANIBAN NumbersIBAN to bank account link, duplicate IBAN checkReadECC + S/4
BNKABank Master DataExistence of the bank keyReadECC + S/4
DFKKBPTAXNUMTax Numbers for Business PartnerTax number type and tax numberReadECC + S/4
ADRCAddresses (Business Address Services)Address fieldsReadECC + S/4
ADR6E-Mail Addresses (Business Address Services)Email addressReadECC + S/4
KNB1Customer Master (Company Code)Customer company code data: reconciliation account, payment termsReadECC + S/4
LFB1Vendor Master (Company Code)Supplier company code data: reconciliation account, payment termsReadECC + S/4
BALHDRApplication Log HeaderApplication log of blocked savesWriteECC + S/4

BAPIs and functions used

  • BAPI_BANK_GETDETAILBank Details. Reads the bank key master data
  • BAPI_BUPA_CENTRAL_GETDETAILRead Business Partner Central Data. Reads central business partner data in the audit report

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_PARTNERBusiness partnerRange / multipleBUT000-PARTNERNo—
S_BUGRPBusiness partner groupingRange / multipleBUT000-BU_GROUPNo—
S_LANDCountryRange / multipleADRC-COUNTRYNoTR
P_ROLERole (customer, supplier or both)Single value—NoFLVN01
P_ERROnly records violating a ruleCheckbox—NoX

Result list columns

#ColumnSource
1Business partnerBUT000-PARTNER
2NameBUT000-NAME_ORG1
3GroupingBUT000-BU_GROUP
4CheckCalculated IBAN, bank consistency, tax number, duplicate or mandatory field
5Field valueCalculated Value checked (IBAN or tax number masked)
6LevelCalculated Error or warning
7MessageCalculated Description of the rule

Sample result list

Business partnerNameGroupingCheckField valueLevelMessage
1000045Örnek Ambalaj A.Ş.SATIIBANTR12 **** **** 4410ErrorIBAN check digits are wrong
1000051Demo Kağıt Ltd.SATIDuplicate47******12WarningTax number also used by business partner 1000032
2000318Anadolu Gıda Dağıtım A.Ş.MUSTMandatory fieldErrorTax office empty for domestic customer
1000063Nordic Supply GmbHSATIBank consistencyDE89 **** **** 3000ErrorBank code in IBAN does not match the bank key
A view built with fictional sample data; not real system data.

How does the program work?

  1. Rules are kept in a setup table: business partner grouping, role (customer, supplier), country, check (IBAN, bank consistency, tax number format, duplicate check, mandatory field) and level (error or warning).
  2. The checks run in a function module registered with BUS7 for the BDT check event (DCHCK), which runs on save in the BP transaction; messages are returned to the BP screen with BUS_MESSAGE_STORE and the record cannot be saved while there is an error. Mass load programs and interfaces call the same rule class before saving.
  3. Bank: for every bank line in BUT0BK the IBAN is validated with CHECK_IBAN for check digits and country length; the bank key and account number resolved with CONVERT_IBAN_2_BANK_ACCOUNT are compared with those on the line, and the bank key must exist in BNKA. If the same IBAN exists for another business partner in TIBAN/BUT0BK, a warning is issued.
  4. Tax number: the format is checked by tax number type in DFKKBPTAXNUM (local check digit calculation in addition to the standard TAX_NUMBER_CHECK); separate types are used for organisations and persons. If the same tax number exists for another business partner, an error or warning is issued according to the rule.
  5. Mandatory fields: address fields (ADRC), email (ADR6), tax office and company code data (KNB1/LFB1 reconciliation account, payment terms) are checked by role and country.
  6. Every blocked save is written to the application log. The audit report scans existing business partners with the same rules and lists incorrect records created before the rules were introduced. In S/4HANA customers and suppliers are maintained only with BP; in ECC the CHECK_ALL_DATA method of the CUSTOMER_ADD_DATA and VENDOR_ADD_DATA BAdIs is used for XD01/XK01.

Performance notes

Run the duplicate IBAN and tax number search only when the field has changed and use indexed fields (TIBAN-IBAN, DFKKBPTAXNUM-TAXNUM). In the audit report, read business partners in packages and run it in the background for large volumes.

Features

  • Line-by-line result and error log Every blocked save is logged with rule and user.
  • ALV list (sort, filter, subtotals)
  • Runs as a background job The audit report can run in the background for all business partners.
  • Delivered as a transport request

Authorization objects

  • B_BUPA_GRPBusiness partner maintenance by authorization group
  • B_BUPA_RLTBusiness partner maintenance by role
  • F_LFA1_BUKSupplier company code data maintenance
  • S_APPL_LOGDisplaying the check log

Frequently asked questions

Are business partners from mass loads and interfaces checked too?

The BDT check event runs in the BP screen. Load programs and interfaces call the same rule class before saving, so the same rules apply whichever path the data comes from and incorrect rows are listed in the load log.

What about existing incorrect records?

The rules apply only to new records and changes. The audit report scans existing business partners with the same rules; the master data team uses the list to correct old records in a planned way.

What happens if the tax number format changes by regulation?

Format and check digit rules are kept in a separate class per country and tax number type. They are checked against current rules during installation; when something changes, only the rule of that country is updated.

Related reports

Let us build this program 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: Business Partner Save Checks for IBAN, Tax Number and Mandatory Fields