Do you have any question about this error?
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 119
Message text: Priority control does not work for merge to account &2 in company code &3
When checking the priority indicators, the system found that the
priority indicator in the mapping table was set only once for all merges
to target account &V2& (which is correct).
The priority indicator was set for the following mapping:
&V1& -> &V2&
In company code &V3&, the source account &V1& does not exist, while at
least two other accounts are merged to target account &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
As the source account &V1& with prio = X does not exist in company code
&V3&, it is not clear which settings will take priority when the other
accounts in this company code are merged to target account &V2&.
Maintain the priority indicator for target account &V2& in company code
&V3& via activity 'Maintain B Segment Merges'. Alternatively check the
settings for the relevant target account &V2& after the conversion.
&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 account merges.
The super priority is mainly useful for tables whose key contains the
chart of accounts, but no other field that needs to be converted in a
chart of accounts conversion, such as account assignment (table T030 and
others).
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 prevail 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.
CNV_20100119
- Priority control does not work for merge to account &2 in company code &3 ?The SAP error message CNV_20100119 indicates an issue related to priority control during a merge operation for accounts in a specific company code. This error typically arises in the context of data migration or conversion processes, particularly when using SAP's tools for data transformation, such as the SAP S/4HANA Migration Cockpit or other data migration tools.
Cause:
The error message suggests that there is a problem with the priority control settings for the merge operation. This can occur due to several reasons:
- Incorrect Configuration: The priority settings for the accounts being merged may not be correctly configured.
- Data Inconsistencies: There may be inconsistencies in the data of the accounts being merged, such as missing or conflicting information.
- Company Code Issues: The specified company code may not be set up correctly or may not allow for the merging of accounts as intended.
- Technical Limitations: There may be technical limitations or restrictions in the system that prevent the merge operation from being executed as expected.
Solution:
To resolve the error, you can take the following steps:
- Check Configuration: Review the configuration settings for the priority control related to account merging. Ensure that the settings are correctly defined for the accounts involved.
- Data Validation: Validate the data for the accounts being merged. Look for any inconsistencies or missing information that could be causing the issue.
- Review Company Code Settings: Ensure that the company code specified in the error message is correctly set up and that it allows for the merging of accounts.
- Consult Documentation: Refer to SAP documentation or notes related to the specific migration or conversion process you are using. There may be specific guidelines or prerequisites that need to be followed.
- Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as there may be bug fixes or enhancements related to this issue.
- Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant context to help them diagnose the issue.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
CNV_20100118
There are no interval limits requiring maintenance
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20100117
There are duplicate CostEl groups or CO acct groups; maintenance required
What causes this issue? The check showed that cost element groups or CO account groups that have the same name, but are currently in different charts...
CNV_20100120
Status of activity '&1' changed from error to warning
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20100121
Settings confirmed on &1 by &2; status changes were made
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.