How To Fix /SCMTMS/OM074 - &1 cannot be canceled; &2 is locked in another session

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/OM -

• Message number: 074

• Message text: &1 cannot be canceled; &2 is locked in another session

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 /SCMTMS/OM074 - &1 cannot be canceled; &2 is locked in another session ?

  The SAP error message /SCMTMS/OM074 &1 cannot be canceled; &2 is locked in another session typically occurs in the context of SAP Transportation Management (TM). This error indicates that an attempt to cancel a transportation order or related document is being blocked because the document is currently locked by another user or session. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Document Locking: In SAP, when a document (like a transportation order) is being processed, it gets locked to prevent concurrent modifications. If another user or session is currently working on the same document, you will receive this error when trying to cancel it.
  Long-running Transactions: If a transaction is taking a long time to complete, it may hold the lock longer than expected, leading to this error for other users.
  System Issues: Occasionally, system issues or bugs can lead to improper locking behavior.
  
  Solutions:
  
  
  Check for Active Sessions:
  
  Use transaction code SM12 to check for locks. You can filter by the user or the object type to see if the document is locked by another session.
  If you find that the document is locked by a session that is no longer active or is stuck, you may need to unlock it.
  
  
  
  Wait and Retry:
  
  If the lock is legitimate (i.e., another user is actively working on the document), you may need to wait until they finish their transaction and then try to cancel the document again.
  
  
  
  Communicate with Users:
  
  If you identify that another user is working on the document, communicate with them to understand their timeline and whether they can release the lock.
  
  
  
  Transaction Monitoring:
  
  Monitor the transaction that is holding the lock. If it is taking too long, you may need to investigate why it is delayed.
  
  
  
  System Administration:
  
  If you are a system administrator, you can forcibly remove locks in SM12, but this should be done with caution as it can lead to data inconsistencies.
  
  
  
  Check for Background Jobs:
  
  Sometimes, background jobs may hold locks. Check transaction SM37 to see if any background jobs are running that might be affecting the document.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review the SAP TM documentation for insights on document locking and transaction management.
  User Training: Ensure that users are trained on how to properly manage documents in SAP TM to minimize locking issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact your SAP support team for further assistance.