How To Fix FARR_CONTRACT_MAIN087 - Changing POB &1 from non-distinct to distinct is not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 087

• Message text: Changing POB &1 from non-distinct to distinct is not permitted

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_MAIN087 - Changing POB &1 from non-distinct to distinct is not permitted ?

  The SAP error message FARR_CONTRACT_MAIN087 indicates that there is an issue with changing the status of a Profitability Object (POB) from non-distinct to distinct in the context of contract management. This error typically arises in the SAP system when there is an attempt to modify the characteristics of a Profitability Object that is not allowed due to the existing configuration or data integrity rules.
  
  Cause:
  
  Data Integrity Rules: The system enforces rules to maintain data integrity. Changing a POB from non-distinct to distinct may violate these rules, especially if there are existing transactions or data linked to the POB.
  Configuration Settings: The configuration settings in the SAP system may not allow for such changes. This could be due to the way the POBs are defined in the system.
  Existing Dependencies: There may be existing dependencies or relationships with other objects or transactions that prevent the change.
  
  
  Solution:
  
  Review Configuration: Check the configuration settings for the Profitability