How To Fix DMCLG470 - Preliminary calculation in sender is still running

SAP Error Message - Details

• Message type: E = Error

• Message class: DMCLG - DMC Tool Development

• Message number: 470

• Message text: Preliminary calculation in sender is still running

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 DMCLG470 - Preliminary calculation in sender is still running ?

  The SAP error message DMCLG470, which states "Preliminary calculation in sender is still running," typically occurs in the context of data transfer processes, particularly in SAP BW (Business Warehouse) or SAP HANA environments. This error indicates that a preliminary calculation or data processing task is still in progress, preventing the completion of the current operation.
  Cause:
  
  Ongoing Process: The most common cause is that a previous data load or calculation process is still running in the background. This can happen if the system is busy processing large volumes of data or if there are long-running queries.
  Locking Issues: There may be locks on the data objects involved, preventing new processes from starting until the current one is completed.
  System Performance: High system load or performance issues can lead to delays in processing, causing the preliminary calculation to take longer than expected.
  
  Solution:
  
  Check Running Processes: Use transaction codes like SM37 (Job Monitoring) or SM66 (Global Work Process Overview) to check for any running jobs or processes that might be causing the delay. If you find a stuck job, you may need to terminate it.
  Wait for Completion: If the preliminary calculation is expected to take time due to the volume of data, it may be best to wait for it to complete before attempting to rerun the process.
  Review System Performance: Check system performance metrics to ensure that there are no bottlenecks. You may need to optimize the system or schedule heavy data loads during off-peak hours.
  Check for Locks: Use transaction SM12 to check for any locks on the relevant database tables. If you find locks that are no longer needed, you can release them.
  Increase Timeout Settings: If this is a recurring issue, consider increasing the timeout settings for the data transfer or calculation processes.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  Performance Tuning: Consider performance tuning for your BW or HANA system, including optimizing data models, indexes, and queries to reduce processing time.
  
  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.