How To Fix CNV_20100072 - &1 and &2 have different authorization groups in company code &3

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_20100 - Messageclass for chart of account conversion

• Message number: 072

• Message text: &1 and &2 have different authorization groups in company code &3

What causes this issue?

Accounts &V1& and &V2& have different authorization groups in company
code &V3&.
This is determined by the indicator <zk>'Authorization group'
</> (field SKB1-BEGRU).
These accounts are to be converted into account &V4&. However problems
may occur due to the different settings.

System Response

The conversion can take place anyway.

How to fix this error?

You may have to adapt the mapping table.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100072 - &1 and &2 have different authorization groups in company code &3 ?

  The SAP error message CNV_20100072 indicates that there is a mismatch in authorization groups for two objects (usually related to master data or transactional data) within a specific company code. This error typically arises during data migration or conversion processes, particularly when using SAP's data migration tools.
  Cause:
  The error occurs when the system detects that two objects (e.g., cost centers, profit centers, etc.) that are being processed have different authorization groups assigned to them. Authorization groups are used in SAP to control access to certain objects based on user roles and permissions. When the authorization groups do not match, the system raises this error to prevent unauthorized access or inconsistencies in data handling.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify the Objects: Check the specific objects mentioned in the error message (represented by &1 and &2) and the company code (represented by &3). This will help you understand which objects are causing the issue.
  
  
  Check Authorization Groups: Review the authorization groups assigned to both objects. You can do this by navigating to the relevant transaction codes (e.g., for cost centers, you can use transaction code KS03 to display cost center details).
  
  
  Align Authorization Groups: If the authorization groups are indeed different, you will need to align them. This can be done by:
  
  Changing the authorization group of one of the objects to match the other.
  If necessary, consult with your security or authorization team to ensure that the change complies with your organization's security policies.
  
  
  
  Re-run the Migration Process: After making the necessary adjustments, re-run the migration or conversion process to see if the error is resolved.
  
  
  Consult Documentation: If you are using a specific migration tool or program, refer to the documentation for any additional steps or considerations that may be relevant to your situation.
  
  
  Related Information:
  
  Authorization Groups: These are defined in the SAP system and can be managed through transaction codes like SU21 (for creating and managing authorization objects) and PFCG (for role maintenance).
  Data Migration Tools: If you are using SAP's Migration Cockpit or other tools, ensure that you are following the best practices and guidelines provided by SAP for data migration.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context or solutions.
  
  If the issue persists after following these steps, consider reaching out to SAP support or your internal SAP team for further assistance.