How To Fix FARR_CONTRACT_MAIN271 - Condition type &1 for acquisition cost on POB &2 cannot be set as price.

FARR_CONTRACT_MAIN271 - Overview

• Message type: E = Error

• Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management

• Message number: 271

• Message text: Condition type &1 for acquisition cost on POB &2 cannot be set as price.

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_MAIN271 - Condition type &1 for acquisition cost on POB &2 cannot be set as price. ?

  The SAP error message FARR_CONTRACT_MAIN271 indicates that there is an issue with the condition type for acquisition costs on a Purchase Order (POB) that cannot be set as a price. This typically occurs in the context of the SAP Flexible Real Estate Management (RE-FX) module, particularly when dealing with contracts and pricing conditions.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Incorrect Condition Type Configuration: The condition type specified (represented by &1 in the error message) may not be configured correctly in the system to be used as a price for the specified POB (represented by &2).
  
  
  Missing or Incomplete Master Data: The master data related to the condition type or the POB may be incomplete or missing, leading to the inability to set the condition type as a price.
  
  
  Incompatibility with Pricing Procedure: The condition type may not be compatible with the pricing procedure defined for the contract or the POB.
  
  
  Authorization Issues: