How To Fix /SCMTMS/UI_MESSAGES164 - Optimizer log does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/UI_MESSAGES -

• Message number: 164

• Message text: Optimizer log does not exist

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/UI_MESSAGES164 - Optimizer log does not exist ?

  The SAP error message /SCMTMS/UI_MESSAGES164 indicates that the optimizer log does not exist. This error typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find the log file that is generated during the optimization process.
  Cause:
  
  Missing Log File: The optimizer log file may not have been created due to an error during the optimization run.
  Incorrect Configuration: There may be issues with the configuration settings for the optimizer that prevent the log from being generated.
  Authorization Issues: The user may not have the necessary authorizations to access the optimizer log.
  System Errors: There could be underlying system errors or issues with the database that prevent the log from being created or accessed.
  
  Solution:
  
  Check Optimization Run: Verify if the optimization process was executed successfully. If it failed, investigate the reasons for the failure.
  Review Configuration: Ensure that the optimizer is correctly configured. Check the settings in the Transportation Management configuration to ensure that logging is enabled.
  User Authorizations: Confirm that the user has the necessary authorizations to view the optimizer logs. You may need to consult with your SAP security team to ensure proper access rights.
  Re-run Optimization: If the log is missing, try re-running the optimization process. Monitor the process to see if the log is generated this time.
  Check System Logs: Look into the system logs (transaction SLG1) for any errors or warnings that might provide more context about why the log is missing.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide patches or updates.
  Contact SAP Support: If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCMTMS/OPTIMIZE for running the optimizer and SLG1 for checking application logs.
  Documentation: Review the SAP Transportation Management documentation for detailed information on the optimizer and logging features.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the optimizer log not existing in SAP TM.