How To Fix FARR_RAI858 - Selected items could not be locked

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 858

• Message text: Selected items could not be locked

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_RAI858 - Selected items could not be locked ?

  The SAP error message FARR_RAI858 ("Selected items could not be locked") typically occurs in the context of the Asset Accounting (FI-AA) module when the system is unable to lock certain items for processing. This can happen for various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Concurrent Access: Another user or process may be accessing the same asset or transaction, preventing the system from locking it for your operation.
  System Configuration: There may be configuration settings that affect how locks are managed in the system.
  Database Issues: There could be underlying database issues that prevent the locking mechanism from functioning correctly.
  Transaction Errors: If there are errors in the transaction data or if the transaction is incomplete, it may lead to locking issues.
  User Authorizations: The user may not have the necessary authorizations to lock the items.
  
  Solutions:
  
  Check for Concurrent Users: Verify if another user is currently processing the same asset or transaction. If so, wait for them to complete their task.
  Retry the Operation: Sometimes, simply retrying the operation after a short period can resolve the issue if it was caused by temporary locks.
  Review System Logs: Check the system logs (transaction SM21) for any related error messages that might provide more context on the locking issue.
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the operation. You can use transaction SU53 to check for authorization issues.
  Consult with Basis Team: If the issue persists, it may be necessary to involve the SAP Basis team to investigate potential database or system configuration issues.
  Transaction Code: If you are using a specific transaction code, ensure that it is being used correctly and that all required fields are filled out properly.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  Documentation: Review the SAP documentation for Asset Accounting to ensure that you are following the correct procedures for the transactions you are attempting.
  Community Forums: Consider searching or posting in SAP community forums for additional insights from other users who may have encountered the same issue.
  
  If the problem continues after trying these solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.