How To Fix FARR_APPLICATION143 - POB &1: Manually changed POB is not supported

FARR_APPLICATION143 - Overview

• Message type: E = Error

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

• Message number: 143

• Message text: POB &1: Manually changed POB 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_APPLICATION143 - POB &1: Manually changed POB is not supported ?

  The SAP error message FARR_APPLICATION143 with the description "POB &1: Manually changed POB 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.
  
  Cause:
  This error usually arises when there is an attempt to manually change a Property Object Business (POB) that is not allowed due to system constraints or configuration settings. The POB may have been set up in a way that restricts manual changes, possibly due to:
  
  System Configuration: The POB might be configured to prevent manual changes to ensure data integrity or compliance with business rules.
  Status of the POB: The POB may be in a status that does not allow changes (e.g., it could be locked or in a closed state).
  Custom Logic: There may be custom enhancements or logic in place that restricts manual changes to certain fields or records.
  
  
  Solution:
  To resolve this error, consider