How To Fix FARR_ACCR_MAIN236 - Calculating contract liabilities and assets started at &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_ACCR_MAIN - Revenue Accounting - Accrual Management

• Message number: 236

• Message text: Calculating contract liabilities and assets started at &1

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_ACCR_MAIN236 - Calculating contract liabilities and assets started at &1 ?

  The SAP error message FARR_ACCR_MAIN236 typically relates to issues encountered during the calculation of contract liabilities and assets in the context of SAP's Revenue Accounting and Reporting (RAR) module. This error can occur for various reasons, and understanding the cause and finding a solution involves several steps.
  Cause:
  
  Data Inconsistencies: There may be inconsistencies in the data related to contracts, such as missing or incorrect entries in the contract master data or related accounting documents.
  Configuration Issues: Incorrect configuration settings in the RAR module can lead to errors during the calculation process.
  Missing Authorizations: Users may not have the necessary authorizations to execute the calculation.
  Technical Issues: There could be underlying technical issues, such as problems with the database or application server.
  Incomplete Process Steps: Certain prerequisite steps in the contract processing may not have been completed, leading to errors during the calculation phase.
  
  Solution:
  
  Check Data Consistency: Review the contract data and ensure that all necessary fields are filled out correctly. Look for any missing or incorrect entries.
  Review Configuration: Verify the configuration settings in the RAR module. Ensure that all necessary settings for contract accounting are correctly configured.
  User Authorizations: Check if the user executing the calculation has the required authorizations. If not, work with your SAP security team to grant the necessary permissions.
  Analyze Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide insights into what went wrong during the calculation.
  Run Consistency Checks: Use transaction codes like FARR_CHECK to run consistency checks on the contract data.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that can resolve known issues.
  Technical Support: If the issue persists, consider reaching out to SAP support for assistance. Provide them with detailed information about the error, including any logs or screenshots.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FARR for Revenue Accounting and Reporting, and SLG1 for application logs.
  Documentation: Review SAP documentation related to RAR for best practices and troubleshooting steps.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.