How To Fix FARR_RAI349 - Cost condition must be main condition type for item ID &1/cond. type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 349

• Message text: Cost condition must be main condition type for item ID &1/cond. type &2

What causes this issue?

Cost condition must be main condition type for item ID &v1& and
condition type &v2&.
This check is not performed for contract acquisition costs.

System Response

It's not possible to transfer the items. Please make sure that the
sender component sends the revenue accounting items with the expected
values or correct the values in the revenue accounting item monitor.

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_RAI349 - Cost condition must be main condition type for item ID &1/cond. type &2 ?

  The SAP error message FARR_RAI349 indicates that there is an issue with the condition types in a financial transaction, specifically related to the cost condition type in the context of asset accounting or related modules. This error typically arises when the system expects a specific condition type to be the main condition type for a given item, but it is not set up correctly.
  Cause:
  
  Incorrect Configuration: The condition type specified in the error message is not set as the main condition type in the configuration settings for the relevant transaction or document.
  Data Entry Error: There may be an error in the data entry where the wrong condition type is being used for the item.
  Missing Customization: The system may not have been customized properly to recognize the condition type as the main one for the specific transaction.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the relevant module (e.g., Asset Accounting).
  Verify that the condition type in question is set as the main condition type for the relevant transaction type.
  If necessary, adjust the configuration to ensure that the correct condition type is marked as the main one.
  
  
  
  Review Document:
  
  Check the document or transaction that triggered the error.
  Ensure that the correct condition types are being used and that they align with the expected configuration.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for guidance on setting up condition types and understanding their roles in transactions.
  
  
  
  Testing:
  
  After making changes, test the transaction again to ensure that the error no longer occurs.
  
  
  
  Seek Help:
  
  If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in checking or adjusting condition types (e.g., SPRO for configuration).
  SAP Notes: Look for SAP Notes related to this error message for any patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.