How To Fix LK035 - Inventory number currently blocked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: LK - WM -> SUB connection messages

• Message number: 035

• Message text: Inventory number currently blocked by another user

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 LK035 - Inventory number currently blocked by another user ?

  The SAP error message LK035, which states "Inventory number currently blocked by another user," typically occurs when a user attempts to access or modify an inventory number that is currently being used or locked by another user in the system. This can happen during various transactions, such as when trying to change or display inventory data.
  Cause:
  
  Concurrent Access: Another user is currently editing or processing the same inventory number.
  Transaction Lock: The inventory number is locked due to an ongoing transaction, such as a goods movement or inventory adjustment.
  Session Timeout: A previous session may not have released the lock properly, causing the inventory number to remain blocked.
  System Configuration: Certain configurations or settings in the SAP system may lead to locking issues.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for a few moments and then try to access the inventory number again. The lock may be released once the other user completes their transaction.
  Identify the Locking User: If you have the necessary permissions, you can use transaction code SM12 to check for locked entries. This will show you which user is currently holding the lock on the inventory number.
  Contact the User: If you identify the user who is blocking the inventory number, you can reach out to them to see if they can complete their transaction or release the lock.
  Release the Lock: If the locking session is no longer active (e.g., the user has logged out), you may need to manually release the lock using transaction code SM12. However, this should be done with caution and typically requires appropriate authorizations.
  Check for Background Jobs: Sometimes, background jobs may also lock inventory numbers. You can check transaction SM37 to see if any background jobs are running that might be causing the lock.
  System Configuration Review: If this issue occurs frequently, it may be worth reviewing the system configuration or consulting with your SAP Basis team to ensure that locking mechanisms are functioning correctly.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locked entries.
  SM37: To check background jobs.
  SE11: To view table definitions, if needed for deeper analysis.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to locking mechanisms in your specific version of SAP.
  User Training: Ensure that users are trained on proper transaction handling to minimize locking issues.
  
  If the problem persists after trying these solutions, it may be necessary to involve your SAP support team or consult SAP documentation for further troubleshooting steps.