How To Fix FARR_RAI386 - More than one main cost condition in predecessor chain (&3/acct.pr. &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 386

• Message text: 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 either to a
predecessor document or are predecessor documents themselves.
Items of a predecessor document chain are aggregated during processing.
After aggregation, there must still be only one cost condition type
flagged as main condition type.
The system tried to process one or more items of the predecessor
document chain that has item &v1& as its highest level predecessor
document. After aggregation, there was more than one cost condition type
flagged as main condition type. Therefore, all items that belong to this
chain could not be processed.

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

System Response

The system cannot process the items for accounting principle &v2&.

How to fix this error?

Correct the revenue accounting items of the predecessor document chain
that lead to more than one main cost condition type and process the
items again.

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_RAI386 - More than one main cost condition in predecessor chain (&3/acct.pr. &2) ?

  The SAP error message FARR_RAI386 indicates that there is an issue with the cost conditions in the predecessor chain of an asset. Specifically, it means that there is more than one main cost condition found in the predecessor chain for the specified asset and accounting period. This can occur in the context of asset accounting when there are multiple cost conditions that are not properly aligned or configured.
  Cause:
  
  Multiple Main Cost Conditions: The error typically arises when there are multiple main cost conditions defined for the same asset in the predecessor chain. This can happen due to incorrect configuration or data entry.
  Incorrect Asset Transactions: If there have been multiple transactions affecting the asset that have not been properly reconciled or if there are inconsistencies in the asset master data.
  Data Migration Issues: If data has been migrated from another system, it may have resulted in duplicate or conflicting entries.
  
  Solution:
  
  Review Asset Master Data: Check the asset master data for the asset in question. Ensure that there is only one main cost condition defined.
  Analyze Predecessor Chain: Use transaction codes like AW01N (Asset Explorer) to analyze the predecessor chain of the asset. Look for any inconsistencies or duplicate entries.
  Adjust Cost Conditions: If you find multiple main cost conditions, you may need to adjust the cost conditions to ensure that only one is marked as the main condition.
  Check Transactions: Review any recent transactions related to the asset to ensure that they have been processed correctly and that there are no errors in the transaction history.
  Consult Documentation: Refer to SAP documentation or consult with your SAP support team for specific guidance on how to resolve this issue based on your system configuration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS02 (Change Asset), AS03 (Display Asset), and AW01N (Asset Explorer) for managing and reviewing asset data.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional insights or patches that can resolve the issue.
  Configuration Settings: Review the configuration settings in the Asset Accounting module to ensure that they are set up correctly and that there are no conflicting settings.
  
  If the issue persists after following these steps, it may be necessary to engage with SAP support for further assistance.