How To Fix FARR_RAI702 - Status changed back to migration; check reconciliation keys and postings

FARR_RAI702 - Overview

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 702

• Message text: Status changed back to migration; check reconciliation keys and postings

What causes this issue?

The status of company code &v1& and accounting principle &v2& changed
from productive to migration.
This should only happen if additional documents need to be loaded from
an external system. Make sure the correct reconciliation keys and
posting periods are used for the additionally loaded documents.
<ZH>Note</>
The system prevents the processing of revenue accounting items
which are not related to the initial load as long as the status
is not reset to <LS>Production</>.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_RAI702 - Status changed back to migration; check reconciliation keys and postings ?

  The SAP error message FARR_RAI702 indicates that there is an issue with the status of a reconciliation key or posting in the context of asset accounting, particularly during the migration process. This error typically arises when there are inconsistencies or discrepancies in the data related to asset transactions or when the system is unable to reconcile the asset values correctly.
  Causes:
  
  Inconsistent Data: There may be inconsistencies in the asset master data or transaction data that prevent the system from completing the migration process.
  Missing Reconciliation Keys: The reconciliation keys required for the migration might be missing or incorrectly configured.
  Postings Issues: There could be issues with the postings related to the assets, such as incorrect amounts, missing entries, or unposted transactions.
  Configuration Errors: Incorrect configuration settings in the asset accounting module can lead to this error.
  Data Migration Issues: If you are migrating data from a legacy system, there may be issues with the data