How To Fix LR352 - &1: Number of database record hits exceeds &2; number reduced to &3

SAP Error Message - Details

• Message type: E = Error

• Message class: LR - CATS: Cross-Application Time Sheet

• Message number: 352

• Message text: &1: Number of database record hits exceeds &2; number reduced to &3

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 LR352 - &1: Number of database record hits exceeds &2; number reduced to &3 ?

  The SAP error message LR352 indicates that the number of database record hits during a query or operation has exceeded a predefined limit. This can occur in various contexts, such as when retrieving data from a database table or executing a report that pulls a large volume of records.
  Cause:
  The error is triggered when the number of records that match the query criteria exceeds the maximum limit set in the system. This limit is often in place to prevent performance issues, such as excessive memory usage or long processing times, which can occur when handling large datasets.
  Solution:
  To resolve the LR352 error, consider the following approaches:
  
  
  Refine the Query: Modify the selection criteria of your query to reduce the number of records being retrieved. This can involve adding more specific filters or conditions to narrow down the results.
  
  
  Increase the Limit: If you have the necessary permissions and it is appropriate for your use case, you can increase the limit for the number of records that can be retrieved. This typically involves adjusting system settings or parameters in the SAP configuration.
  
  
  Pagination: If the application supports it, implement pagination to retrieve records in smaller batches rather than all at once. This can help manage memory usage and improve performance.
  
  
  Check for Performance Issues: Investigate whether there are any underlying performance issues with the database or the query itself. Optimizing the database indexes or the query structure can help improve performance and reduce the number of records processed.
  
  
  Consult Documentation: Review SAP documentation or notes related to the specific transaction or report you are using. There may be specific recommendations or best practices for handling large datasets.
  
  
  Contact SAP Support: If the issue persists or if you are unsure how to proceed, consider reaching out to SAP support for assistance. They can provide guidance based on your specific system configuration and usage.
  
  
  Related Information:
  
  Transaction Codes: Depending on the context of the error, you may be using specific transaction codes (e.g., SE16, SE11) to access database tables or reports.
  Performance Tuning: Familiarize yourself with performance tuning techniques in SAP, such as optimizing database queries, using appropriate indexes, and analyzing execution plans.
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide additional context and solutions.
  
  By following these steps, you should be able to address the LR352 error and improve the performance of your SAP queries or reports.