How To Fix /SCWM/DELIVERY359 - Lock statistics

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/DELIVERY -

• Message number: 359

• Message text: Lock statistics

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/DELIVERY359 - Lock statistics ?

  The SAP error message /SCWM/DELIVERY359 typically relates to issues with lock statistics in the context of the Extended Warehouse Management (EWM) module. This error can occur when there are problems with the system's ability to manage locks on database entries, which can lead to performance issues or data inconsistencies.
  Cause:
  
  Lock Contention: This error often arises due to high levels of lock contention, where multiple processes are trying to access the same data simultaneously, leading to delays or failures in processing.
  Long-running Transactions: If transactions take too long to complete, they can hold locks for extended periods, causing other processes to wait and potentially leading to this error.
  Configuration Issues: Incorrect configuration of the EWM system or database settings can also contribute to lock issues.
  Database Performance: Poor database performance or resource constraints can exacerbate locking issues.
  
  Solution:
  
  Analyze Lock Statistics: Use transaction codes like SM12 (to view and manage locks) and SM21 (to check system logs) to analyze the current locks and identify any long-running transactions.
  Optimize Transactions: Review and optimize the code or processes that are causing long-running transactions. Ensure that they are efficient and do not hold locks longer than necessary.
  Increase System Resources: If the system is under heavy load, consider increasing the resources available to the database or application server.
  Adjust Lock Timeout Settings: Review and adjust the lock timeout settings in the system configuration to reduce the likelihood of contention.
  Database Tuning: Perform database tuning to improve performance and reduce lock contention. This may involve indexing, query optimization, or other database management practices.
  Monitor System Performance: Regularly monitor system performance and lock statistics to proactively identify and address potential issues before they lead to errors.
  
  Related Information:
  
  SAP Notes: Check for relevant SAP Notes that may provide specific guidance or patches related to this error. SAP Notes can be found in the SAP Support Portal.
  Documentation: Review the official SAP documentation for EWM and lock management to understand best practices and configuration settings.
  Community Forums: Engage with the SAP community forums or user groups to see if others have encountered similar issues and what solutions they have implemented.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.