How To Fix CNV_20100196 - No priority indicator set at B level for cost element &1 &2 in CoAr &3

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 196

• Message text: No priority indicator set at B level for cost element &1 &2 in CoAr &3

What causes this issue?

The system found that no priority indicator is set for the
<DS:TX.CNV_20100_TX_BSEGMENT>B segment</> merge for cost element &V1&
&V2& (that will exist after the conversion) in controlling area &V3&.
This means that it is not clear which settings from which controlling
area will take priority in the merge.

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?

Either set the priority indicator in the mapping table for B segment
merges for the respective cost element, or check the settings for the
new cost element manually after the conversion.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100196 - No priority indicator set at B level for cost element &1 &2 in CoAr &3 ?

  The SAP error message CNV_20100196 indicates that there is no priority indicator set at the B level for a specific cost element in the context of a conversion or migration process, particularly in the area of Controlling (Co) and Asset Accounting (Ar). This error typically arises during data migration or conversion activities, especially when using SAP's Migration Cockpit or similar tools.
  Cause:
  
  Missing Configuration: The error usually occurs when the cost element does not have a priority indicator defined at the B level. This can happen if the configuration for the cost element is incomplete or if the necessary settings were not made during the setup of the cost element in the system.
  Data Migration Issues: If you are migrating data from a legacy system, the mapping of cost elements may not have been done correctly, leading to missing priority indicators.
  Custom Development: If there are custom developments or enhancements in the system, they might interfere with the standard behavior of cost element processing.
  
  Solution:
  
  
  Check Cost Element Configuration:
  
  Go to the transaction code OKB9 (or use the appropriate transaction for your version) to check the configuration of the cost element.
  Ensure that the priority indicator is set for the cost element at the B level. If it is missing, you will need to define it.
  
  
  
  Review Migration Settings:
  
  If you are using a migration tool, review the mapping and transformation rules to ensure that all necessary fields, including the priority indicator, are correctly populated.
  Make sure that the source data from the legacy system includes the required information.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific instructions or prerequisites that need to be followed.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test run of the migration process to ensure that the error does not occur again.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists after checking the configuration and migration settings, consider reaching out to SAP support for further assistance. They may provide additional insights or patches if this is a known issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKB9 (Cost Element: Maintain) and OBY6 (for company code settings).
  SAP Notes: Search for SAP Notes related to CNV_20100196 for any specific fixes or recommendations provided by SAP.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to resolve the error message CNV_20100196 and ensure that your cost elements are correctly configured for the migration process.