Do you have any question about this error?
Message type: E = Error
Message class: FARR_RAI - Revenue Accounting Item
Message number: 388
Message text: Local currency in legacy data condition does not match company code &2
The local currency keys in legacy data condition item &v1& do not match
the
<DS:TRAN.OB22>local currency settings</> of the related company code
&V2&.
The legacy data cannot be saved for item &v1&.
Correct the legacy data and resend the 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.
FARR_RAI388
- Local currency in legacy data condition does not match company code &2 ?The SAP error message FARR_RAI388 indicates that there is a mismatch between the local currency in the legacy data and the company code's local currency in the system. This error typically occurs during the migration or integration of legacy data into the SAP system, particularly in the context of Asset Accounting (FI-AA).
Cause:
- Currency Mismatch: The local currency defined in the legacy data does not match the local currency set for the company code in SAP.
- Incorrect Configuration: The company code may have been configured with a different local currency than what is present in the legacy data.
- Data Import Issues: During data import, the legacy data may not have been correctly mapped to the corresponding company code.
Solution:
To resolve this error, you can take the following steps:
Verify Company Code Currency:
- Check the local currency assigned to the company code in SAP. You can do this by navigating to the transaction code OBY6 (or through the configuration menu).
- Ensure that the local currency of the company code matches the local currency in the legacy data.
Adjust Legacy Data:
- If the legacy data is incorrect, you may need to adjust it to match the local currency of the company code.
- This may involve converting amounts to the correct currency or updating the legacy data to reflect the correct currency.
Data Mapping:
- Ensure that the data mapping during the import process is correctly set up to match the local currency of the company code.
- Review the data import templates or tools being used to ensure they are configured correctly.
Consult Documentation:
- Review SAP documentation or notes related to the specific error message for any additional guidance or updates that may be relevant.
Testing:
- After making the necessary adjustments, perform a test import to ensure that the error does not reoccur.
Seek Support:
- If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who can provide further assistance.
Related Information:
By following these steps, you should be able to resolve the FARR_RAI388 error and successfully import your legacy data into the SAP system.
Get instant SAP help. Start your 7-day free trial now.
FARR_RAI387
Conflicting cost conditions in predecessor chain (&3/acct.pr. &2)
What causes this issue? You have processed one or more revenue accounting items that are part of a predecessor document chain, that is, they refer ei...
FARR_RAI386
More than one main cost condition in predecessor chain (&3/acct.pr. &2)
What causes this issue? You have processed one or more revenue accounting items that are part of a predecessor document chain, that is, they refer ei...
FARR_RAI389
Exchng diff. condition &1 contain amounts in 1st local or trans. currency
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_RAI390
Item &1: Condition of type &2 contains trans. currency amount or key
What causes this issue? Legacy data condition items of condition type &v2& (Exchange rate differences) are not supposed to contain an amount ...
Click on this link to search all SAP messages.