How To Fix FARR_APPLICATION156 - POB &1: POB with Duration is not supported

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_APPLICATION - General Revenue Accounting Applications and Code

• Message number: 156

• Message text: POB &1: POB with Duration is not supported

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_APPLICATION156 - POB &1: POB with Duration is not supported ?

  The SAP error message FARR_APPLICATION156 with the description "POB &1: POB with Duration is not supported" typically occurs in the context of the SAP Flexible Real Estate Management (RE-FX) module, particularly when dealing with Property Object Business (POB) transactions that involve duration-based contracts or agreements.
  Cause:
  The error indicates that the system encountered a Property Object Business (POB) that is defined with a duration, but the current configuration or the specific transaction does not support duration-based POBs. This can happen due to several reasons, such as:
  
  Configuration Issues: The system may not be configured to handle duration-based POBs properly.
  Data Entry Errors: The POB might have been incorrectly set up or entered with parameters that are not compatible with duration handling.
  Version Limitations: The version of SAP you are using may not support certain features related to duration in POBs.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration: Review the configuration settings for the RE-FX module to ensure that it supports duration-based POBs. This may involve checking the settings in the customizing transaction (SPRO) related to Real Estate Management.
  
  
  Review POB Setup: Verify the setup of the specific POB that is causing the error. Ensure that it is configured correctly and that all required fields are filled out appropriately.
  
  
  Consult Documentation: Refer to the SAP documentation or release notes for your version to see if there are any known limitations or specific configurations required for duration-based POBs.
  
  
  Update or Patch: If you are using an older version of SAP, consider applying any relevant updates or patches that may address this issue.
  
  
  Contact SAP Support: If the issue persists after checking the configuration and setup, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration or version.
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to this error message. SAP Notes often contain fixes, workarounds, or additional information about specific error messages.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed. Other users may have encountered the same error and can provide insights or solutions.
  Training and Documentation: Ensure that users involved in setting up and managing POBs are adequately trained and have access to the necessary documentation to avoid configuration errors.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.