How To Fix FARR_RAI651 - No or incomplete legacy data available for item &1, acct. principle &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 651

• Message text: No or incomplete legacy data available for item &1, acct. principle &2

What causes this issue?

No legacy data or legacy data that have the flag XINCOMPLETE set could
be found for the revenue accounting item &V1& and the accounting
principle &V2&.

System Response

The revenue accounting item cannot be processed as the required minimum
information for legacy data for the migrated item is not available.
Table FARR_D_LEGACY must contain an entry with field XINCOMPLETE = SPACE
for the revenue accounting item key and accounting principle &V2&.

How to fix this error?

Check if the corresponding legacy data has been loaded completely for
the respective revenue accounting item.
If necessary, reload the legacy data for the source document.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_RAI651 - No or incomplete legacy data available for item &1, acct. principle &2 ?

  The SAP error message FARR_RAI651 indicates that there is no or incomplete legacy data available for a specific item and account principle in the context of Asset Accounting (FI-AA). This error typically arises during the migration of asset data or when trying to perform transactions that require historical data.
  Cause:
  
  Missing Legacy Data: The most common cause is that the required legacy data for the asset is not available in the system. This could happen if the data was not properly migrated from a previous system or if it was not entered correctly.
  Incomplete Data: The legacy data might be incomplete, meaning that some necessary fields or records are missing.
  Incorrect Configuration: There may be configuration issues in the asset accounting settings that prevent the system from recognizing the legacy data.
  Data Transfer Issues: Problems during the data transfer process, such as errors in the data extraction or loading phases, can lead to incomplete records.
  
  Solution:
  
  Check Legacy Data: Verify that the legacy data for the asset in question is present and complete. This includes checking the asset master data and any related historical transactions.
  Data Migration: If the legacy data is missing, you may need to perform a data migration process to ensure that all necessary historical data is transferred into the SAP system.
  Review Configuration: Ensure that the configuration settings for Asset Accounting are correct. This includes checking the account principles and ensuring they are set up to recognize the legacy data.
  Use Transaction AS91: If you need to create an asset with legacy data, you can use transaction code AS91 to enter the legacy asset data manually.
  Consult Documentation: Review SAP documentation or notes related to asset accounting and legacy data migration for any specific instructions or guidelines.
  SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if you suspect a bug or a more complex issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS01 (Create Asset), AS02 (Change Asset), AS03 (Display Asset), and AS91 (Create Asset with Legacy Data).
  SAP Notes: Check for any SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Data Migration Tools: If you are migrating data, consider using tools like SAP Data Services or LSMW (Legacy System Migration Workbench) to facilitate the process.
  Documentation: Review the SAP Asset Accounting documentation for best practices on data migration and handling legacy data.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.