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

LM352 - Overview

• 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