Do you have any question about this error?
Message type: E = Error
Message class: QT - QM: Inspection during production (with inspection points)
Message number: 107
Message text: Results recording not supported for shop floor routing-based inspections
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You can record inspection results for shop floor routing-based
inspection lots in the <ZH>Perform Operation Activity</> app (F2898).
Error message extract from SAP system. Copyright SAP SE.
QT107
- Results recording not supported for shop floor routing-based inspections ?The SAP error message QT107, which states "Results recording not supported for shop floor routing-based inspections," typically occurs in the context of quality management (QM) processes when attempting to record inspection results for a routing-based inspection lot. This error indicates that the system does not allow results recording for the specific type of inspection you are trying to perform.
Cause:
- Inspection Type Configuration: The inspection type may not be configured to allow results recording for routing-based inspections. This can happen if the inspection type is set up incorrectly in the Quality Management module.
- Routing Settings: The routing associated with the production order may not be set up to support quality inspections. This could be due to missing or incorrect settings in the routing or the inspection plan.
- Inspection Lot Status: The inspection lot may be in a status that does not allow results recording. For example, if the lot is already completed or if it is in a status that restricts further processing.
- User Authorizations: The user may not have the necessary authorizations to perform results recording for the specific inspection lot or inspection type.
Solution:
Check Inspection Type Configuration:
- Go to the configuration settings for the inspection type in the Quality Management module (Transaction code: SPRO).
- Ensure that the inspection type is set up to allow results recording for routing-based inspections.
Review Routing and Inspection Plan:
- Verify that the routing associated with the production order is correctly set up to include quality inspections.
- Check the inspection plan to ensure it is linked to the correct routing and that all necessary characteristics are defined.
Inspect Lot Status:
- Check the status of the inspection lot in the system. If the lot is in a status that does not allow results recording, you may need to change the status or create a new inspection lot.
User Authorizations:
- Ensure that the user has the necessary authorizations to perform results recording. This can be checked with the security team or by reviewing the user roles and permissions in the system.
Consult Documentation:
- Review SAP documentation or help resources for any additional configuration or settings that may be required for your specific scenario.
Related Information:
Transaction Codes:
QA32
(Display Inspection Lots) to check the status of inspection lots.QAL1
(Results Recording) to attempt results recording and see if the error persists.SAP Notes:
Quality Management Configuration:
By following these steps, you should be able to identify the root cause of the QT107 error and implement the necessary changes to resolve it.
Get instant SAP help. Start your 7-day free trial now.
QT106
Serialized material (&1) does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
QT105
Inspection point type for serialized materials (&1) not supported
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
QT110
The function module name & you entered is invalid
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
QT111
The exceptions for function module &1 differ from the example module
What causes this issue? You specified a function module whose interface does not correspond with the interface of sample function module &v2&...
Click on this link to search all SAP messages.