How To Fix FARR_RAI687 - Item &1: Error determining CO object number

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 687

• Message text: Item &1: Error determining CO object number

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_RAI687 - Item &1: Error determining CO object number ?

  The SAP error message FARR_RAI687 indicates that there is an issue with determining the Controlling (CO) object number for a specific item in the context of Asset Accounting (FI-AA) or related financial processes. This error typically arises when the system is unable to find or resolve the CO object associated with the asset or transaction.
  Causes:
  
  Missing CO Object: The CO object (such as a cost center, internal order, or project) may not be assigned or may be missing in the relevant configuration.
  Incorrect Configuration: There may be issues with the configuration settings in the controlling area or the asset master data.
  Data Inconsistencies: There could be inconsistencies in the data, such as missing entries in the master data tables.
  Authorization Issues: The user may not have the necessary authorizations to access the CO object.
  System Errors: There may be temporary system errors or inconsistencies in the database.
  
  Solutions:
  
  Check CO Object Assignment: Verify that the CO object is correctly assigned in the asset master data. Ensure that the relevant cost center, internal order, or project is properly configured.
  Review Configuration Settings: Check the configuration settings in the controlling area to ensure that they are set up correctly. This includes verifying the assignment of cost elements and cost centers.
  Data Consistency Check: Run consistency checks on the relevant master data to identify any missing or inconsistent entries. You can use transaction codes like OKB9 (for cost centers) or KOB1 (for internal orders) to review the data.
  Authorization Check: Ensure that the user has the necessary authorizations to access the CO object. You may need to consult with your SAP security team to verify this.
  Debugging: If the issue persists, consider debugging the program or transaction that is generating the error to identify the root cause. This may require the assistance of an ABAP developer.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS01 (Create Asset), AS02 (Change Asset), and AS03 (Display Asset) to manage asset data.
  SAP Documentation: Review SAP documentation related to Asset Accounting and Controlling for best practices and configuration guidelines.
  Support Community: Engage with the SAP Community or forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem continues after trying the above solutions, it may be necessary to escalate the issue to your SAP support team or consult with SAP directly for further assistance.