Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: UMG - Message Class for the Unicode Migration Tool.
Message number: 372
Message text: Selection restricted to &1 hits.
In the current selection the number of read accesses is restricted.
Therefore not all data are displayed on the screen which match your
selection.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Increase the maximum number of lines to be displayed in your selection.
Error message extract from SAP system. Copyright SAP SE.
UMG372
- Selection restricted to &1 hits. ?The SAP error message UMG372 "Selection restricted to &1 hits" typically occurs in the context of the SAP User Management Engine (UME) or when dealing with user-related data in SAP systems. This message indicates that the selection criteria you have used in a query or report has resulted in a limited number of hits (in this case, &1 represents the number of hits found).
Cause:
- Limited Selection Criteria: The selection criteria you have specified may be too restrictive, leading to a limited number of results.
- Data Restrictions: There may be data restrictions in place that limit the visibility of certain records based on user roles or authorizations.
- System Configuration: The system may be configured to limit the number of records returned for performance reasons.
Solution:
- Review Selection Criteria: Check the selection criteria you are using. If they are too specific, consider broadening them to include more potential results.
- Check Authorizations: Ensure that your user account has the necessary authorizations to view all relevant data. If you are restricted by roles, you may need to request additional access from your system administrator.
- Adjust System Settings: If you have access to system configuration, you may want to check if there are any settings that limit the number of hits returned in queries and adjust them accordingly.
- Use Pagination: If the system supports it, consider implementing pagination to view results in smaller chunks rather than all at once.
Related Information:
If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
UMG371
Exception List was not uploaded correctly.
What causes this issue? You tried to initialize the worklist for the Consistency Check or to update the worklist for the Consistency Check or to sche...
UMG370
Reset/Restart not possible. Worker jobs are running.
What causes this issue? You tried to reset or to restart transaction SPUMG. This is currently not allowed because SPUMG worker jobs are still active ...
UMG373
The language "?" cannot be inserted into the SPUMG Language List.
What causes this issue? The SPUMG scan "Tables with Ambiguous Language Information" found records which use the character '?' as ...
UMG374
The reports must not run in non Unicode systems.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.