The following figure displays different scenarios for result recording and capturing additional data for each inspection point:
In all cases, you record inspection results for each (quantitative or qualitative) inspection characteristic (for example length, surface state, or functional test). Based on the recorded inspection results and the assigned sampling procedure, the system or the user valuates the inspection characteristic according to the valuation settings of the sampling procedure. Finally, you close the inspection characteristic.
Note
The status schema for inspection results (for example must be processed, processed, valuated, closed, and so on) is identical to the inspection scenario without inspection points.In contrast to quality inspection without inspection points, you can record results for the same inspection characteristic multiple times. In the example scenario, you execute the functional test (operation 30) at the beginning, in the middle, and at the end of the production operation. As indicated in the example, you valuate each inspection point according to the inspection results of the respective inspection point. Usually, if all inspection characteristics are accepted the respective inspection point valuation is also positive. In the case of rejected inspection characteristics you also valuate the inspection point as rejected.
Note
When comparing this scenario to the inspection scenario without inspection points, the inspection point valuation is similar to a usage decision. While the usage decision summarizes the entire quality inspection to one valuation (either accepted or rejected), the inspection point valuation also summarizes the quality inspection, but only takes into account the characteristic results which are assigned to this inspection point.
Technically, you also set up the inspection point valuation codes in catalog type 3.
Depending on the Inspection Point Completion Variant that you assigned during master data set up to the inspection operation, you must provide additional information when you complete the inspection point:
In the example operation 10, you configured the inspection operation so that the quality technician must provide, in addition to the inspection point valuation, an operation confirmation containing quantities (for example yield, scrap, rework, and so on) and time (for example machine time, labor, and so on).
You usually use this scenario if the production operator executes a worker self inspection.
In the example operation 20, you configured the inspection operation so that the quality technician does not need to provide an operation confirmation. Instead, you only require inspection point quantities and the inspection point valuation.
You usually use this scenario if the quality technician and production operator work independently.
Both scenarios have the advantage that there is an assignment between the manufactured quantity and the recorded inspection results so that, for example in case of rejected inspection results and/or defects, you only must rework a subset of the produced quantity.
If you do not require a link between the manufactured quantities and the inspection results, for example, when you periodically draw samples to monitor the state of the production process, you can configure the inspection operation to such that the quality technician can only maintain an inspection valuation (example operation 30). Alternatively, you can also enable automated inspection point valuation based on inspection results.
If you observe defects when executing results recording for inspection points you can also document the defect using the defects recording functionality of the SAP S/4HANA system. If you record a defect against an inspection characteristic or an inspection operation, the system also documents the inspection point in the defect item details. If you record a defect against the inspection lot, there is no reference to an inspection point in the defect item details.
After valuation of the inspection point, the inspection results are updated in the statistics and can be used for analytical purposes.
To record inspection results, the SAP S/4HANA system offers various apps and transactions, for example, Record Results for Inspection Points or Record Inspection Results - Hierarchical Worklist (QE51N).
Note
The Selection Screen of the App Record Inspection Results - Hierarchical Worklist (QE51N) provides the Checkbox Default Next Inspection Point:
When you activate this field, the system displays all automatically generated inspection points and the virtual inspection point Next Inspection. When you double-click this virtual inspection point, you can create a new inspection point on the operation level to capture additional inspection results.
Please note that you must activate this field if you do not use automatically generated inspection points as, only when this field is active, you can create new inspection points.
If you do not activate this field, the system displays only existing inspection points (for example automatically generated inspection points). You cannot create new inspection points in the hierarchy.
With the SAP Fiori app Record Results for Inspection Points, you can only record inspection results for inspection points whose inspection point identifier contains the date and time fields. Different identifiers are not supported and you must use the Record Inspection Results - Hierarchical Worklist (QE51N) instead.
Hint
To display information about inspection points, you can use the app Display Inspection Points.
For additional information how to process inspection points for an operation, please refer to the SAP Application Documentation.
For additional information how to record the inspection point confirmation, please refer to the SAP Application Documentation.