How To Fix LM352 - An active end-of-day processing run has exceeded the maximum runtime

SAP Error Message - Details

• Message type: E = Error

• Message class: LM - Treasury: Limit Management

• Message number: 352

• Message text: An active end-of-day processing run has exceeded the maximum runtime

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 LM352 - An active end-of-day processing run has exceeded the maximum runtime ?

  The SAP error message LM352 indicates that an active end-of-day (EOD) processing run has exceeded the maximum runtime allowed. This can occur in various SAP modules, particularly in logistics and warehouse management, where end-of-day processing is crucial for closing out daily operations.
  Cause:
  
  Long Processing Time: The end-of-day processing may be taking longer than expected due to a large volume of transactions, complex calculations, or inefficient processing logic.
  System Performance Issues: The underlying system may be experiencing performance issues, such as high CPU or memory usage, which can slow down processing.
  Configuration Settings: The maximum runtime for end-of-day processing may be set too low in the system configuration.
  Locks or Deadlocks: Other processes may be locking resources needed for the end-of-day processing, causing delays.
  Database Issues: Slow database performance or issues with database locks can also contribute to extended processing times.
  
  Solution:
  
  Increase Maximum Runtime: Review and, if necessary, increase the maximum runtime setting for end-of-day processing in the system configuration. This can often be done in transaction codes like SPRO or through specific configuration settings related to the module in use.
  Optimize Processes: Analyze the end-of-day processing logic to identify any inefficiencies. This may involve optimizing queries, reducing the volume of data processed, or breaking down the processing into smaller batches.
  Monitor System Performance: Use transaction codes like ST03N or SM66 to monitor system performance and identify any bottlenecks. Address any performance issues, such as high CPU or memory usage.
  Check for Locks: Use transaction code SM12 to check for locks that may be affecting the end-of-day processing. Resolve any unnecessary locks.
  Database Maintenance: Ensure that the database is well-maintained, including regular performance tuning, indexing, and cleanup of old data.
  Run During Off-Peak Hours: If possible, schedule end-of-day processing during off-peak hours to reduce the load on the system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM21 (System Log), and ST22 (Dump Analysis) to troubleshoot and monitor the system.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to end-of-day processing.
  Documentation: Review SAP documentation for best practices on configuring and optimizing end-of-day processing in your specific module.
  
  By addressing the underlying causes and optimizing the configuration and performance of the system, you can resolve the LM352 error and ensure smoother end-of-day processing.