Mapping Quality Inspection Processes

Objective

After completing this lesson, you will be able to examine quality management in SAP EWM

Quality Management

Note

See the following video to learn more about the necessity of performing a quality inspection when receiving goods:

QIE Architecture

In the QIE architecture, a QIE consumer refers to an application that uses QIE functionality. The QIE consumer is generally an independent system that is linked to the QIE through a qRFC and/or XI interface. Alternatively, the QIE can be part of the consumer system. This is for example the case with SAP EWM.

Flowchart illustrating the integration of a consumer system, such as SAP EWM, with the Quality Inspection Engine (QIE). At the top, a green database represents the consumer system. Below it, an orange downward arrow labeled Request points to a magnifying glass inspecting charts, symbolizing the QIE. To the right of the magnifying glass, an icon shows a clipboard with a checklist containing three options, with the top option ticked.

The QIE is independent of the SAP ERP system. It can be connected to an external ERP system for a complete quality management (QM) process.

The development platform for the QIE is the Web Application Server (WAS). The QIE is an engine that is technically designed as an add-on. SAP EWM is the first consumer system and it uses QIE as a required add-on.

Note

SAP S/4HANA embedded EWM does not use the QIE for quality inspections, but uses QM directly. Therefore, not all inspection object types described in this section are available in SAP S/4HANA embedded EWM.

Processes with Quality Inspection in SAP EWM

Quality checks can be performed at different stages, for example:

When the transportation unit is unloaded: check the pallet and move it to a work place for unpacking.
When the pallet is routed to an inspection area: check the quality of the product and then putaway to the final storage bin or return it to the vendor (depending on the quality).
In set intervals for products in the warehouse.

The inspections that are done are controlled by the inspection object type. The inspection object type defines in which software component, in which process, and for which object the inspection documents can be created in the QIE. The inspection object types for SAP EWM exist by default. In customizing, they are activated for each warehouse number. When they are activated, inspections are possible.

Inspection Object Types

Preliminary Inspection Inbound Delivery (1).
Preliminary Inspection Handling Unit (2).
Counting Inbound Delivery (2).
Q-Inspection Returns Delivery.
Q-Inspection Product/Batch Inbound Delivery.
Q-Inspection Product/Batch Warehouse-Internal.
Defect Processing.

(1) this inspection object type is only available in SCM based SAP EWM up to SAP EWM 9.5.

(2) these inspection object types are only available in a decentralized EWM, but not in embedded EWM.

Another requirement for inspections is an inspection rule. An inspection rule describes an inspection in further detail, for example:

What shall be inspected, for example, a material, a delivery type, or deliveries from a specific vendor?
How shall the inspection be performed, for example, on a sample or with 100% inspection?

In embedded EWM, it is not necessary anymore to use inspection rules.

Use Counting as Part of Quality Inspection

This is part 1 of 2 of this exercise:

ExerciseStart Exercise

This is part 2 of 2 of this exercise:

ExerciseStart Exercise

Quality Inspection with SAP ERP QM

If you require a more complex quality management process, the QIE can be connected to an external QM system, such as SAP ERP QM. Here, you can cover detailed analytical inspections with characteristics.

Within the activation of an inspection document in SAP EWM, the QIE triggers the creation of an inspection lot in ERP QM. The inspection process is executed in the external system, which is the ERP QM system. ERP QM sends back the usage decision to the QIE after the inspection is done.

Note

Because SAP S/4HANA embedded EWM does not use the Quality Inspection Engine, the communication is different. Messages are sent directly between EWM and QM in this instance.

Flowchart illustrating the interaction between a Consumer System (such as SAP EWM), a Quality Inspection Engine (QIE), and SAP ERP. The Consumer System is represented by a green cylinder labeled at the top, from which an arrow labeled Request is directed towards a document symbol connecting to the QIE. The QIE symbol is enclosed in a dashed box, showing three connected nodes, a magnifying glass, and a bar chart with varying height columns. To the right, there is a blue cylinder labeled QM for SAP ERP. Two arrows labeled Request and Usage decision connect the QIE with SAP ERP, both pointing to envelope symbols indicating communication. Below the blue cylinder is a clipboard icon with a checklist.

Summary

Quality inspection is used to examine products to confirm that the correct quality and quantity was received. The process works very different depending if a decentralized or an embedded SAP EWM is used.
Quality inspection can directly be done in SAP EWM through the Quality Inspection Engine based on inspection rules.
The SAP ERP system can also be used to perform a more detailed quality inspection using the QM functions of this system.

Explore an Inbound Process with Quality Inspection

This is part 1 of 3 of this exercise:

ExerciseStart Exercise

This is part 2 of 3 of this exercise:

ExerciseStart Exercise

This is part 3 of 3 of this exercise:

ExerciseStart Exercise

Next lesson