Do you have any question about this error?
Message type: E = Error
Message class: CNV_20410_CHECK - Messages for ERKRS checks
Message number: 100
Message text: Currency type 10 (Company code ledger) is not used in target op.conc.
Currency type 10 (Company code ledger) is not used in the target
operating concern. However, it is used in at least one source operating
concern.
The data related to currency type 10 will not be transferred from the
source operating concerns into the target operating concern.
This affects tables CE1<xxxx>, CE2<xxxx> and CE3<(>
<<)>xxxx>.
No action required.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message CNV_20410_CHECK100 indicates that there is an issue with the currency type 10 (which typically represents the company code ledger) not being used in the target operational concern during a data migration or conversion process. This error is often encountered during the use of SAP's data migration tools, particularly in the context of the SAP S/4HANA migration or other data conversion projects.
Cause:
- Currency Type Configuration: The target system may not be configured to use currency type 10 for the specified company code. This can happen if the target system's configuration does not align with the source system's currency settings.
- Missing Configuration: The company code ledger may not be set up correctly in the target system, leading to the absence of currency type 10.
- Data Mapping Issues: There may be issues with how data is being mapped from the source to the target system, particularly regarding currency types.
Solution:
Check Configuration:
- Verify the currency settings in the target system. Ensure that currency type 10 is configured for the relevant company code.
- Go to the transaction code OB22 (Define Currency Types) and check if currency type 10 is defined and assigned correctly.
Adjust Company Code Settings:
- Ensure that the company code in the target system is set up to use the same currency types as the source system. This can be checked in the company code settings (transaction code OBY6).
Data Mapping Review:
- Review the data mapping settings in the migration tool to ensure that currency types are correctly mapped from the source to the target system.
- If necessary, adjust the mapping to ensure that currency type 10 is included.
Consult Documentation:
- Refer to the SAP documentation or notes related to the specific migration or conversion process you are undertaking. There may be specific instructions or prerequisites that need to be followed.
Testing:
- After making the necessary adjustments, perform a test migration to see if the error persists. This will help confirm that the changes have resolved the issue.
Related Information:
By addressing the configuration and mapping issues related to currency type 10, you should be able to resolve the CNV_20410_CHECK100 error and proceed with your data migration or conversion successfully.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
CNV_20410_CHECK099 Op.concern &1 without currency type &2 ( &3 )
What causes this issue? Operating concern &V1& without currency type &a...
CNV_20410_CHECK098 Participating operating concerns have different currency types
What causes this issue? Participating operating concerns have different currenc...
CNV_20410_CHECK101 Data related to currency type &2 of Op.conc. &1 will not be transferred
What causes this issue? Data related to currency type &V2& ( &V3&am...
CNV_20410_CHECK258 No implicit operating concern merges
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.