How To Fix FARR_CONTRACT_MAIN788 - Non-distinct POB &1 cannot be a time-based POB with SDT3.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 788

• Message text: Non-distinct POB &1 cannot be a time-based POB with SDT3.

What causes this issue?

A non-distinct performance obligation cannot be a time-based POB with a
start date type of 3 ( Always the Event Date).

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_CONTRACT_MAIN788 - Non-distinct POB &1 cannot be a time-based POB with SDT3. ?

  The SAP error message FARR_CONTRACT_MAIN788 indicates that there is an issue with a non-distinct Point of Business (POB) that cannot be classified as a time-based POB when it is associated with a specific SDT3 (Service Delivery Type 3). This typically occurs in the context of contract management or service agreements within SAP.
  Cause:
  
  Non-Distinct POB: The error suggests that the POB in question is not distinct, meaning it does not have unique characteristics that differentiate it from other POBs. In SAP, POBs are used to define specific business processes or service delivery items.
  Time-Based POB: The system expects that a time-based POB should have distinct characteristics to ensure proper processing and reporting. If the POB is not distinct, it cannot be treated as time-based.
  Configuration Issues: There may be configuration issues in the contract or service delivery settings that lead to this error.
  
  Solution:
  
  Check POB Configuration: Review the configuration of the POB in question. Ensure that it is set up correctly and has distinct characteristics that allow it to be classified as a time-based POB.
  Modify POB Attributes: If the POB is indeed non-distinct, consider modifying its attributes to make it distinct. This may involve changing the parameters or settings associated with the POB.
  Review Contract Settings: Check the contract settings and ensure that they align with the requirements for time-based POBs. Make sure that the contract is set up to handle distinct POBs appropriately.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on configuring POBs and contracts. This can provide insights into best practices and common pitfalls.
  Seek SAP Support: If the issue persists, consider reaching out to SAP support or consulting with an SAP expert who can provide tailored assistance based on your specific system configuration and business processes.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on POB configuration.
  Transaction Codes: Familiarize yourself with transaction codes related to contract management and POB configuration, such as FARR (for contract management) and SPRO (for configuration).
  Training and Documentation: Ensure that users involved in contract management are trained on the proper setup and management of POBs to prevent similar issues in the future.
  
  By addressing the configuration and ensuring that POBs are distinct and properly set up, you should be able to resolve the error message FARR_CONTRACT_MAIN788.