How To Fix CNV_20200_CHECK161 - Same G/L account numbers used by different house bank account IDs

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20200_CHECK - Messages for check functions (company code merge)

• Message number: 161

• Message text: Same G/L account numbers used by different house bank account IDs

What causes this issue?

The same G/L account number is assigned to more than one house bank
account ID in company codes that will be merged (see table T012K 'House
bank account IDs'). The accounts with the same number would consequently
also be merged.

System Response

Error

How to fix this error?

It may be necessary to make a transfer posting for one (or several) of
the G/L accounts that are now in different company codes, but would no
longer be so after the merge.
If identical G/L account assignments to house bank account IDs were
already in the same company code before the conversion, this was either
intentional or an error, and the company code merge will not have any
influence on this situation (by default).

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20200_CHECK161 - Same G/L account numbers used by different house bank account IDs ?

  The SAP error message CNV_20200_CHECK161 indicates that the same General Ledger (G/L) account numbers are being used by different house bank account IDs during a data migration or conversion process. This situation can lead to inconsistencies in financial reporting and transaction processing, as each house bank account should ideally be linked to a unique G/L account.
  Cause:
  The error typically arises in the context of data migration, particularly when using SAP's Migration Cockpit or other data transfer tools. The root causes can include:
  
  Duplicate G/L Accounts: The same G/L account is assigned to multiple house bank accounts, which is not allowed in SAP.
  Incorrect Configuration: The configuration of house bank accounts may not have been set up correctly, leading to overlaps in G/L account assignments.
  Data Quality Issues: The source data being migrated may contain duplicates or inconsistencies.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify Duplicates:
  
  Use transaction codes like FS00 (G/L Account Master) or FI12 (House Bank) to review the G/L accounts and house bank accounts.
  Check for any house bank accounts that are assigned the same G/L account.
  
  
  
  Reassign G/L Accounts:
  
  If you find that multiple house bank accounts are using the same G/L account, you will need to reassign one or more of these house bank accounts to a different G/L account.
  Ensure that each house bank account has a unique G/L account assigned.
  
  
  
  Data Cleansing:
  
  If the issue is due to data quality, cleanse the source data before migration. Ensure that there are no duplicates or incorrect mappings.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test migration to ensure that the error does not reoccur.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific migration process you are using, as there may be additional guidelines or best practices.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FS00 (G/L Account Master), FI12 (House Bank), and OBHB (House Bank Configuration).
  SAP Notes: Check for any SAP Notes related to the CNV_20200_CHECK161 error for additional insights or patches that may address the issue.
  Migration Cockpit: If you are using the SAP S/4HANA Migration Cockpit, review the migration templates and mappings to ensure they are set up correctly.
  
  By following these steps, you should be able to resolve the CNV_20200_CHECK161 error and ensure a smooth data migration process.