Do you have any question about this error?
Message type: E = Error
Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing
Message number: 203
Message text: Currency in CO doesn't match the ones in FI (ledger &1/company code &2)
The currency type set as a currency in controlling (KSL) in ledger
configuration doesn't match any of the currency types set in FI.
In FINSC_LD_CMP: CURTPK = '&V3&'
In T001A: &V4&
This leads to a database mismatch.
Please contact SAP.
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.
FINS_ACDOC_CUST203
- Currency in CO doesn't match the ones in FI (ledger &1/company code &2) ?The SAP error message FINS_ACDOC_CUST203 indicates a mismatch between the currency used in the Controlling (CO) module and the currency used in the Financial Accounting (FI) module for a specific ledger and company code. This error typically arises during the posting of documents when the currency settings in CO do not align with those in FI.
Cause:
- Currency Configuration Mismatch: The currency settings in the CO module (such as the controlling area or cost center) do not match the currency settings in the FI module (such as the company code or ledger).
- Document Posting: When attempting to post a document, the system checks the currency settings in both modules. If they do not match, the error is triggered.
- Multiple Currencies: If the company code is set up to use multiple currencies, and the CO document is being posted in a currency that is not recognized or allowed in the FI settings, this error can occur.
Solution:
Check Currency Settings:
- Go to the configuration settings for both FI and CO.
- Ensure that the currency settings for the controlling area, company code, and any relevant cost centers or internal orders are consistent.
- Verify that the currency used in the CO document matches the currency defined in the FI settings.
Adjust Document Currency:
- If the document is being posted in a currency that is not valid, consider changing the currency of the document to match the FI settings.
- Ensure that the currency conversion settings are correctly configured if you are dealing with multiple currencies.
Review Master Data:
- Check the master data for the relevant cost centers, internal orders, and other CO objects to ensure that they are set up with the correct currency.
- Make sure that the controlling area is assigned to the correct company code and that the currency settings are aligned.
Consult with SAP Support:
- If the issue persists after checking the configurations, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration.
Related Information:
OBY6
(for company code settings), OKKP
(for controlling area settings), and KS01
(for cost center creation) to review and adjust the relevant settings.By following these steps, you should be able to resolve the FINS_ACDOC_CUST203 error and ensure that the currency settings in both FI and CO are aligned.
Get instant SAP help. Start your 7-day free trial now.
FINS_ACDOC_CUST202
1st add. curr type doesn't match the ones in FI (ledger &1/comp. code &2)
What causes this issue? The currency type set as first additional currency (OSL) in ledger configuration doesn't match any of the currency types...
FINS_ACDOC_CUST201
Correct the Customizing settings for ledgers for the universal journal
What causes this issue? There are inconsistencies in the Customizing settings for ledgers for the universal journal.System Response To prevent datab...
FINS_ACDOC_CUST204
Allocation indicator should not be empty (ledger &1/company code &2)
What causes this issue? The allocation indicator (KOKFI) in the table T001 is empty although there is a controlling area assigned to the company code...
FINS_ACDOC_CUST205
For CoCode &1, version &2, there is no entry in table FINSC_CMP_VERSNC.
What causes this issue? The content of tables FINSC_CMP_VERSNC and FINSC_CMP_VERSND seems to be outdated.System Response The reason for this could b...
Click on this link to search all SAP messages.