How To Fix FARR_CONTRACT_MAIN670 - POB &1 cannot be marked as completed; has suspended revenue posting.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 670

• Message text: POB &1 cannot be marked as completed; has suspended revenue posting.

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_CONTRACT_MAIN670 - POB &1 cannot be marked as completed; has suspended revenue posting. ?

  The SAP error message FARR_CONTRACT_MAIN670 indicates that a Profitability Analysis (CO-PA) contract cannot be marked as completed because it has suspended revenue postings. This typically occurs in the context of contract accounting or revenue recognition processes within SAP.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Suspended Revenue Posting: There are pending or suspended revenue postings associated with the contract. This can happen if there are issues with the revenue recognition process, such as incomplete data or errors in the configuration.
  Open Items: There may be open items or transactions related to the contract that need to be resolved before the contract can be marked as completed.
  Configuration Issues: There might be configuration settings in the system that prevent the completion of the contract due to specific business rules or conditions.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check for Suspended Revenue Postings:
  
  Navigate to the contract in question and check for any suspended revenue postings. You can do this by reviewing the contract's revenue recognition status and any related documents.
  Use transaction codes like FARR (Contract Accounting) or FBL1N (Vendor Line Item Display) to investigate any related postings.
  
  
  
  Review Open Items:
  
  Check for any open items or transactions that are linked to the contract. Ensure that all necessary postings have been completed and that there are no outstanding issues.
  You can use transaction codes like FBL3N (G/L Account Line Item Display) to review open items.
  
  
  
  Correct Configuration:
  
  If the issue is related to configuration, review the settings in the contract accounting and revenue recognition areas. Ensure that all necessary configurations are in place and that they align with your business processes.
  Consult with your SAP configuration team or refer to SAP documentation for guidance on the relevant settings.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that can resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after following the above steps, consider reaching out to SAP Support for further assistance. Provide them with the error message details and any relevant transaction logs.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FARR, FBL1N, FBL3N, and others that may help in diagnosing the issue.
  Documentation: Review SAP documentation related to contract accounting and revenue recognition for best practices and troubleshooting steps.
  User Forums: Consider checking SAP community forums or user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.