Message type: E = Error
Message class:  CNV_20100 - Messageclass for chart of account conversion 
Message number: 186
Message text: No priority indicator set at B level for G/L account &1 &2 in CoCd &3
The system found that you did not set the priority indicator for the
<DS:TX.CNV_20100_TX_BSEGMENT>B segment</> merge for G/L account &V1&
&V2& (that will exist after the conversion) in company code &V3&.
Consequently, it is not clear which settings from which company code
will take priority during the conversion.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Either set the priority indicator for the relevant account in the
mapping table for B segment merges for accounts/cost elements, or check
the settings for the new account manually after the conversion.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CNV_20100186 indicates that there is no priority indicator set at the B level for a General Ledger (G/L) account in a specific Company Code (CoCd). This error typically arises during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.
Cause: Missing Priority Indicator: The error suggests that the G/L account does not have a priority indicator defined at the B level. The priority indicator is essential for determining how the system should handle the account during the migration process.
Configuration Issues: There may be configuration issues in the Financial Accounting (FI) module where the G/L accounts are not properly set up. Data Migration Settings: The settings in the data migration tool may not be correctly configured to recognize the priority indicators for the G/L accounts.
Solution: Check G/L Account Configuration: Go to the transaction code FS00 (G/L Account Master Record) and check the configuration of the
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
CNV_20100185 CoA merge: Source account &1 exists; implicit merge by CoA rename
What causes this issue?  As a consequence of the planned chart of accounts merge, implicit account merges will occur as well. When checking the G/L ac...
CNV_20100184 Target account &2 exists already, implicit merge by CoA rename
What causes this issue?  When checking the G/L accounts you want to merge, the system found that as a result of the chart of accounts change the accou...
CNV_20100187 CoA-related master data from CoA &1 was copied to CoA &3
What causes this issue?  The chart of accounts-specific part of the G/L account master records (table SKA1) of operative chart of accounts &V1&...
CNV_20100188 Priority set more than once at B level for cost element &1 &2 in CoAr &3
What causes this issue?  The system found that the priority indicator was set more than once in the <DS:TX.CNV_20100_TX_BSEGMENT>B segment</&...
Click on this link to search all SAP messages.