How To Fix /SCMTMS/BATCH_80068 - Some documents have been locked by others and cannot be confirmed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/BATCH_80 -

• Message number: 068

• Message text: Some documents have 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_80068 - Some documents have been locked by others and cannot be confirmed ?

  The SAP error message /SCMTMS/BATCH_80068 indicates that some documents are locked by other users or processes, preventing the current user from confirming or processing those documents. This is a common issue in systems where multiple users or processes may be trying to access the same data simultaneously.
  Cause:
  
  Document Locking: In SAP, when a user or process is working on a document (like a transport order, shipment, etc.), it gets locked to prevent other users from making changes that could lead to inconsistencies.
  Long-running Transactions: If a transaction takes too long to complete, it may hold locks longer than expected, causing other users to encounter this error.
  User Sessions: Sometimes, a user may have multiple sessions open, and one session may be locking the document while another tries to access it.
  Background Jobs: Background jobs or batch processes may also lock documents while they are being processed.
  
  Solution:
  
  Wait and Retry: Often, the simplest solution is to wait for a few moments and then try to confirm the documents again. The locks may be released once the other user or process completes its transaction.
  Identify Locking User: Use transaction code SM12 to check for locked entries. You can see which user or process is holding the lock on the document. If necessary, you can contact the user to ask them to release the lock.
  Release Locks: If you have the necessary authorizations, you can manually release the locks in SM12. However, be cautious with this approach, as it may lead to data inconsistencies if the other user is still working on the document.
  Check Background Jobs: If a background job is causing the lock, you may need to wait for it to complete or check with the administrator to see if it can be stopped or rescheduled.
  Review System Performance: If this issue occurs frequently, it may be worth reviewing system performance and transaction handling to identify any bottlenecks or long-running processes that could be optimized.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locked entries.
  SM21: To check system logs for any related errors or warnings.
  ST22: To check for dumps that might indicate underlying issues.
  
  
  User Communication: If you identify a user holding a lock, communicate with them to understand if they can release the document or if they are still actively working on it.
  Documentation: Refer to SAP Help documentation for more details on document locking and handling in your specific version of SAP.
  
  If the problem persists after trying these solutions, it may be necessary to involve your SAP Basis team or support for further investigation.