How To Fix /SCWM/DELIVERY358 - Lock owner holds further &1 &2 locks for &3 &4


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /SCWM/DELIVERY -

  • Message number: 358

  • Message text: Lock owner holds further &1 &2 locks for &3 &4

  • Show details Hide details


  • 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/DELIVERY358 - Lock owner holds further &1 &2 locks for &3 &4 ?

    The SAP error message /SCWM/DELIVERY358 typically indicates that a lock conflict has occurred in the SAP Extended Warehouse Management (EWM) system. This error message suggests that a lock owner is holding additional locks that are preventing the current operation from proceeding. Here’s a breakdown of the cause, potential solutions, and related information:

    Cause:

    1. Locking Mechanism: SAP uses a locking mechanism to ensure data consistency during transactions. When a user or process is working on a particular object (like a delivery), it locks that object to prevent other processes from making changes simultaneously.
    2. Multiple Locks: The error message indicates that the lock owner is holding additional locks (indicated by &1 &2) that are preventing the current transaction from acquiring the necessary lock (indicated by &3 &4).
    3. Long-running Transactions: If a transaction takes too long to complete, it can hold locks longer than expected, leading to conflicts with other transactions trying to access the same data.

    Solution:

    1. Identify the Lock Owner: Use transaction code SM12 to view the locks currently held in the system. You can filter by user or object to identify the lock owner.
    2. Release Locks: If the lock owner is identified and it is safe to do so, you can manually release the locks using transaction SM12. Be cautious when doing this, as it may lead to data inconsistencies if the lock owner is still processing.
    3. Check for Long-running Processes: Investigate any long-running processes that may be holding locks. You can use transaction SM66 to monitor active processes and identify any that are taking an unusually long time.
    4. Optimize Processes: If certain processes frequently lead to lock conflicts, consider optimizing them to reduce the time they hold locks. This may involve reviewing the logic of the processes or breaking them into smaller transactions.
    5. Increase Lock Timeout: In some cases, you may want to consider increasing the lock timeout settings, but this should be done with caution and typically as a last resort.

    Related Information:

    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on lock management in EWM.
    • Documentation: Review SAP documentation on locking mechanisms and best practices for managing locks in EWM.
    • Performance Monitoring: Regularly monitor system performance and lock situations to proactively address potential issues before they lead to conflicts.

    If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant