Ensuring Product Quality

Objectives

After completing this lesson, you will be able to:
  • Execute a quality check with the Quality Inspection Engine (QIE).
  • Summarize inspection lots.

Quality Inspection in SAP Extended Warehouse Management (EWM)

You can use quality inspections to determine whether the stock you receive in your warehouse satisfies the quality requirements that you have put in place. A quality inspection allows you to record and document a decision, for example, OK, not OK. It also allows you to use a defect catalog to appraise the quality of an object, such as a delivery, handling unit, or product. Quality inspections in SAP EWM can be used during the inbound process and as an internal warehouse process.

Diagram showing items on a trolley being checked on a conveyor belt. Incorrect items are discarded, while correct ones are placed on shelves, illustrating a sorting process.

You can fully handle quality inspections in SAP EWM. The decision for a quality inspection is taken by the warehouse staff and entered in the system using SAP EWM. However, you can also forward quality inspections to a (central) external system, such as SAP ERP. In this case, the decision for a quality inspection is made by a central quality management team, but the stock in SAP EWM is linked to the inspection documents and updated based on the decision in the external system.

Flowchart illustrating warehouse process: goods receipt (IB01 unloading) leads to quality inspection (QIS), then to put-away (IB03). Types, bins, and work centers are specified at each step.

The following figure shows an example of a process where the quality inspection step is included.

Other then counting, a quality inspection can happen also at other places, when it is paper-based. The RF or work center transactions require the products to be at the work center. But you can enter the inspection results in the desktop transaction at any other time.

Note

In an SAP S/4HANA based EWM, you actually find two transactions for quality inspection at a work center:
  • Quality Inspection and Count (/SCWM/QINSP): this transaction is only for decentral EWM. In case of a quality inspection integrated in ERP QM, this transaction is only used for the handling unit processing, but not for the quality inspection.
  • Quality Workload Overview (SCWM/QINSP_S4): this transaction is only for embedded EWM. In this transaction much less functions are available for handling unit processing.

Dynamic Modification

You can determine the inspection frequency for a process in the Quality Inspection Engine (QIE) in different ways. For example, you can use the data from past inspection valuations to calculate the current inspection scope. To react flexibly to this data, you can modify the inspection scope dynamically by using sampling procedures and dynamic modification rules.

Flowchart of QIE process: goods move to inspection, analyzed with magnifying glass, and approved for shelving. Two people examine boxes; analysis represented by info-chart.

With respect to sample sizes and inspection probability, dynamic modification allows you to control the inspection scope for a series of inspection documents so that you can achieve a predefined quality goal with a high degree of certainty. In the QIE, you can perform dynamic modification at inspection document level.

Dynamic Modification Criteria and Functions

The user maintains dynamic modification criteria and dynamic modification rules in an inspection rule.

The dynamic modification criteria define the properties that are the basis for combining inspections for dynamic modification. The criteria are the key fields that the system uses to update the quality level.

The dynamic modification rule contains the definition of the inspection stages, the dynamic modification time, and the conditions for the inspection stage changes. An inspection stage specifies inspection parameters, such as the inspection severity, as well as the probability that an inspection is to be performed.

Quality Level

The user creates a quality level according to the dynamic modification criteria of the inspection rule.

The information in the quality level determines which inspection stage is used for the sample determination of the next inspection document.

The system calculates the inspection scope, dependent on the current inspection stage based on the quality level.

A user performs a quality inspection.

The system saves the inspection decision that has been made in the quality level.

The system determines the inspection stage for the next inspection document, based on the specified dynamic modification criteria and the dynamic modification rule and updates the quality level accordingly.

Quality Inspections with a Sample in SAP EWM

If the inspection rule arguments specify that there is to be no dynamic modification and that the inspection procedure is to be a 100% inspection, the system uses the lot size as the sample size. However, it is often not necessary to inspect the complete inspection lot, but to inspect only a calculated sample. Then, the rest of the lot can be putaway before the decision is made.

Flowchart of pallet processing: a truck delivers 100 pallets, forklift moves 90 to storage, 10 processed by two workers on a conveyor belt. Arrow indicates correct process towards storage.

For this, you can use a sample-drawing procedure. The sample-drawing procedure and, in some cases, the sample-drawing unit, define the quantity that must be inspected based on the specified lot size and on the number of containers. They also define how this quantity is distributed among individual samples. To do this, the system evaluates the sample-drawing instructions. The sample-drawing instruction can use a sampling scheme to determine the total sample quantity.

Inspection Lots Summary

Sometimes you might receive several inbound deliveries for the same purchase order or manufacturing order, but it is not practical to do the same quality inspection every time. In the same inspection document, you can summarize several stocks that have similar properties for inspection. You have the option to summarize stocks having the same combination of Product/Batch or Product/Batch/Reference Document (Purchase Order or Production/Process Order). A Business Add-In (BAdI) also allows a summarization according to a customized combination of properties. This summarization is possible when the quality inspection is standalone in the QIE, as well as integrated with SAP ERP QM.

Flowchart showing document exchange between ERP and EWM: Purchase order in ERP triggers two inbound deliveries, linked to EWM, resulting in goods receipt and inspection document creation.

The inspection document summary overrules the settings on Inspection Object Type (IOT) level regarding the automatic decision of the inspection document in the background, but this can be influenced by a BAdI.

An existing document is extended if an appropriate inspection document exists (released, not archived, to be archived, canceled, or decided) and the inspection has not begun in ERP. If there is no existing inspection document that can be extended (first document for the batch, wrong status), or the control for inspection summary has been changed on inspection level, a new inspection document is created. This occurs even if the inspection document summary is switched on.

There is one exception. If an inspection document is found that has a status of Decided, and the inspection summary control is set to One Inspection Document for Prod/Batch and Reference Document (Purchase Order / Manufacturing Order):

  • The system creates a new inspection document if the valuation of the status was Rejected.

  • The system suppresses the creation of a new inspection document if the decision has been valuated with Accepted. Therefore, the delivery item is posted directly to unrestricted stock without inspection process.