How To Fix FARR_RAI346 - Different comp. code in legacy data and revenue account. item &2 (&1/&3)

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 346

• Message text: Different comp. code in legacy data and revenue account. item &2 (&1/&3)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_RAI346 - Different comp. code in legacy data and revenue account. item &2 (&1/&3) ?

  The SAP error message FARR_RAI346 indicates that there is a discrepancy between the company code in the legacy data and the revenue account associated with a specific item. This error typically arises during the migration of legacy data into the SAP system, particularly in the context of Asset Accounting (FI-AA) or Revenue Accounting (FI-RA).
  Cause:
  
  Company Code Mismatch: The company code in the legacy data does not match the company code defined for the revenue account in the SAP system.
  Incorrect Configuration: The revenue account may not be properly configured in the system, leading to inconsistencies.
  Data Migration Issues: During the data migration process, the legacy data may have been incorrectly mapped or imported, resulting in mismatched company codes.
  
  Solution:
  
  Verify Company Codes: Check the company code in the legacy data and ensure it matches the company code defined for the revenue account in SAP.
  Review Account Configuration: Go to the configuration settings for the revenue account in SAP and ensure that it is set up correctly for the relevant company code.
  Data Mapping: If you are migrating data, review the mapping of legacy data to ensure that the company codes are correctly aligned.
  Adjust Legacy Data: If necessary, adjust the legacy data to ensure that the company code matches the revenue account in SAP.
  Consult Documentation: Refer to SAP documentation or guides related to data migration and asset accounting to ensure compliance with best practices.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBY6 (to check company code settings) or OAAQ (to check asset account settings) to investigate the issue further.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling legacy data migration.
  Testing: After making adjustments, conduct thorough testing to ensure that the error is resolved and that data integrity is maintained.
  
  If the issue persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.