Do you have any question about this error?
Message type: E = Error
Message class: CNV_20200_CHECK - Messages for check functions (company code merge)
Message number: 193
Message text: Company code &1, ledger &2 with currencies &3 and currency types &4
Company code &V1&, ledger &V2& with
Currencies (CURR1, CURR2, CURR3)= &V3& ;
Currency types (CURT1, CURT2, CURT3)= &V4& ;
Information
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.
CNV_20200_CHECK193
- Company code &1, ledger &2 with currencies &3 and currency types &4 ?The SAP error message CNV_20200_CHECK193 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 inconsistency or issue with the currency settings for a specific company code and ledger combination.
Cause:
The error message CNV_20200_CHECK193 is generally caused by one or more of the following issues:
Currency Configuration Issues: The specified company code and ledger may not have the correct currency settings configured. This can include missing or incorrect currency types or currencies that are not defined in the system.
Inconsistent Currency Types: The currency types defined for the ledger may not match the expected configuration for the company code. For example, if the ledger is set to use a specific currency type (like local currency or group currency), but the company code is not configured to support that currency type, this error can occur.
Data Migration Issues: During the data migration process, if the source data does not align with the target system's currency settings, this error can be triggered.
Solution:
To resolve the CNV_20200_CHECK193 error, you can take the following steps:
Check Currency Configuration:
- Go to the transaction code
OB22
to check the currency types assigned to the company code and ledger.- Ensure that the currency types (e.g., local currency, group currency) are correctly defined and assigned.
Verify Ledger Settings:
- Use transaction code
OB37
to check the ledger settings for the specified company code.- Ensure that the ledger is configured to use the correct currency types.
Review Migration Data:
- If you are migrating data, review the source data to ensure that it contains valid currency information that matches the target system's configuration.
- Make any necessary adjustments to the data before migration.
Consult Documentation:
- Refer to SAP documentation or notes related to the specific migration process you are using. There may be specific guidelines or prerequisites that need to be followed.
Contact SAP Support:
- If the issue persists after checking the configurations, consider reaching out to SAP support for further assistance. They may provide additional insights or solutions based on the specific context of your system.
Related Information:
OB22
(Define Currency Types), OB37
(Define Ledgers), and OBY6
(Define Company Code).By following these steps, you should be able to identify and resolve the underlying issue causing the CNV_20200_CHECK193 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
CNV_20200_CHECK192
Company code &1 not assigned to ledger &2
What causes this issue? One or more participating company codes are assigned to ledger &V2&. However, company code &V1& is not assign...
CNV_20200_CHECK191
Reference company code &1 did not post taxes
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20200_CHECK194
Company code &1, ledger &2 with fiscal year variant &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CNV_20200_CHECK195
Participating company codes have open asset postings
What causes this issue? The periodic posting run in FI-AA of one ore more company codes is not up to date. To ensure a consistent conversion, all ass...
Click on this link to search all SAP messages.