How To Fix FARR_CONTRACT_MAIN590 - Revenue can't be fully suspended for &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 590

• Message text: Revenue can't be fully suspended for &1 &2

What causes this issue?

You want to suspend revenue for selected contracts. This action can be
done for open reconciliation keys and periods only. One of periods in
your system for selected accounting principle &V2& and company code &V1&
has closing status In-Closing. Revenue recognized in this period can't
be suspended.

System Response

The report can't be executed.

How to fix this error?

You must switch the closing status of the period with status In-Closing
back to Open and run the report.
When you do not mind suspending revenue incompletely, you can set the
report parameter 'Suspend even when In-Closing' to true. The message
turns into warning and you can execute the report, however the revenue
in period with closing status In-Closing will not be suspended.

Procedure for System Administrators

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_CONTRACT_MAIN590 - Revenue can't be fully suspended for &1 &2 ?

  The SAP error message FARR_CONTRACT_MAIN590 indicates that revenue cannot be fully suspended for a specific contract. This error typically arises in the context of contract accounting or revenue recognition processes within SAP, particularly in the SAP Revenue Accounting and Reporting (RAR) module.
  Cause:
  The error can occur due to several reasons, including:
  
  Incomplete Data: The contract may not have all the necessary data or configurations set up correctly, which prevents the system from processing the suspension of revenue.
  Contract Status: The status of the contract may not allow for revenue suspension. For example, if the contract is already in a closed or completed status, the system may not permit further changes.
  Revenue Recognition Rules: There may be specific rules or conditions defined in the system that restrict the suspension of revenue for certain types of contracts or under certain circumstances.
  Dependencies on Other Transactions: There may be dependencies on other transactions or processes that need to be completed before revenue can be suspended.
  
  Solution:
  To resolve the error, consider the following steps:
  
  Check Contract Data: Review the contract details to ensure that all required fields and configurations are correctly filled out. Look for any missing or incorrect information.
  Review Contract Status: Verify the status of the contract. If it is in a status that does not allow for revenue suspension, you may need to change the status or take appropriate actions to enable suspension.
  Consult Revenue Recognition Rules: Check the revenue recognition rules that apply to the contract. Ensure that the conditions for revenue suspension are met according to the defined rules.
  Analyze Dependencies: Investigate if there are any other transactions or processes that need to be completed before you can suspend revenue. This may involve checking related contracts or accounting entries.
  SAP Notes and Documentation: Look for any relevant SAP Notes or documentation that may provide additional insights or solutions specific to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP that pertain to contract management and revenue recognition, such as FARR (Revenue Accounting and Reporting).
  SAP Support: If the issue persists, consider reaching out to SAP support or consulting with your internal SAP team for further assistance.
  User Forums and Communities: Engage with SAP user forums or communities where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.