How To Fix FARR_CONTR_LIFECYCLE086 - Manual POB &1 cannot have a main price condition type.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTR_LIFECYCLE - Message from Contract Lifecyle (RAR 2.0 Object Model)

• Message number: 086

• Message text: Manual POB &1 cannot have a main price condition type.

What causes this issue?

A manual performance obligation cannot have a main price condition type.
This error occurs if the system detects, that a main price condition
type was added to a manual performance obligation.

System Response

The system stops processing the affected contract.

How to fix this error?

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

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_CONTR_LIFECYCLE086 - Manual POB &1 cannot have a main price condition type. ?

  The SAP error message FARR_CONTR_LIFECYCLE086 indicates that there is an issue with the pricing conditions in a manual Purchase Order (POB) in the context of the SAP system, particularly in the area of contract lifecycle management or related modules.
  Cause:
  The error typically arises when you attempt to create or modify a manual Purchase Order (POB) that includes a main price condition type that is not allowed. This can happen due to several reasons:
  
  Incorrect Condition Type: The condition type you are trying to use is not defined as a main price condition type in the system.
  Configuration Issues: The configuration settings in the pricing procedure may not allow for the specified condition type to be used as a main price condition.
  Data Entry Errors: There may be a mistake in the data entry, such as selecting an incorrect condition type or not following the required sequence of conditions.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Condition Types:
  
  Review the condition types defined in your pricing procedure. Ensure that the condition type you are trying to use is set up correctly and is allowed as a main price condition.
  
  
  
  Review Pricing Procedure:
  
  Go to the configuration settings for the pricing procedure in SAP (Transaction code: SPRO).
  Navigate to the relevant section for pricing and check the settings for the pricing procedure being used. Ensure that the main price condition types are correctly defined.
  
  
  
  Adjust Manual POB:
  
  If you are manually entering the POB, double-check the entries to ensure that you are using the correct condition types and that they are in the correct sequence.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on the condition types and their allowed usage in manual POBs.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support or your internal SAP team for further assistance. They may provide insights based on your specific configuration and setup.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to manage POBs.
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may address the issue.
  Training and Documentation: Ensure that users involved in creating or modifying POBs are trained on the correct procedures and understand the implications of the condition types used.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.