FKKBIX858 - Selected items could not be locked

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKBIX - Conv.Inv.: Billing (Invoice Preprocessing)

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

  The SAP error message FKKBIX858, which states "Selected items could not be locked," typically occurs in the context of financial transactions, particularly when dealing with document processing in the SAP system. This error indicates that the system was unable to lock certain items for processing, which is necessary to ensure data integrity and prevent concurrent modifications.
  Causes:
  
  Concurrent Access: Another user or process is currently accessing or modifying the same items, leading to a lock conflict.
  Long-running Transactions: A transaction that takes too long to complete may hold locks longer than expected, causing other transactions to fail when trying to access the same items.
  System Configuration: Certain configurations in the SAP system may lead to locking issues, especially if the locking mechanism is not set up correctly.
  Database Locks: Locks at the database level may also prevent the application from obtaining the necessary locks on the items.
  User Authorizations: The user may not have the necessary authorizations to lock the items, leading to this error.
  
  Solutions:
  
  Wait and Retry: If the error is due to concurrent access, waiting for a short period and then retrying the operation may resolve the issue.
  Check for Active Sessions: Use transaction codes like SM12 (to check for lock entries) to identify if another user or process is holding locks on the items in question. If necessary, you can ask the user to release the lock or terminate their session if appropriate.
  Optimize Long-running Transactions: Review and optimize any long-running transactions that may be holding locks for extended periods.
  Review Authorizations: Ensure that the user has the necessary authorizations to perform the action that is causing the error.
  System Configuration Review: Consult with your SAP Basis team to review the system configuration related to locking mechanisms and ensure they are set up correctly.
  Database Monitoring: If the issue persists, it may be necessary to monitor the database for locks and performance issues that could be affecting the locking mechanism.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to view lock entries), SM21 (to check system logs), and ST22 (to check dumps) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review SAP documentation related to locking mechanisms and transaction processing to better understand how locks are managed within the system.
  
  If the problem persists after trying the above solutions, it may be beneficial to engage with your SAP support team or consult SAP's support resources for further assistance.