How To Fix /SCMTMS/BATCH_80073 - &1 &2 has been locked by others and cannot be confirmed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/BATCH_80 -

• Message number: 073

• Message text: &1 &2 has been locked by others and cannot be confirmed

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/BATCH_80073 - &1 &2 has been locked by others and cannot be confirmed ?

  The SAP error message /SCMTMS/BATCH_80073 indicates that a batch job or a transport request is locked by another user or process, preventing the current user from confirming or processing it. This typically occurs in the context of SAP Transportation Management (TM) or when dealing with batch jobs in the system.
  Cause:
  
  Lock by Another User: Another user or process is currently working on the same batch job or transport request, which causes a lock.
  Long-Running Processes: If a batch job is taking a long time to complete, it may remain locked for an extended period.
  System Errors: Sometimes, system errors or crashes can leave locks in place that need to be cleared.
  Configuration Issues: Incorrect configuration in the transport management system or batch job settings can lead to locking issues.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for the other user or process to complete their work may resolve the issue.
  Identify the Locking User/Process:
  
  Use transaction code SM12 to check for locks in the system. You can filter by the object name or user to find the specific lock.
  If you identify the locking user, you can communicate with them to understand when they will release the lock.
  
  
  Release the Lock: If you have the necessary authorizations and it is safe to do so, you can manually delete the lock entry in SM12. Be cautious with this approach, as it may disrupt the work of the other user.
  Check for Long-Running Jobs: Use transaction SM37 to check for any long-running jobs that may be causing the lock. If necessary, you can cancel these jobs if they are no longer needed.
  Review System Logs: Check the system logs (transaction SM21) for any errors or warnings that might indicate underlying issues causing the lock.
  Consult Basis Team: If the issue persists, it may be necessary to involve your SAP Basis team to investigate further, especially if it appears to be a systemic issue.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To monitor and manage background jobs.
  SM21: To view system logs.
  
  
  Documentation: Refer to SAP Help documentation for more details on transport management and batch processing.
  SAP Notes: Check for any relevant SAP Notes that may address known issues related to this error message.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the /SCMTMS/BATCH_80073 error message.