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

SAP Error Message - Details

• 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 the contract.
  
  Use transaction code SLG1 to view the application log.
  Filter by the relevant object and date to find the specific error messages related to the contract.
  
  
  
  Review Contract Data: Go through the revenue accounting contract in question and verify that all required fields are filled out correctly. Look for:
  
  Missing or incorrect entries.
  Properly defined revenue recognition rules.
  
  
  
  Validate Master Data: Ensure that all related master data (customers, products, etc.) is complete and accurate. Check for any missing or incorrect entries.
  
  
  Configuration Check: Review the configuration settings for revenue accounting to ensure they align with the business requirements and that all necessary settings are activated.
  
  
  Reprocess the Contract: After correcting any identified issues, try to reprocess the revenue accounting contract to see if the error persists.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional guidance and troubleshooting steps.
  
  
  Seek Help from SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP support for assistance, providing them with the error details and any relevant logs.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FARR: Revenue Accounting and Reporting
  SLG1: Application Log
  FBL1N: Vendor Line Item Display (for checking related vendor data)
  FBL3N: G/L Account Line Item Display (for checking related G/L data)
  
  
  
  SAP Notes: Search for SAP Notes related to the error message FARR_RAI673 in the SAP Support Portal for any known issues or patches.
  
  
  Training and Documentation: Ensure that users involved in revenue accounting are adequately trained and have access to documentation that outlines the processes and requirements for managing revenue contracts.
  
  
  By following these steps, you should be able to identify and resolve the issues causing the FARR_RAI673 error in SAP.