How To Fix /SCWM/DELIVERY357 - Lock on &1 &2 since &3 &4

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/DELIVERY -

• Message number: 357

• Message text: Lock on &1 &2 since &3 &4

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 /SCWM/DELIVERY357 - Lock on &1 &2 since &3 &4 ?

  The SAP error message /SCWM/DELIVERY357 Lock on &1 &2 since &3 &4 typically indicates that there is a lock on a specific delivery document in the SAP Extended Warehouse Management (EWM) system. This lock prevents further processing of the delivery until the lock is released. The placeholders &1, &2, &3, and &4 represent specific details about the lock, such as the document number, the type of document, and the timestamp of when the lock was placed.
  Cause:
  
  Concurrent Processing: The most common cause of this error is that another user or process is currently working on the same delivery document, which results in a lock being placed on it.
  Long-running Transactions: If a transaction takes too long to complete, it may hold a lock on the document longer than expected.
  System Errors: Occasionally, system errors or crashes can leave locks in place that are not released properly.
  
  Solution:
  
  Identify the Lock: Use transaction code SM12 to check for locks on the delivery document. You can filter by user or document number to find the specific lock.
  Release the Lock: If you identify that the lock is held by a user or process that is no longer active, you can manually delete the lock entry in SM12. However, be cautious when doing this, as it may disrupt ongoing processes.
  Wait for Release: If the lock is legitimate and held by another user actively working on the document, you may need to wait until they complete their transaction.
  Check for Long-running Processes: Investigate if there are any long-running processes that may be causing the lock. You can use transaction SM66 to monitor active processes in the system.
  System Administration: If locks are frequently occurring, it may be worth reviewing system performance and user training to minimize concurrent access to the same documents.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage locks.
  SM66: Monitor active processes.
  SM21: Check system logs for errors that may indicate issues with locks.
  
  
  Documentation: Review SAP documentation for EWM and locking mechanisms to understand how locks are managed in the system.
  User Training: Ensure that users are trained on how to properly handle deliveries and avoid situations that lead to locking conflicts.
  
  If the issue persists or if you are unsure about releasing locks, it may be advisable to consult with your SAP Basis team or a technical consultant for further assistance.