Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: CNV_20100 - Messageclass for chart of account conversion
Message number: 200
Message text: Addit. rules for autom. recon.: Interval limit &1 will not be converted
The system found that the value &V1& was entered in the additional rules
for automatical reconciliation (transaction OB74, line &V2& &V3&).
However this value does not correspond to an existing account and is not
maintained in the mapping table for 'other accounts'.
This means that this value will not be converted.
Either check the additional rules after the conversion, or include the
interval limit in the mapping table for 'other accounts' (activity
<ZK>Specify Mapping Values (Chart of Accounts)</>).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
&ADDITIONAL_HINTS&Error message extract from SAP system. Copyright SAP SE.
CNV_20100200
- Addit. rules for autom. recon.: Interval limit &1 will not be converted ?The SAP error message CNV_20100200 typically occurs during the data migration process, particularly when using the SAP S/4HANA Migration Cockpit or other data migration tools. This error indicates that there is an issue with the conversion of interval limits for automatic reconciliation rules.
Cause:
The error message "Addit. rules for autom. recon.: Interval limit &1 will not be converted" suggests that there is a problem with the specified interval limit for automatic reconciliation rules. The specific causes can include:
- Invalid Interval Limits: The interval limit specified may not be valid or may not meet the criteria required for conversion.
- Data Inconsistencies: There may be inconsistencies in the data that prevent the conversion from being executed properly.
- Configuration Issues: The configuration settings for automatic reconciliation rules may not be set up correctly in the source system.
- Missing Customization: If there are custom rules or settings that are not recognized in the target system, this can lead to conversion issues.
Solution:
To resolve this error, you can take the following steps:
- Check Interval Limits: Review the interval limits defined in the source system. Ensure that they are valid and conform to the expected format and range.
- Data Validation: Validate the data in the source system to ensure there are no inconsistencies or errors that could affect the conversion process.
- Review Configuration: Check the configuration settings for automatic reconciliation rules in both the source and target systems. Ensure that they are aligned and that all necessary settings are in place.
- Custom Rules: If there are custom rules or settings, ensure that they are properly defined in the target system. You may need to create or adjust these rules to match the source system.
- Consult Documentation: Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or updates that address this error.
- Use Migration Tools: Utilize SAP's migration tools or transaction codes (like LTMC) to assist in the migration process, as they may provide additional checks and balances.
Related Information:
If the issue persists after following these steps, consider reaching out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
CNV_20100199
CoA &1 is already country-specific CoA for participating company codes
What causes this issue? According to the mapping table, you want to transfer or restructure the existing chart of accounts &V1& into &V2&...
CNV_20100198
Country-specific CoA &1 was added to CoA list (T004)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20100201
Merge at A/B level: No priority control for merge to account &1
What causes this issue? The system found that two or more old G/L accounts are mapped to target &V1&, but the priority indicator is set for n...
CNV_20100202
Merge at A level: No priority control for merge to cost element &1
What causes this issue? The system found that two or more old cost elements are mapped to target &V1&, but the priority indicator is set for ...
Click on this link to search all SAP messages.