How To Fix /PLMI/ER_CI_TRANS010 - Selected engineering record &1 is locked by &2

/PLMI/ER_CI_TRANS010 - Overview

• Message type: E = Error

• Message class: /PLMI/ER_CI_TRANS -

• Message number: 010

• Message text: Selected engineering record &1 is locked by &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/ER_CI_TRANS010 - Selected engineering record &1 is locked by &2 ?

  The SAP error message /PLMI/ER_CI_TRANS010 Selected engineering record &1 is locked by &2 indicates that the engineering record you are trying to access or modify is currently locked by another user or process. This is a common issue in systems where multiple users may be working on the same data simultaneously.
  
  Cause:
  
  User Lock: Another user is currently editing the engineering record, which prevents you from making changes.
  System Lock: The record may be locked due to a background process or transaction that is currently running.
  Session Timeout: Sometimes, a session may not release the lock properly if it times out or if the user exits unexpectedly.
  
  
  Solution:
  
  Wait and Retry: If the lock is due to another user, you may need to wait until they finish their work and release the lock. You can periodically check if the record is still locked.
  Identify the Locking User: You can use transaction codes like SM12 (for lock entries)