How To Fix 1H021 - Maximum number of selected data (&) was reached

SAP Error Message - Details

• Message type: E = Error

• Message class: 1H - BKK: Scheck-/Wechselverwaltung

• Message number: 021

• Message text: Maximum number of selected data (&) was reached

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 1H021 - Maximum number of selected data (&) was reached ?

  The SAP error message 1H021 ("Maximum number of selected data (&) was reached") typically occurs when a user attempts to select or process more data than the system is configured to handle in a single operation. This can happen in various contexts, such as when running reports, executing queries, or processing large datasets.
  Cause:
  The error is generally caused by exceeding the predefined limits set in the SAP system for data selection. This limit is often in place to prevent performance issues, such as excessive memory usage or long processing times. The specific limit can vary based on the transaction, report, or program being executed.
  Solution:
  To resolve this error, you can consider the following approaches:
  
  
  Reduce the Selection Criteria:
  
  Narrow down your selection criteria to reduce the number of records being processed. This can be done by applying additional filters or parameters to your query or report.
  
  
  
  Use Pagination:
  
  If the application supports it, implement pagination to process data in smaller chunks rather than trying to retrieve all records at once.
  
  
  
  Check System Settings:
  
  Consult with your SAP Basis or system administrator to check if the maximum selection limit can be adjusted in the system settings. However, be cautious with this approach, as increasing limits may lead to performance degradation.
  
  
  
  Batch Processing:
  
  If applicable, consider processing the data in batches. This means breaking down the data into smaller sets and processing them sequentially.
  
  
  
  Review Custom Code:
  
  If the error occurs in a custom report or program, review the code to ensure it is optimized for performance and does not attempt to load excessive amounts of data at once.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific transaction or report you are using to see if there are known limitations or recommended practices.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific guidance or patches related to the error message. SAP frequently updates its knowledge base with solutions for common issues.
  Performance Monitoring: Use transaction codes like ST03N or ST22 to monitor system performance and analyze dumps that may provide insights into the error.
  User Training: Ensure that users are trained on how to effectively use selection criteria to avoid overwhelming the system with large data requests.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.