How To Fix FARR_CONTRACT_MAIN787 - Compound POB &1 cannot be a time-based POB.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 787

• Message text: Compound POB &1 cannot be a time-based POB.

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_MAIN787 - Compound POB &1 cannot be a time-based POB. ?

  The SAP error message FARR_CONTRACT_MAIN787 indicates that there is an issue with a compound Purchase Order (POB) in the context of contract management within the SAP system. Specifically, the error states that the compound POB cannot be a time-based POB. This typically arises in the context of contract management, particularly when dealing with service contracts or agreements that have specific time-based conditions.
  Cause:
  
  Incorrect Configuration: The compound POB may have been incorrectly configured in the system, leading to a mismatch between the expected type of POB and the actual configuration.
  Data Entry Error: There may be an error in the data entry where the system is expecting a different type of POB (e.g., quantity-based instead of time-based).
  Incompatibility: The system may not support the combination of a compound POB with time-based conditions due to business rules or system limitations.
  
  Solution:
  
  Review Configuration: Check the configuration settings for the POB in the SAP system. Ensure that the compound POB is set up correctly and that it aligns with the intended use case.
  Adjust POB Type: If the POB is incorrectly set as time-based, consider changing it to a quantity-based POB if that aligns with your business requirements.
  Data Validation: Validate the data entered for the POB to ensure that all fields are correctly filled out and that there are no inconsistencies.
  Consult Documentation: Refer to SAP documentation or help resources for guidance on setting up POBs correctly, especially in the context of contracts.
  Seek Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide insights based on your specific configuration and business processes.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context on handling POBs.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME31K (Create Contract), ME32K (Change Contract), and ME33K (Display Contract) to manage contracts effectively.
  Training and Documentation: Ensure that users involved in contract management are trained on the correct procedures for setting up and managing POBs to minimize errors.
  
  By addressing the configuration and data entry aspects, you should be able to resolve the error and proceed with your contract management tasks in SAP.