How To Fix FARR_CONTRACT_MAIN811 - Unit-distinct cannot be marked for compound and non-distinct perf. ob. &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 811

• Message text: Unit-distinct cannot be marked for compound and non-distinct perf. ob. &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_CONTRACT_MAIN811 - Unit-distinct cannot be marked for compound and non-distinct perf. ob. &1 ?

  The SAP error message FARR_CONTRACT_MAIN811 typically occurs in the context of contract management within the SAP system, particularly when dealing with performance obligations in the context of revenue recognition. This error indicates that there is a conflict in the way performance obligations are defined for a contract, specifically regarding the distinction between unit-distinct and non-distinct performance obligations.
  Cause:
  The error arises when you attempt to mark a performance obligation as both unit-distinct and non-distinct within the same contract. In SAP, performance obligations can be classified as:
  
  Unit-distinct: These are obligations that can be fulfilled separately and are distinct from other obligations.
  Non-distinct: These obligations are not separately identifiable and are typically bundled with other obligations.
  
  When the system detects that a performance obligation is being marked in a way that contradicts these definitions, it triggers the error message.
  Solution:
  To resolve this error, you should take the following steps:
  
  
  Review Performance Obligations: Check the performance obligations defined in the contract. Ensure that you are not trying to classify the same obligation as both unit-distinct and non-distinct.
  
  
  Adjust Classifications: If you find that there are conflicting classifications, adjust them accordingly. Decide whether the performance obligation should be treated as unit-distinct or non-distinct based on the nature of the goods or services being provided.
  
  
  Consult Documentation: Refer to SAP documentation or guidelines on performance obligations to ensure that you are following the correct procedures for classification.
  
  
  Test Changes: After making adjustments, test the changes in a development or test environment to ensure that the error no longer occurs.
  
  
  Seek Help from SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support or consulting with an SAP expert who can provide more tailored assistance based on your specific configuration and business processes.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context.
  Configuration Settings: Review the configuration settings related to revenue recognition and performance obligations in your SAP system.
  Training and Documentation: Ensure that users involved in contract management are trained on the distinctions between unit-distinct and non-distinct performance obligations to prevent future occurrences of this error.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to prevent it from recurring.