How To Fix R1228 - Bank details &1 &2 &3 in the validity period are not unique

SAP Error Message - Details

• Message type: E = Error

• Message class: R1 - Business Partner Messages from S_BUPA_GENERAL

• Message number: 228

• Message text: Bank details &1 &2 &3 in the validity period are not unique

What causes this issue?

Bank details must be unique in the validity period with regard to the
key data country, bank number and account number.
If you want to create other bank details with an identical key, then the
validity of the new bank details may not overlap the validity of the
bank details that already exist.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Adjust the validity periods of the identical bank details accordingly.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message R1228 - Bank details &1 &2 &3 in the validity period are not unique ?

  The SAP error message R1228, which states "Bank details &1 &2 &3 in the validity period are not unique," typically occurs when there are duplicate bank details for a vendor or customer within a specified validity period. This can happen in various scenarios, such as when you are trying to create or update bank details in the vendor or customer master data.
  
  Cause:
  
  Duplicate Entries: The primary cause of this error is that there are multiple bank details for the same vendor or customer that overlap in their validity periods.
  Incorrect Data Entry: Sometimes, during data entry, users may inadvertently create duplicate records with the same bank account information.
  Data Migration Issues: If data has been migrated from another system, it may have resulted in duplicate bank details being imported into SAP.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Existing Bank Details:
  
  Go to the vendor or customer master data (transaction codes like XK03