How To Fix 28481 - No restriction because maximum number of hits exceeded

SAP Error Message - Details

• Message type: E = Error

• Message class: 28 - Configuration

• Message number: 481

• Message text: No restriction because maximum number of hits exceeded

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 28481 - No restriction because maximum number of hits exceeded ?

  The SAP error message 28481 ("No restriction because maximum number of hits exceeded") typically occurs in the context of SAP queries or reports when the system has reached a predefined limit on the number of records (or "hits") that can be processed or displayed. This is a safeguard to prevent performance issues that could arise from processing too many records at once.
  Cause:
  
  Exceeding Hit Limit: The error is triggered when the number of records returned by a query exceeds the maximum limit set in the system configuration.
  Large Data Set: The query or report is attempting to retrieve a large volume of data, which can happen if the selection criteria are too broad or if there are no filters applied.
  System Configuration: The maximum number of hits is often defined in the system settings, and it may be set to a low value to optimize performance.
  
  Solution:
  
  Refine Selection Criteria: Modify the selection criteria of your query or report to narrow down the results. This can include adding filters or conditions to limit the number of records returned.
  Increase Hit Limit: If appropriate, you can increase the maximum number of hits allowed in the system settings. This typically requires administrative access:
  
  Go to transaction RZ10 or RZ11 to adjust the parameter rdisp/max_wprun_time or similar parameters that control the maximum hits.
  Consult with your SAP Basis team to ensure that increasing this limit will not adversely affect system performance.
  
  
  Use Pagination: If the application supports it, implement pagination to retrieve data in smaller chunks rather than all at once.
  Check for Background Jobs: If the query is part of a background job, consider running it in smaller batches or segments.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance or patches related to this error message. SAP frequently updates its documentation and may have specific recommendations for your version.
  Performance Monitoring: Use transaction ST03N or ST04 to monitor system performance and identify if the high number of hits is a recurring issue.
  User Training: Ensure that users are trained on how to effectively use filters and selection criteria to avoid generating overly broad queries.
  
  If the problem persists after trying these solutions, it may be beneficial to consult with your SAP support team or reach out to SAP directly for further assistance.