How To Fix 61352 - BOM explosion number & is blocked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 352

• Message text: BOM explosion number & is 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 61352 - BOM explosion number & is blocked by another user ?

  The SAP error message 61352, which states "BOM explosion number & is blocked by another user," typically occurs when a user attempts to access or modify a Bill of Materials (BOM) that is currently being edited or processed by another user. This is a locking mechanism in SAP to prevent data inconsistencies and ensure that only one user can make changes to a BOM at a time.
  Cause:
  
  Concurrent Access: Another user is currently editing the BOM, which locks it for other users.
  Session Timeout: A previous session may not have released the lock due to a timeout or an unexpected termination.
  System Issues: Sometimes, system errors or bugs can lead to locks not being released properly.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish their work and then try again.
  Identify the Lock: Use transaction code SM12 to check for locks in the system. You can see which user is holding the lock on the BOM.
  
  Enter the relevant details (like the BOM number) and execute the transaction.
  If you find the lock is held by a user who is no longer active, you may need to contact your SAP administrator to release the lock.
  
  
  Release the Lock: If you have the necessary permissions, you can manually release the lock from SM12. However, this should be done with caution to avoid data inconsistencies.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check if there are any jobs running that might be using the BOM.
  Contact Support: If the issue persists and you cannot identify the cause, it may be necessary to contact your SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12: To view and manage locks.
  SE11: To check the structure of the BOM table.
  CS03: To display the BOM.
  
  
  User Roles: Ensure that users have the appropriate roles and permissions to access and modify BOMs.
  Documentation: Refer to SAP documentation for more details on BOM management and locking mechanisms.
  
  By following these steps, you should be able to resolve the error message 61352 and continue working with the BOM in SAP.