How To Fix /PLMI/BO_MBOM035 - Item &1 cannot be locked and changed in BOM &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/BO_MBOM -

• Message number: 035

• Message text: Item &1 cannot be locked and changed in BOM &2

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 /PLMI/BO_MBOM035 - Item &1 cannot be locked and changed in BOM &2 ?

  The SAP error message /PLMI/BO_MBOM035 indicates that an item in a Bill of Materials (BOM) cannot be locked and changed. This typically occurs when there are issues related to the locking mechanism in SAP, which prevents concurrent changes to the same BOM item by multiple users or processes.
  Causes:
  
  Concurrent Access: Another user or process is currently editing the BOM item, which prevents your session from locking it for changes.
  System Lock: The system may have a lock on the BOM item due to a previous transaction that did not complete properly.
  Authorization Issues: The user may not have the necessary authorizations to change the BOM item.
  Technical Issues: There could be a technical issue with the SAP system, such as a database lock or a problem with the application server.
  
  Solutions:
  
  
  Check for Concurrent Users: Verify if another user is currently editing the BOM item. You can use transaction code SM12 to check for locks on the item. If you find a lock that is no longer needed, you may need to contact the user or administrator to release it.
  
  
  Wait and Retry: If the item is locked by another user, you may need to wait until they finish their changes and release the lock. You can periodically retry your changes.
  
  
  Check Authorizations: Ensure that you have the necessary authorizations to edit the BOM item. You can check your user roles and authorizations with transaction code SU53 after receiving the error.
  
  
  Release Locks: If you suspect that a lock is lingering due to a failed transaction, you can use transaction code SM12 to manually release locks if you have the necessary permissions.
  
  
  System Check: If the issue persists, it may be necessary to check for any system errors or issues. You can consult with your SAP Basis team to investigate any underlying technical problems.
  
  
  Consult Documentation: Review SAP Notes and documentation related to BOM management and locking mechanisms for any specific guidance or patches that may address the issue.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: Display and manage locks.
  SU53: Display authorization check.
  SE11: Data dictionary to check the structure of BOM tables.
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  
  
  BOM Management: Familiarize yourself with the BOM management processes in SAP, including how locks are managed and the implications of concurrent access.
  
  
  If the problem continues after trying these solutions, it may be beneficial to escalate the issue to your SAP support team for further investigation.