How To Fix CNV_20100139 - Priority control does not work for merge to sec. CostEl &2 in CoAr &3

SAP Error Message - Details

• 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

What causes this issue?

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&.

System Response

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&.

How to fix this error?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV_20100139 - Priority control does not work for merge to sec. CostEl &2 in CoAr &3 ?

  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 the merging process.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Review the configuration settings for the controlling area and ensure that the cost elements are set up correctly.
  Verify that the merging rules for secondary cost elements are properly defined.
  
  
  
  Data Validation:
  
  Perform a thorough validation of the data being migrated. Look for duplicates or inconsistencies in the cost element data.
  Use transaction codes like KAH1 (Create Cost Element) and KAH2 (Change Cost Element) to check the existing cost elements.
  
  
  
  Review Authorizations:
  
  Ensure that the user executing the migration has the necessary authorizations to perform the operation. Check the roles and permissions assigned to the user.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes or patches that address this specific error. There may be updates or fixes available that resolve the issue.
  
  
  
  Log Analysis:
  
  Analyze the logs generated during the migration process for any additional error messages or warnings that could provide more context about the issue.
  
  
  
  Testing:
  
  If possible, conduct a test migration in a development or quality assurance environment to replicate the issue and test potential solutions without affecting production data.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error, including the context in which it occurs.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KSB1 (Cost Centers: Actual Line Items) and KOB1 (Order: Actual Line Items) to analyze cost elements and their usage.
  Migration Tools: Understand the tools and methodologies used for data migration in SAP S/4HANA, including the Migration Cockpit and Data Migration Workbench.
  Documentation: Review SAP documentation related to cost element accounting and data migration best practices to ensure compliance with recommended procedures.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.