Skip to Content
Technical Articles

SAP S/4HANA Business Partner: Handling of IBAN with CVI

Introduction

There are two different scenarios how to manage a bank account and an IBAN in business partner master data. There are also differences in handling of IBANs when using the Business Partner without (for example for FSCM only) or with CVI (Customer-Vendor-Integration).

In this blog post I am going to provide an overview how the respective data will be stored in different scenarios.

As the Business Partner is the leading object to update customer and vendor master data, CVI is impacting the way how an IBAN is stored for all the three objects. The bank data is part of the shared data between these objects. In fact, the objects are kept redundantly.

This blog is related to SAP S/4HANA. It is based on SAP S/4HANA 1909, but the information is valid for all previous releases as well.

We differentiate two main scenarios:

  1. Manage IBAN in addition to a bank account
  2. IBAN ONLY to handle IBAN without bank account number

The information how to enter an IBAN in both scenarios is well described in note 2229348 – Guide “How to enter a new IBAN”. This blog post is rather about the data that are stored in respective tables.

 

Bank Detail and IBAN Tables KNBK/LFBK, BUT0BK, TIBAN

Please let me refer to the general data model of bank account- and IBAN-handling in case of using Customer and Vendor objects. For both objects the bank account information is stored in the bank details tables. Both tables are having the same structure except customer or vendor number in the key:

  • Customer Master (Bank Details): KNBK
  • Vendor Master (Bank Details): LFBK

None of these tables can store the IBAN-information.

In case an IBAN is added an entry in table TIBAN (IBAN) is generated. This table is used for all entered or generated IBAN’s from any applications. Its key consists of full bank account information (country, bank key, bank account, control key). It can be considered as a “central IBAN management”: unique combination of bank details leads exactly to one IBAN. This IBAN is stored once in table TIBAN.

Bank data at Business Partner level is stored in table BUT0BK. Beside the Business Partner number its key consists of a Bank details ID (subsequent number or free characters, is synchronized by CVI with field “Partner Bank Type” in KNBK/LFBK). Unique combination of bank key and bank account is checked by the business logic.
BUT0BK-table would be able to store an IBAN-information. The cases when this field is filled or not will be described in this blog.

 

Scenario: Manage Bank Account and IBAN (Classic Way)

This is the classic scenario of managing IBANs in SAP S/4HANA.

Dependent applications (such as FI AR/AP) are still consuming the classic bank data retrieved from customer and vendor (tables KNBK, LFBK and TIBAN). As the Business Partner is now the leading object

  • the bank details are synchronized with CVI from Business Partner (BUT0BK) to the Customer (KNBK) and Vendor data (LFBK).
  • the IBAN is initially generated out of the Business Partner. Customer and Vendor objects are referring to the same IBAN in table TIBAN by using the bank details:

 

Table BUT0BK (BP Bank Data)

When checking the table content, we see that the IBAN-field in BUT0BK is not updated here (the IBAN is stored in table TIBAN).

  • Key: PARTNER (Business Partner), BKVID (Bank Details ID)
  • Saved attributes: BANKS (Bank Country), BANKL (Bank Key), BANKN (Account),
  • Field IBAN remains empty

Please note: We would see the same behavior when a Business Partner without CVI (for example only role 000000 has been created) is created.

 

Table TIBAN (IBAN)

This table is now updated with an entry for the IBAN:

  • Key: BANKS (Country) BANKL (Bank Key), BANKN (Account)
  • Field IBAN is filled here
  • The origin of this entry is saved in to fields TABNAME (Table Name) and Tabkey (Key to origin): BUT0BK and BP number

Tables KNBK / LFBK (Customer/Vendor Bank Details)

  • Key: KUNNR (Customer Number) or LIFNR (Vendor Number), BANKS (Bank Country), BANKL (Bank Key), BANKN, (Bank Account)
  • IBAN-Field is not available

 

Scenario: IBAN ONLY (without Bank Account)

This scenario describes how the data is saved once you have decided to store IBAN without account number (“IBAN ONLY”).

