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

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/LK -

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

  The SAP error message /SCWM/LK035 Inventory number currently blocked by another user typically occurs in the SAP Extended Warehouse Management (EWM) module when a user attempts to access or modify an inventory number that is currently locked by another user. This locking mechanism is in place to prevent data inconsistencies and ensure that inventory transactions are processed correctly.
  Cause:
  
  Concurrent Access: Another user is currently working on the same inventory number, which causes the system to lock it for that user.
  Long-running Transactions: If a user has a long-running transaction or is taking time to complete an operation, the inventory number may remain locked for an extended period.
  System Errors: Occasionally, system errors or crashes can leave inventory numbers in a locked state even after the user has exited the transaction.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to complete their transaction. After a short period, try accessing the inventory number again.
  Identify the Lock: If waiting is not feasible, you can identify which user has locked the inventory number. This can be done using transaction codes like SM12 (for lock entries) or SM21 (for system logs) to see who is currently using the inventory number.
  Contact the User: If you can identify the user, you may want to contact them to see if they can complete their transaction or release the lock.
  Release the Lock: If necessary and if you have the appropriate permissions, you can manually release the lock using transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on the inventory number.
  Check for System Issues: If this error occurs frequently, it may indicate a larger issue with system performance or user training. Consider reviewing system logs or consulting with your SAP Basis team.
  
  Related Information:
  
  User Training: Ensure that users are trained on how to properly complete transactions to minimize the time inventory numbers are locked.
  System Performance: Regularly monitor system performance to identify any bottlenecks that may be causing long transaction times.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its software, and there may be fixes or recommendations available.
  
  By following these steps, you should be able to resolve the /SCWM/LK035 error and minimize its occurrence in the future.