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

SAP Error Message - Details

• 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: There may be authorization issues preventing the user from setting the condition type as a price.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Condition Type Configuration:
  
  Go to the configuration settings for condition types in the SAP system (Transaction code: SPRO).
  Ensure that the condition type is correctly defined and is allowed to be used as a price.
  
  
  
  Review Master Data:
  
  Verify that all necessary master data related to the POB and the condition type is complete and accurate.
  Check if the POB is correctly set up and linked to the relevant contract.
  
  
  
  Examine Pricing Procedure:
  
  Review the pricing procedure assigned to the contract and ensure that the condition type is included and configured correctly.
  Make adjustments if necessary to allow the condition type to be used as a price.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to set the condition type as a price.
  Consult with your SAP security team if there are any authorization issues.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  
  Testing:
  
  After making the necessary changes, test the process again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), ME22N (Change Purchase Order), and SPRO (Customizing).
  Documentation: Refer to SAP documentation for detailed information on condition types, pricing procedures, and contract management in RE-FX.
  Support: If the issue persists after following the above steps, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.