How To Fix FARR_RAI771 - Different CO object numbers in predecessor chain (&1/acct.principle &2)

FARR_RAI771 - Overview

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 771

• Message text: Different CO object numbers in predecessor chain (&1/acct.principle &2)

What causes this issue?

Item &v3& is part of a predecessor document chain, that is, it either
refers to a predecessor document or is a predecessor document itself or
both.
Items of a predecessor document chain are aggregated during processing
and therefore must belong to the same CO object number.
The system tried to process one or more items of the predecessor
document chain that has item &v1& as its highest level predecessor
document. Not all of the processed items of this chain belong to the
same CO object number. Therefore, all items that belong to this chain
could not be processed.

System Response

The system cannot process item &v3& for accounting principle &v2&.

How to fix this error?

Contact SAP Support.

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_RAI771 - Different CO object numbers in predecessor chain (&1/acct.principle &2) ?

  The SAP error message FARR_RAI771 indicates that there is a discrepancy in the CO (Controlling) object numbers in the predecessor chain for a specific asset transaction. This typically occurs in the context of Asset Accounting (FI-AA) when there are inconsistencies in the assignment of cost objects (like cost centers, internal orders, etc.) across different transactions related to the same asset.
  
  Cause:
  
  Inconsistent CO Object Assignment: The error arises when the system detects that the CO object numbers (like cost centers or internal orders) assigned to the predecessor transactions of an asset are different from the current transaction.
  Data Entry Errors: Manual data entry errors can lead to different CO objects being assigned to related transactions.
  Changes in CO Object: If a CO object was changed or replaced in the system after the initial transaction was recorded, it can lead to inconsistencies.
  Incorrect Configuration: Configuration issues in the Asset Accounting module or the Controlling module can