Inspection object types define the software component, the process, and the object for which you can create inspection documents in the Quality Inspection Engine (QIE). An IOT is created in the QIE from the consumer system.
- IOT Preliminary Inspection Inbound Delivery
If you activate an inbound delivery notification, the system generates an inspection document automatically for checking complete deliveries. The system requires an inspection rule for the current version of the inspection object type and warehouse number.
The inspection document is released automatically when being created, so that it is already available when the goods physically arrive. The document cannot contain samples or items and is stored as a reference document for the delivery header in the delivery.
This IOT is only available in a Supply Chain Management based EWM, up to EWM 9.5.
- IOT Preliminary Inspection Handling Unit (HU)
For each delivery of a complete commercial truck (with multiple deliveries), you can classify all HUs as good or bad. When you have classified all the HUs, the system creates the HU inspection document automatically. In doing this, it generates one inspection document for each delivery and one item for each HU in this inspection document. You can also decide this directly for the good HUs. You then manually process the bad HUs in an additional process in the inspection document.
Inspection documents for HUs cannot be scheduled in advance. You can only create them manually for the HU inspection using RF.
Because you always create this inspection document manually, it makes sense to create only one inspection rule for the warehouse number and for the version of the inspection object.
This IOT is only available in a decentralized EWM, it is not available in embedded EWM.
- IOT Counting Inbound Delivery
The system creates this inspection document automatically, depending on Customizing for the inspection document creation within inbound delivery processing. The system releases it when it creates it. Counting is always a 100% inspection, because counting samples is irrational.
This IOT is only available in a decentralized EWM, it is not available in embedded EWM.
- IOT Q-Inspection Product/Batch Inbound Delivery
The inspection document is automatically generated, but released with the first goods receipt posting. The inspection quantity is determined from the deliver quantity and if the inspection rule contains a sample-drawing instruction, the system generates corresponding samples for the inspection document.
There are subtypes of this IOT, acceptance sampling (for externally procured goods), and presampling in production (in-house production), which are relevant before goods receipt.
- IOT Q-Inspection Returns Delivery
This works in a similar way to the quality inspection for a product, but it is specifically for returns. This IOT offers the additional functionality to enable a usage decision in the warehouse with delegating the follow up action to an external system, for example, SAP CRM.
For example, a returned product item is received in the warehouse. A warehouse worker inspects the returned product item and rejects it for quality reasons. The decision about the follow-up action is made by the sales clerk in an SAP CRM system.
A return process using Advanced Returns Management with a quality inspection process is supported in decentralized as well as in embedded EWM. A customer returns process that does not use ARM is generally not supported in SAP S/4HANA embedded EWM.
- IOT Q-Inspection Product/Batch Warehouse-Internal
Warehouse-internal inspection documents can be created manually, using either the RF environment or desktop transactions. They can also be created automatically using the interval assigned to the batches to be inspected.
- IOT Defect Processing
Using the Record Warehouse Defect app in the QM component, you create defects with the defect category Warehouse Defect to record defects for EWM-managed materials. You can enter details such as the defective material, the plant, and the storage location.
This IOT is available in embedded EWM starting with SAP S/4HANA 2020, and in decentral EWM starting with SAP S/4HANA 2023.
Generating IOT versions
For any of the available inspection object types, you first must generate an inspection version in your system. This is valid for all warehouses. Only after that the various settings can be done.
After certain changes, it might be necessary to create a new version for an IOT. In this case, you should check SAP Note "2866278 - How-to generate new IOT version in EWM" for the follow-up steps.
Note
The note describes in the step 4 how to reactivate inspection rules and that the transaction /SCWM/QRSETUP can list inactive rules. For finding the inactive rules, you must use the Advanced Search, there you can set the flag to Include Inactive Versions.
