How To Fix FARR_RAI673 - Revenue accounting contract &1 contains errors; check system log

FARR_RAI673 - Overview

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 673

• Message text: Revenue accounting contract &1 contains errors; check system log

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_RAI673 - Revenue accounting contract &1 contains errors; check system log ?

  The SAP error message FARR_RAI673 indicates that there are errors in a revenue accounting contract, and it prompts the user to check the system log for more details. This error typically arises in the context of SAP Revenue Accounting and Reporting (RAR) when there are inconsistencies or issues with the data related to a specific revenue contract.
  Causes:
  
  Data Inconsistencies: There may be missing or incorrect data in the revenue accounting contract.
  
  Configuration Issues: The configuration settings for revenue recognition may not be set up correctly.
  Validation Errors: The system may have encountered validation errors while processing the contract.
  Incomplete Master Data: Related master data (e.g., customer, product) may be incomplete or incorrect.
  System Updates: Recent updates or changes in the system may have introduced new validation rules or requirements.
  
  Solutions:
  
  
  Check the System Log: The first step is to check the system log for detailed error messages. This can provide specific information about what is wrong with