Do you have any question about this error?
Message type: E = Error
Message class: QG - QM: Evaluation of inspection results
Message number: 748
Message text: Code group cannot be used to restrict the hit list
The range for the combined catalog type and code group field on the
selection screen for the analysis cannot be used as a selection
criteria for structuring the notification list.
You have entered the range <(>&<)>v1& - <(>&<)>v2& as the filter value
for the combined catalog type and code group field. When selecting the
notification list, you cannot restrict your selection using the range
for the code group <(>&<)>v3& - <(>&<)>v4<(>&<)>.
All notifications with items for catalog type <(>&<)>v1& - <(>&<)>v2
<(>&<)> are displayed. The list can therefore contain notifications
that do not match the selection criteria.
The list content of the notifications matches the content of the
standard analysis for the following selection criteria:
Range contains only one catalog type (for example, '9F-100' -
'9F-900').
The code group has a generic entry for the range (such as '1*' - 'Z*').
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
QG748
- Code group cannot be used to restrict the hit list ?The SAP error message QG748, which states "Code group cannot be used to restrict the hit list," typically occurs in the context of quality management or when working with code groups in SAP. This error indicates that the code group you are trying to use is not valid for the operation you are attempting to perform, often related to the selection criteria in a report or transaction.
Cause:
- Invalid Code Group: The code group you are trying to use may not be defined correctly or may not exist in the system.
- Inappropriate Context: The code group may not be applicable for the specific transaction or report you are working with.
- Authorization Issues: There may be restrictions on your user role that prevent you from accessing certain code groups.
- Configuration Issues: The configuration settings for the code groups may not be set up correctly in the system.
Solution:
- Check Code Group Definition: Verify that the code group you are trying to use is defined in the system. You can do this by navigating to the relevant configuration settings in SAP.
- Use Valid Code Group: Ensure that you are using a code group that is appropriate for the transaction or report. You may need to consult with your SAP administrator or refer to documentation to find a suitable code group.
- Review User Authorizations: Check if your user role has the necessary authorizations to access the code group. If not, you may need to request additional permissions.
- Consult Configuration Settings: If you have access, review the configuration settings related to code groups in the SAP system to ensure they are set up correctly.
- Contact SAP Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it seems to be a system-level issue.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
QG747
Material & could not be converted from unit & to unit &
What causes this issue? There is no quantity conversion from unit <(>&<)>v2& to the base unit of measure <(>&<)>v...
QG746
Inspection lot & does not exist in table &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
QG750
The reorganization was cancelled because the run time was exceeded
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
QG751
The list display could not be limited with drill-down criterion &
What causes this issue? The subsequent list is usually limited by the drill-down criteria of the current line. However, criterion &v1& is not...
Click on this link to search all SAP messages.