Creation of Inspection Rule
Use
You use transaction /SCWM/QRSETUP to define the inspection rules required by the system for creating inspection documents, under consideration of the dynamic modification criteria you have defined (optional). For more information, see Dynamic Modification Criteria at Inspection Document Creation.
Inspection rules contain the following sets of parameters:
-
Property values for determination, such as for which product or quality inspection group and supplier an inspection is to take place
-
General arguments
-
Inspection procedure (sample inspection and 100% inspection) is mandatory for rules created in SAP Extended Warehouse Management (SAP EWM)
Rules created from QIR (SAP ERP) do not have a procedure assigned – inbound inspection (inspection object type (IOT) 4).
-
Possible decisions (decision code groups for headers and items that define the follow-up actions)
-
Possible findings (defects, efforts)
-
-
Specific arguments
-
Sampling (if you use the inspection procedure for sample inspection)
You define the sampling size (as a percentage or a fixed value), movement relevance, and quality control relevance (for example, destructive).
-
External (if you integrate with the Quality Management module in SAP ERP)
You define the SAP ERP inspection type and task list attributes.
-
You can also use inspection rules to influence logistics management in the warehouse by executing the following:
-
Defining the location-independent stock type of the stock for which an inspection rule is determined (inspection rule property) or the location-independent stock type the system is to use for the stock while the quality inspection takes place (inspection rule argument)
-
Transporting the stock being checked to special work centers or special areas (by defining a process step in the inspection rule argument)
-
Influencing the goods receipt in SAP EWM by using the settings for goods receipt control (inbound inspection IOT 4)
Integration
Depending on the IOT, you can use the following master data in the inspection rule:
-
Product master records
-
Business partners
-
Quality inspection groups
You can also include sample procedures in inspection rules (see Sampling Procedure). You define a sample-drawing procedure comprising of a sample-drawing unit (see Sample-Drawing Unit) and sample-drawing instruction (see Sample-Drawing Instruction) in Customizing for the Quality Inspection Engine. This enables you, for example, to define a sample-drawing instruction of type Container in such a way that you inspect ten pieces out of every handling unit (HU) or pallet of a goods receipt.
Prerequisites
You have an active version of at least one IOT. For more information, see Customizing Settings for QM in EWM.
Features
To define the inspection rules, you have the following options:
-
You can define warehouse-specific and cross-warehouse inspection rules.
To create cross-warehouse inspection rules, you must select the New Rules Cross-Warehouse checkbox in the control parameters for your user ().
-
In the exceptional case that you have generated a new version of an IOT, you can copy inspection rules to new IOT versions.
Before you do this, specify the new version in the control parameters for your user.
-
You can create, change, and display inspection rules.
-
You can deactivate an inspection rule by choosing the No Check inspection procedure.
The maintained arguments will be deleted by saving the change.
-
For inbound inspections – IOT 4 you can deactivate an inspection rule by using the setting for inspection control.
All arguments of inspection rule will be kept; this information is also part of the data transfer from QIR in SAP ERP.
-
You can upload and link documents (for example, a Microsoft Word document or a PDF) to your inspection rule that, for example, give detailed instructions or pictures on how to perform an inspection.
Inspection Procedure
You can choose the 100% inspection or sample inspection as an inspection procedure.
If you want to maintain exceptions for, for example, certain products, you can choose the No Inspection inspection procedure.
Inspection Rule Arguments
|
Argument of Inspection Rule |
Definition |
|---|---|
|
Inspection rule group |
Short code with description for grouping inspection rules of the same type. |
|
Inspection duration and unit |
The system uses this entry to calculate the planned inspection completion date and time. You can use this field for selection using the warehouse management monitor (). |
|
Independent stock type |
Defines the stock type in which you want to post the stock while it is under inspection. |
|
Process step |
If process-oriented storage control is not active or if the delivery item is unpacked, you use the external process step (storage control) to define the inspection area in the warehouse. |
|
Control indicator for inspection document creation (Inbound Inspection IOT 4 and Counting IOT 2) |
You can create one inspection document for one of the following:
If you cumulate multiple delivery items in one inspection document, the standard logic for the automatic decision of the inspection document header is modified. The system no longer automatically determines the decision for inspection documents when a decision is made on element level. The only way to automatically decide inspection documents in this case is to implement BAdI: Custom Criteria Definition for Inspections. |
|
Argument of Sample |
Definition |
|---|---|
|
Sample type |
Define how the sample quantity is to be determined by the system (percentage, fix, sampling scheme, or BAdI). |
|
Quality control relevance |
Define how the sample is handled (for example, destructive sample or relevance for follow-up action after completing inspection). |
|
Warehouse process type |
Warehouse process type for posting a destructive sample. |
|
Movement-relevant |
Indicator where you define whether the sample quantity is to be separated from the lot and moved in the warehouse. |
Inspection Process (Inbound)
If you create rules for the quality inspection inbound delivery, it is possible to define the following types of inspection processes:
|
Inspection Process |
Definition |
|---|---|
|
0 |
Inspection After Goods Receipt |
|
1 |
Acceptance Sampling (for external procurement; before goods receipt) |
|
2 |
Presampling in Production (for production or process orders; before goods receipt) |
Goods Receipt Control (Inbound)
Specific settings for goods receipt control are available on the inspection role for Q-inspection Inbound Delivery (IOT 4) in the context of the goods receipt control process.
|
Goods Receipt Block for Q-Reasons |
<blank> No Block 1 No Block but Warning 2 Block 0 No Block – Overrule Inheritance Use option “0” if the goods receipt block is inherited from a higher level of rule hierarchy to deactivate the goods receipt block for a single inspection rule. |
|
Inspection Control |
<blank> Inspection Rule Active 1 Inspection Rule Not Active 0 Insp. Rule Active – Overrule Inheritance Use option “0” if the inspection rule is deactivated by the setting from a higher level of rule hierarchy to activate a single inspection rule. |
Activities
Define at least one inspection rule for each IOT that you want to use. To do so, on the SAP Easy Access screen, choose
Define inspection rules for the IOT for the various property values. This means, for example, that you define inspection rules for the owner property value, or for a combination of owner and product.
You specify the inspection rule arguments for each inspection rule, namely the parameters for the checks being performed.
-
You only perform a product inspection.
Assign an inspection procedure to define whether a check is to be performed. If a check is to be performed, you define whether it is to be a 100% inspection or a sample inspection.
-
Depending on the inspection procedure, you also specify a sample procedure or a sample-drawing procedure and dynamic modification rule, if required.
-
If required, you assign documents that contain the inspection instruction or product specifications, for example.
When the system creates an inspection document based on the inspection rule, it passes the assigned documents on to the inspection document.
-
You specify a code group for the inspection document valuation. For HU inspections, counting, and returns, you also specify a code group for items. For inbound deliveries and warehouse-internal movements, specifying a code group is optional.
-
You specify an action profile of the post processing framework for printing documents belonging to the inspection document and sample-drawing instruction.
-
If you want the system to automatically create samples when creating an inspection document, specify a sample type, a sample-drawing procedure, and a sample-drawing unit.
-
If you want to decide on the samples to be created separately, specify a decision code.
-
If you want to record defects and deviations, specify a finding type and a catalog filter for findings. Use the data that is offered for defects. For effort, the catalog filter corresponds to the defect group.

