7.6    Quality Inspections

The quality inspection component helps users determine whether a product consistently meets defined quality requirements. In a quality inspection, a material or product is inspected using master data predefined in the inspection planning component.

7.6.1    Inspection Lot Creation

A quality inspection is processed on the basis of inspection lots. To inspect a specified quantity of a material, an inspection lot is created in the SAP S/4HANA system. The inspection lots are created automatically by the system or manually by the user based on the master data setup. During the inspection lot creation process, transactional data such as purchase order data and master data relevant for quality is automatically copied to the inspection lot. The SAP S/4HANA system uses the inspection lot to record, process, and manage information for a quality inspection. This information includes the following:

7.6.2    Create Inspection Lot Manually

Manual lots are created to carry out unplanned inspections for the various materials and equipment. When you create an inspection lot manually, you can’t reference an original document (e.g., a GR document, an order, or a delivery note).

When you create an inspection lot manually for a material and lot origin combination, an inspection type for the specified origin should be active in the material master for that material. Inspection lots can’t be created manually for the following lot origins:

To manually create an inspection lot, navigate to LogisticsQuality ManagementQuality InspectionInspection Lot ProcessingInspection LotCreate (QA01) (see Figure 7.21).

Inspection Lot

Figure 7.21    Inspection Lot

Save your data. You can print inspection instructions by clicking Inspection Instruction.

7.6.3    Resetting the Inspection Lot

This function is used to reset the inspection lot for an inspection lot (e.g., because you want to use a different inspection plan to inspect the goods). Navigate to LogisticsQuality ManagementQuality InspectionInspection LotProcessingCancel Sample Calculation (QAC3), or Transaction QAC3.

You can only reset the inspection lot if the following are true:

7.6.4    Results Recording/Defect Recording

Using this transaction, you can do the following:

To record inspection results, the following conditions must be met:

Results recording for inspection lots can be accessed in the following two ways:

Figure 7.22 displays an example of the results recordings. Defects can be reported by clicking the Defects button.

Results Recording

Figure 7.22    Results Recording

Inspection Lot Completion

After the inspection results recording is completed for an inspection lot, then you must give a decision about the usage of the inspected material and close the inspection lot. Using the usage decision component, you can do the following:

Note

You can only make the usage decision for an inspection lot when all required inspection characteristics (mandatory) have been closed. After the usage decision has been given for an inspection lot, you can no longer change the inspection results. However, you can still process long-term inspection characteristics.

In the usage decision component, you can display the following inspection data:

Stock Postings

If an inspection lot is stock-relevant, you can post the stock for the inspection lot manually while you’re in the process of making the usage decision.

Note

On the basis of your stock postings, the system makes the corresponding postings in the SAP ERP Materials Management (SAP ERP MM) component.

You can post quantities of material from an inspection lot to the following stock types:

Note

Stock posting need not to be carried out at the time of usage decision. Stock posting can be done at the various stages of the inspection lot completion process:

The usage decision for an inspection lot can be changed after saving the usage decision, but a stock posting can’t be changed after the usage decision is saved.

To do this, navigate to LogisticsQuality ManagementQuality InspectionInspection lotUsage DecisionRecord (QA11), or Transaction QA11 (see Figure 7.23).

Usage Decision

Figure 7.23    Usage Decision