Also, in this case some dependent applications (such as FI AR/AP) are still consuming the IBAN data retrieved from table TIBAN. As the Business Partner is now the leading object

  • the bank details are synchronized with CVI from Business Partner (BUT0BK) to the Customer (KNBK) and Vendor data (LFBK).
  • the IBAN is now generated initially for the Business Partner only (table BUT0BK). Once CVI is creating Customer and Vendor bank data (tables KNBK, LFBK) they must continue to refer to the respective IBAN in table TIBAN. Please remember here that tables KNBK and LFBK do not contain any IBAN information.

 

Table BUT0BK (BP Bank Data)

Once IBAN ONLY is activated the IBAN will be stored into this table.

  • Key: PARTNER (Business Partner), BKVID (Bank Details ID)
  • Saved attributes: BANKS (Bank Country), BANKL (Bank Key),
  • Field BANKN (Account) remains empty in this case
  • Field IBAN contains the respective entry

Table TIBAN (IBAN)

Here we are now facing a special situation:

If the Business Partner is not synchronized neither with a Customer nor with a Vendor master table TIBAN won’t be updated (no CVI = no TIBAN). This is the case for example for pure FI-CA Business Partners or any BP without CVI-relevant roles.

When CVI for updating Customer and/or Vendor master data is triggered, table TIBAN will be updated to keep downwards compatibility (CVI = entry in TIBAN).

  • Key: BANKS (Country) BANKL (Bank Key)
  • Key BANKN (Account) is updated now due to technical reason with a dummy account value (such as ‘<IBAN>000000000001’)
  • Field IBAN is filled
  • The origin of this entry is not saved into fields TABNAME (Table Name) and Tabkey (Key to origin)

Tables KNBK / LFBK (Customer/Vendor Bank Details)

  • Key: KUNNR (Customer Number) or LIFNR (Vendor Number), BANKS (Bank Country), BANKL (Bank Key) are filled with respective values
  • Key BANKN (Bank Account) is updated with the same dummy account value (such as ‘<IBAN>000000000001’)
  • IBAN-Field is not available

 

Required Settings for IBAN ONLY

For setting up the IBAN ONLY scenario there are several notes available. An overall overview (mainly for FI-CA settings) is provided in KBA 2115809 – FI-CA IBANONLY: IBAN ohne BIC / IBAN without BIC.

With note 1029195 – Bank without account number support in Master Data Sync. the switch to activate IBAN ONLY in master data synchronization (CVI) has been introduced already in SAP ECC. It is also available in SAP S/4HANA. You will find view V_TB056 here

  • IMG: SAP Customizing Implementation Guide -> Cross-Application Components -> SAP Business Partner -> Activation Switch for Functions

One important remark with regards to use IBAN ONLY for IDocs DEBMAS and CREMAS: please check note 2754287 – DEBMAS/CREMAS IBAN without Bank Account Number functionality. This note enables IBAN ONLY for both IDoc types.
Please also consider that you need to activate Switch MM_SFWS_SC2 (business function LOG_MM_CI_2). More details you fill with KBA 1664137 – IBAN field is not getting updated by CREMAS / DEBMAS Idoc.

Conclusion

As you could see there are 2 options to manage an IBAN in Business Partner master data. On the one hand side we have the classic way with bank key, bank account and IBAN. On the other hand side we have the option to manage IBAN ONLY with bank key and IBAN. This can be covered within the Business Partner bank data (BUT0BK).
However when we have to an IBAN in Customer and/or Vendor master data, CVI still has to ensure downwards compatibility. This leads to an additional entry in table TIBAN.

Let me point to one example where you can expect this behavior: Imagine an SAP ECC system with Business Partner master data, for example for FI-CA. IBAN ONLY is activated, and so no TIBAN-entries are generated. Customer masters were created with transaction like KCLJ and not with CVI. When converting to SAP S/4HANA you have to use CVI to create Customer master data – and TIBAN-entries are created now.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.