How To Fix MZ090 - Exception & blocked by other users

SAP Error Message - Details

• Message type: E = Error

• Message class: MZ - Message for the EWS in LIS

• Message number: 090

• Message text: Exception & blocked by other users

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 MZ090 - Exception & blocked by other users ?

  The SAP error message MZ090, which states "Exception & blocked by other users," typically occurs in the context of inventory management or material document processing. This error indicates that the transaction you are trying to perform is being blocked because another user is currently accessing or modifying the same data.
  Causes:
  
  Concurrent Access: Another user is currently processing the same material document or inventory item, leading to a lock on the data.
  Long-running Transactions: If a transaction takes too long to complete, it can block other users from accessing the same data.
  System Configuration: Certain configurations in the SAP system may lead to locking issues, especially if the system is not optimized for concurrent access.
  
  Solutions:
  
  Wait and Retry: The simplest solution is to wait for the other user to complete their transaction and then try again.
  Identify the Lock: Use transaction codes like SM12 (to view and manage locks) to identify which user is holding the lock. You can then communicate with that user to understand when they will release the lock.
  Transaction Monitoring: If the lock is due to a long-running transaction, you may need to monitor the transaction and, if necessary, ask the user to complete or terminate it.
  System Configuration Review: If this issue occurs frequently, it may be worth reviewing the system configuration and performance. Consider optimizing the database or adjusting the locking mechanisms.
  User Training: Ensure that users are trained on how to properly complete transactions to minimize the time locks are held.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM12 (to check locks), SM21 (to view system logs), and ST22 (to check for dumps) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Performance Tuning: Consider performance tuning of the SAP system to reduce the likelihood of long-running transactions that can lead to locks.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or technical support for further investigation.