Message type: E = Error
Message class:  CNV_20100 - Messageclass for chart of account conversion 
Message number: 139
Message text: Priority control does not work for merge to sec. CostEl &2 in CoAr &3
When checking the priority indicators, the system found that the
priority indicator was set exactly once for all merges to the target
cost element &V2& in the mapping table (which is correct).
The priority indicator is set for the following mapping:
&V1& -> &V2&
Cost element &V1& is a secondary cost element.
In controlling area &V3&, the source cost element &V1& does not exist,
while at least two other cost elements are going to be merged into
target cost element &V2&.
Because the source cost element &V1& with priority = X does not exist in
controlling area &V3&, it is not clear which settings will take priority
when the other cost elements in this controlling area are merged into
target cost element &V2&.
If required, execute the activity <ZK>Maintain B Segment Merges</> to
explicitly specify the source cost element for controlling area &V3&
whose <DS:TX.CNV_20100_TX_BSEGMENT>B segment</> settings you want to use
for target cost element &V2&.
&ADDITIONAL_HINTS&
Note that the priority indicator must not be set more than <ZH>once</>
for all merges to a given target account. 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/cost element) take priority during a merge
to a given target if <ZH> more than one</>  account or cost element from
the <ZH>same</> chart of accounts is merged into this target.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CNV_20100139 typically relates to issues encountered during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This specific error indicates that there is a problem with the priority control for merging secondary cost elements in a particular controlling area.
Cause: The error message suggests that the system is unable to apply the priority control for merging secondary cost elements due to one or more of the following reasons:
Configuration Issues: The controlling area or cost element settings may not be properly configured to allow for the merging of secondary cost elements. Data Inconsistencies: There may be inconsistencies or conflicts in the data being migrated, such as duplicate entries or incorrect mappings. Missing Authorizations: The user executing the migration may not have the necessary authorizations to perform the operation. Technical Limitations: There may be technical limitations or bugs in the version of SAP being used that affect
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
CNV_20100138 CoA &1 is implemented as country-specific CoA: No CoCds selected
What causes this issue?  Chart of accounts &V1& is meant to be implemented as country-specific chart of accounts of &V2& with name &am...
CNV_20100137 For CoA &1, no company code was indicated (country-specific CoA)
What causes this issue?  When maintaining the mapping table, you stated that you want to convert the chart of accounts &V1&. However you selec...
CNV_20100140 No scenarios could be determined yet
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20100141 Error during update to table &1, field &2, package &3.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.