How To Fix FARR_RAI846 - Item &1: revenue account neither sent nor determined correctly via rules

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 846

• Message text: Item &1: revenue account neither sent nor determined correctly via rules

What causes this issue?

For revenue accounting item &v1& the mandatory attribute "revenue
account" was neither transferred by the integration component nor was it
determined by applying determination rules.

For revenue accounting item &v1& the mandatory attribute "revenue
account" was neither transferred by the integration component nor was it
determined by applying a BRFplus rule.

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?

If the revenue account should be determined using determination rules,
make sure that you maintain a determination rules for revenue accounting
in Customizing.

If the revenue account should be determined using BRFplus, make sure
that you maintain a BRFplus application for revenue accounting class
&v2& in Customizing.

INCLUDE RAI_NA_CUST_1 OBJECT DOKU ID TX

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_RAI846 - Item &1: revenue account neither sent nor determined correctly via rules ?

  The SAP error message FARR_RAI846 indicates that there is an issue with the revenue account determination for a specific item in the context of the SAP Revenue Accounting and Reporting (RAR) module. This error typically arises when the system is unable to determine the appropriate revenue account for an item based on the defined rules or when the account is not provided in the transaction.
  Cause:
  
  Missing Configuration: The revenue account determination rules may not be properly configured in the system. This could be due to missing entries in the configuration tables or incorrect settings.
  Item Data Issues: The item in question may not have the necessary data (like account assignment) that allows the system to determine the revenue account.
  Inconsistent Master Data: There may be inconsistencies in the master data related to the item, such as missing or incorrect account assignments in the material master or customer master.
  Transaction Type: The transaction type being used may not be mapped correctly to the revenue account determination rules.
  
  Solution:
  
  Check Configuration: Review the configuration settings for revenue account determination in the RAR module. Ensure that the rules are correctly defined and that all necessary accounts are included.
  
  Navigate to the configuration path: SPRO > Financial Accounting > Revenue Accounting and Reporting > Revenue Account Determination.
  
  
  Review Item Data: Check the item data for the specific item that is causing the error. Ensure that all required fields are filled out correctly and that the item is properly set up in the system.
  Master Data Validation: Validate the master data for the item, including the material master and customer master, to ensure that all relevant account assignments are present and correct.
  Transaction Type Mapping: Ensure that the transaction type used for the item is correctly mapped to the revenue account determination rules. This may involve checking the settings for the specific transaction type in the RAR configuration.
  Testing: After making any changes, perform a test transaction to see if the error persists. If it does, further investigation may be needed.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on configuration and troubleshooting.
  Documentation: Refer to the official SAP documentation for Revenue Accounting and Reporting for detailed information on account determination and configuration.
  Community Forums: Engage with SAP community forums or support channels for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary changes to resolve it.