How To Fix /SCMTMS/BATCH_80074 - &1 &2 has been locked by others; no creation or update of freight unit

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/BATCH_80 -

• Message number: 074

• Message text: &1 &2 has been locked by others; no creation or update of freight unit

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_80074 - &1 &2 has been locked by others; no creation or update of freight unit ?

  The SAP error message /SCMTMS/BATCH_80074 indicates that a freight unit is locked by another user or process, preventing the current user from creating or updating that freight unit. This is a common issue in systems where multiple users or processes may be trying to access the same data simultaneously.
  Cause:
  
  Concurrent Access: Another user or background job is currently accessing or modifying the freight unit.
  Long-Running Transactions: A transaction that takes a long time to complete may hold a lock on the freight unit.
  System Configuration: Certain configurations in the SAP system may lead to locking behavior that is more aggressive than necessary.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Lock:
  
  Use transaction code SM12 to check for locks in the system. You can filter by the user ID or the object type to find the specific lock.
  If you find a lock that is not being released, you may need to contact the user or process holding the lock.
  
  
  Release the Lock: If you have the necessary authorizations, you can manually delete the lock entry in SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other process is still running.
  Check Background Jobs: Use transaction code SM37 to check for any background jobs that might be holding the lock. If a job is stuck, you may need to terminate it.
  Review System Configuration: If this issue occurs frequently, it may be worth reviewing the system configuration and locking mechanisms to ensure they are set up optimally.
  
  Related Information:
  
  Lock Management: Understanding how SAP handles locks can help in troubleshooting. Locks are typically managed at the database level, and SAP uses various types of locks (e.g., exclusive, shared) to ensure data integrity.
  User Training: Ensure that users are trained on how to properly manage freight units and understand the implications of long-running transactions.
  Performance Monitoring: Regularly monitor system performance and transaction times to identify potential bottlenecks that could lead to locking issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.