How To Fix /SCMTMS/FAG_MSG345 - Cannot run optimizer; execution of historical spend report not finished

/SCMTMS/FAG_MSG345 - Overview

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 345

• Message text: Cannot run optimizer; execution of historical spend report not finished

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 /SCMTMS/FAG_MSG345 - Cannot run optimizer; execution of historical spend report not finished ?

  The SAP error message /SCMTMS/FAG_MSG345 indicates that the optimizer cannot run because the execution of the historical spend report has not been completed. This error typically occurs in the context of SAP Transportation Management (TM) when there is a dependency on the completion of a report or process before the optimizer can be executed.
  
  Cause:
  
  Pending Report Execution: The historical spend report is still running or has not finished processing. The optimizer requires the data from this report to function correctly.
  Long Processing Time: The historical spend report may take a long time to execute due to large volumes of data or system performance issues.
  System Locking: There may be a locking issue where the report is being executed by another user or process, preventing the optimizer from starting.
  
  
  Solution:
  
  
  Check Report Status: 
  
  Go to the transaction code for monitoring background jobs (e.g., SM37) and check if the historical spend report is still running. If it