How To Fix CNV_20100201 - Merge at A/B level: No priority control for merge to account &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 201

• Message text: Merge at A/B level: No priority control for merge to account &1

What causes this issue?

The system found that two or more old G/L accounts are mapped to target
&V1&, but the priority indicator is set for none of these accounts.
If the priority indicator is not set, it is not clear which settings
will take priority when the accounts are merged to &V1&.
Besides, the check showed that the merge will be carried out at
<DS:TX.CNV_20100_TX_ASEGMENT>A level</> as well as at
<DS:TX.CNV_20100_TX_BSEGMENT>B level</>.
At B level, the following accounts in company code &V4& will be merged:
&V2& -> &V1&
&V3& -> &V1&

How to fix this error?

Set the priority indicator for <ZH>one</> of the entries with target
account &V1&.
&NOTE&
It is possible to do the conversion without setting the priority
indicator. In this case, however, you should check the A and B segment
settings for the account &V1& after the conversion.

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

&ADDITIONAL_HINTS&
This message is also displayed if the merge is implicit. In this case,
the log will contain another message for target &V1& that describes the
recommended next steps.
The priority indicator must not be set more than once for all merges to
a given target. This is also valid for cross-chart of accounts merges.
The super priority is mainly useful for merging records in tables that
have only a chart of accounts field, but no account/cost element field,
as well as in tables for which the priority indicator has not been set
at G/L account/cost element level so that it is not clear which of the
records is meant to take priority.
Note also that even if a <DS:TX.CNV_20100_TX_SUPERPRIO>super priority</>
was defined at chart of accounts level it is still not clear which
settings (from which account or cost element) will take priority during
a merge to a given target if <ZH> more than one</> account (cost
element) fromthe <ZH>same</> chart of accounts is merged into this
target.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100201 - Merge at A/B level: No priority control for merge to account &1 ?

  The SAP error message CNV_20100201 typically occurs during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is an issue with merging accounts at the A/B level, specifically that there is no priority control defined for the merge to the specified account.
  Cause:
  
  Missing Priority Control: The error suggests that the system does not have a defined priority for how to handle the merging of accounts. This can happen if the configuration for account merging is incomplete or not set up correctly.
  Data Inconsistencies: There may be inconsistencies in the data being migrated, such as duplicate accounts without a clear priority for which account should be retained.
  Configuration Issues: The settings in the migration tool or the underlying configuration in the SAP system may not be properly aligned to handle the merging of accounts.
  
  Solution:
  
  
  Define Priority Control:
  
  Go to the configuration settings for account merging in your SAP system.
  Ensure that you have defined a clear priority for the accounts that are being merged. This may involve specifying which account should take precedence in case of duplicates.
  
  
  
  Check Migration Settings:
  
  Review the settings in the migration cockpit or the tool you are using for data migration. Ensure that all necessary parameters for account merging are correctly configured.
  
  
  
  Data Cleansing:
  
  Before running the migration, perform a data cleansing exercise to identify and resolve any duplicate accounts or inconsistencies in the data. This may involve manually reviewing the accounts and determining which should be merged and which should be retained.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation related to the migration process and account merging. There may be specific guidelines or best practices that can help resolve this issue.
  
  
  
  Testing:
  
  After making the necessary adjustments, conduct a test migration to ensure that the error does not occur again. Monitor the logs for any other potential issues.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on account merging and migration processes.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps you have taken to resolve it.
  
  By following these steps, you should be able to address the CNV_20100201 error and successfully complete your data migration process.