CA Report Custom development ALV report

Business Partner and Vendor Bank Details Change Control Report

Short answer: A custom ALV report that lists every change to business partner or vendor bank details (IBAN, account, bank key, account holder) in a period with old and new value, changing user and transaction, and flags cases where a payment was made to the new account shortly after the change. The weekly control against payment fraud comes down to one list.

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

Why is the standard not enough?

The change history in transaction BP works for one business partner at a time; although change documents can be displayed in general, no standard report gives the bank fields per period, for all vendors and matched with the next payment. Auditors answer the question "was any vendor paid right after a bank detail change?" by comparing change documents with payment run lists by hand. The custom report does this matching automatically.

Who uses it? Internal control and internal audit teams, accounts payable managers, treasury and master data owners.

Closest standard alternatives

  • BP Maintain Business Partner. Shows the change history for one business partner; no view of all vendors per period and no matching with the next payment.
  • F110 Automatic Payment Program. Provides the payment list of a payment run; it does not compare it with bank detail changes.

Tables used

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

TableRoleJoinSystem
CDHDRChange Document HeaderChange document header: user, date, time, transaction (driving table)—ECC + S/4
CDPOSChange Document ItemsOld and new values of the bank fieldsCDPOS-OBJECTCLAS = CDHDR-OBJECTCLAS AND CDPOS-OBJECTID = CDHDR-OBJECTID AND CDPOS-CHANGENR = CDHDR-CHANGENRECC + S/4
BUT0BKBusiness Partner Bank DetailsCurrent bank details and account holder of the business partner (S/4HANA)BUT0BK-PARTNER = CDHDR-OBJECTIDECC + S/4
BUT000Business Partner: General DataBusiness partner GUID and nameBUT000-PARTNER = BUT0BK-PARTNERECC + S/4
CVI_VEND_LINKAssignment Between Vendor and Business PartnerMapping from business partner to vendor numberCVI_VEND_LINK-PARTNER_GUID = BUT000-PARTNER_GUIDECC + S/4
LFBKVendor Master: Bank DetailsVendor bank details (for ECC change documents)LFBK-LIFNR = LFA1-LIFNRECC + S/4
LFA1Vendor Master (General Section)Vendor nameLFA1-LIFNR = CVI_VEND_LINK-VENDORECC + S/4
REGUHPayment Program Settlement DataPayments made to the new account after the changeREGUH-LIFNR = LFA1-LIFNR AND REGUH-XVORL = ' 'ECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_UDATEChange dateRange / multipleCDHDR-UDATEYes10.11.2026 – 16.11.2026
S_USERChanged byRange / multipleCDHDR-USERNAMENo—
S_PARTNRBusiness partnerRange / multipleBUT000-PARTNERNo—
S_LIFNRVendorRange / multipleLFA1-LIFNRNo—
S_ZBUKRPaying company codeRange / multipleREGUH-ZBUKRNo1000
P_PAYDYPayment check after change (days)Single value—No30
P_MASKMask account numbersCheckbox—NoX

Output columns

#ColumnSource
1Change dateCDHDR-UDATE
2TimeCDHDR-UTIME
3Changed byCDHDR-USERNAME
4TransactionCDHDR-TCODE
5Business partnerBUT000-PARTNER
6VendorLFA1-LIFNR
7Vendor nameLFA1-NAME1
8FieldCDPOS-FNAME
9Change typeCDPOS-CHNGIND
10Old valueCDPOS-VALUE_OLD
11New valueCDPOS-VALUE_NEW
12Account holderBUT0BK-KOINH
13First payment dateREGUH-LAUFD
14Amount paidREGUH-RWBTR
15CurrencyREGUH-WAERS
16RiskCalculated Payment to new account within N days: High; user outside master data: +1; account holder mismatch: flag

Sample output

Change dateTimeChanged byTransactionBusiness partnerVendorVendor nameFieldChange typeOld valueNew valueAccount holderFirst payment dateAmount paidCurrencyRisk
11/11/202616:42:10MDVERI01BP1000245100245Atlas AmbalajIBANUTR** **** 4417TR** **** 9023Atlas Ambalaj San. ve Tic. A.Ş.11/13/2026186,400TRYHigh
11/12/202609:15:33SATINALMA03BP1000512100512Ege KimyaIBANITR** **** 6610Mavi Danışmanlık Ltd.0TRYHigh – account holder mismatch
11/14/202611:03:47MDVERI02BP1000387100387Delta MetalKOINHUDelta Metal Ltd.Delta Metal San. Ltd. Şti.Delta Metal San. Ltd. Şti.0TRYLow
11/15/202614:20:05MDVERI01BP1000733100733Kuzey LojistikBANKLU0062****0046****Kuzey Lojistik A.Ş.12/04/202652,750TRYMedium
A view built with fictional sample data; not real system data.

How does the report work?

  1. Change documents in the selected date range are read from CDHDR: in S/4HANA the business partner bank details object (BUPA_BUK, table BUT0BK), in ECC vendor master data the object KRED (table LFBK).
  2. Lines for the bank fields are taken from CDPOS (BANKS, BANKL, BANKN, IBAN, KOINH); the change type (CHNGIND: I insert, U update, D delete) and the old and new values are read.
  3. The business partner is derived from the object key; through CVI_VEND_LINK and BUT000-PARTNER_GUID it is mapped to the vendor number and the vendor name is read from LFA1. In ECC the vendor number is in the key directly.
  4. Payment check: in REGUH entries of real runs (XVORL blank), a payment to the same vendor within N days after the change date and to the new account (ZBNKN/ZBNKL or ZIBAN) is searched; the first payment date and amount are added.
  5. Risk: a payment to the new account within N days after the change is High; one level higher if the changing user is not in the master data group; a mismatch between the account holder name and the vendor name is flagged as well.
  6. With “Mask account numbers” selected, only the last four digits of account and IBAN values are shown.

Performance notes

Always read CDHDR with the object class and date range; access CDPOS with the full key. Read REGUH only for the vendors found and the date range. Running it as a weekly background job and emailing it to internal control is sufficient.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document Double-clicking the business partner opens the change history in BP.
  • Export to Excel
  • Runs as a background job
  • Send the result by email The weekly list can be sent to the internal control team.

Authorization objects

  • B_BUPA_GRPDisplay authorization by business partner grouping
  • F_LFA1_BUKDisplay authorization for vendor data by company code

Frequently asked questions

Does the report show the full IBAN?

Not by default; account and IBAN values are masked and only the last four digits are visible. The unmasked view can be restricted with a separate authorization.

Is a vendor bank change caught if it was made with old transactions instead of BP?

In ECC systems vendor master changes are written to the KRED change document object, which the report also reads. In S/4HANA vendor bank details are kept on the business partner, so changes appear in the business partner bank object.

What if no change documents are written?

Bank fields write change documents as standard. At installation the report warns if the selected objects have no entries in the last 90 days, so a problem with the change document settings gets noticed.

Packages that include this solution

BASIS Package Custom

SAP Access and Payment Risk Audit Pack

A six-component pack that brings together the controls asked most often in the yearly IT and finance audit: users with critical authorizations, …

6 components · v1.0

Related reports

FI Report Custom ALV report

Vendor Open Items Aging Report

A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …

BSIK · LFA1 · LFB1 · T001

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: Business Partner and Vendor Bank Details Change Control Report