How To Fix MQ345 - According to 'Find largest tables' no execution required

SAP Error Message - Details

• Message type: E = Error

• Message class: MQ - Messages for Euro Changeover Package

• Message number: 345

• Message text: According to 'Find largest tables' no execution required

What causes this issue?

In the IMG point 'Find Largest Tables' you have specified that you do
not want this program to be executed. Consequently the program was
simply started only to be immediately terminated again.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If you change your mind then access the IMG point again and change the
setting from OFF to ON. You will then be able either to start the
analysis phase from the beginning or reschedule the program using the
IMG point 'Start Preprocessing Programs Individually'

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MQ345 - According to 'Find largest tables' no execution required ?

  The SAP error message MQ345, which states "According to 'Find largest tables' no execution required," typically indicates that the system has determined that there are no large tables that need to be processed or analyzed at the moment. This message is often related to database management and performance optimization tasks within SAP systems.
  Cause:
  
  No Large Tables Detected: The system has scanned the database and found that there are no tables that exceed the predefined thresholds for size or growth that would require further action.
  Configuration Settings: The thresholds for what constitutes a "large" table may be set too high, leading to the system not identifying any tables that need attention.
  Database Maintenance: Regular maintenance and cleanup of the database may have already been performed, resulting in no large tables being present.
  
  Solution:
  
  Review Configuration: Check the configuration settings for the thresholds that define large tables. Adjust these settings if necessary to ensure that the system accurately identifies tables that may need attention.
  Database Analysis: If you believe there are large tables that should be flagged, perform a manual analysis of the database to identify any tables that may not have been detected by the automated process.
  Regular Maintenance: Ensure that regular database maintenance tasks are being performed to keep the database optimized and to prevent the growth of large tables.
  Consult Documentation: Refer to SAP documentation or support resources for specific guidance on managing large tables and interpreting error messages.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional context or solutions related to this error message.
  Performance Monitoring: Utilize SAP performance monitoring tools to keep an eye on database performance and table sizes.
  Database Administration: Engage with your database administrator (DBA) to ensure that the database is being managed effectively and that any potential issues are being addressed.
  
  If the issue persists or if you have specific concerns about your SAP environment, consider reaching out to SAP support for further assistance.