How To Fix FARR_INB_MAIN062 - Only Cost conditions are allowed with Cost Order RAI.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_INB_MAIN - Messages for Inbound Processing

• Message number: 062

• Message text: Only Cost conditions are allowed with Cost Order RAI.

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_INB_MAIN062 - Only Cost conditions are allowed with Cost Order RAI. ?

  The SAP error message FARR_INB_MAIN062 indicates that there is an issue with the configuration of cost conditions in relation to a cost order in the SAP system. This error typically arises in the context of the SAP Controlling (CO) module, particularly when dealing with cost orders and their associated conditions.
  Cause:
  The error message "Only Cost conditions are allowed with Cost Order RAI" suggests that the system is expecting only cost-related conditions to be processed with a specific type of cost order (RAI - which stands for "Resource Assignment Internal"). If there are other types of conditions (like revenue conditions) being processed alongside cost conditions, the system will throw this error.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Condition Types: Review the condition types that are being used in the transaction. Ensure that only cost-related conditions are included when processing the cost order.
  
  
  Review Configuration: 
  
  Go to the configuration settings for the cost order in the SAP system. 
  Ensure that the settings are correctly defined to allow only cost conditions for the specific order type you are working with.
  
  
  
  Adjust the Document: If you are trying to post a document that includes non-cost conditions, you may need to adjust the document to remove those conditions or change the order type to one that allows for those conditions.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for more detailed information on the specific cost order type and the conditions that are permissible.
  
  
  Testing: After making the necessary adjustments, perform a test transaction to ensure that the error no longer occurs.
  
  
  Seek Help from SAP Support: If the issue persists, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  
  Related Information:
  
  Cost Orders: In SAP, cost orders are used to track costs associated with specific projects or activities. They are part of the Controlling module and are essential for internal cost tracking and reporting.
  Condition Types: In SAP, condition types are used to define how costs and revenues are calculated and processed. They can be configured to handle various scenarios, including discounts, surcharges, and other pricing elements.
  RAI (Resource Assignment Internal): This is a specific type of cost order that is used for internal resource assignments. It is important to understand the implications of using this order type in your transactions.
  
  By following these steps and understanding the context of the error, you should be able to resolve the issue effectively.