How To Fix MLT774 - Maximum duration of generic search was saved (current session)

SAP Error Message - Details

• Message type: E = Error

• Message class: MLT - Messages for Translation Tools

• Message number: 774

• Message text: Maximum duration of generic search was saved (current session)

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 MLT774 - Maximum duration of generic search was saved (current session) ?

  The SAP error message MLT774, which states "Maximum duration of generic search was saved (current session)," typically occurs when a search operation in SAP takes longer than the predefined maximum duration set for generic searches. This can happen in various SAP modules, particularly when dealing with large datasets or complex queries.
  Cause:
  
  Long Query Execution Time: The search operation is taking too long to complete, possibly due to large volumes of data or inefficient search criteria.
  System Performance: The performance of the SAP system may be affected by high load, insufficient resources, or other performance-related issues.
  Configuration Settings: The maximum duration for a generic search may be set too low in the system configuration.
  
  Solution:
  
  Optimize Search Criteria: Review and refine the search criteria to make it more specific, which can help reduce the execution time.
  Increase Maximum Duration: If appropriate, consider increasing the maximum duration for generic searches in the system settings. This can usually be done by an SAP Basis administrator.
  Check System Performance: Monitor the system performance to identify any bottlenecks. This may involve checking CPU usage, memory usage, and database performance.
  Database Optimization: Ensure that the database is optimized, including proper indexing and statistics updates, which can significantly improve query performance.
  Batch Processing: If applicable, consider breaking down the search into smaller batches to avoid long-running queries.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific recommendations or patches related to this error message.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in monitoring and optimizing performance, such as ST22 (Dump Analysis), SM37 (Job Monitoring), and ST03N (Workload Analysis).
  User Training: Ensure that users are trained on how to effectively use search functions to avoid overly broad queries that can lead to performance issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.