Recurring Inspection (IOT 5) in SAP EWM
Recurring inspection is used when for a particular product regular inspection is required. In my case, the batteries of the products need to be charged every 6 months. So inspection lot was required to be generated at regular intervals for different products and the product has to be moved to Quality stock, so that it doesn’t get dispatched to the customer.
Here are the settings required to achieve this functionality.
SPRO>>SCM Extended Warehouse Management>>Extended Warehouse Management>>Cross-Process Settings>>Quality Management>>Generate Inspection Object Types Version
SPRO>>SCM Extended Warehouse Management>>Extended Warehouse Management>>Cross-Process Settings>>Quality Management>> Define and Activate Warehouse-Dependent IOTs
Following is the setting for the class in transaction CL02. These characteristics LOBM_QNDAT is mandatory for recurring inspection and characteristics LOBM_VFDAT is valid for my scenario and you can ignore this characteristic also.
Since I have tested the entire scenario with batch so I’ll be sharing batch settings also.
SPRO>> SCM Extended Warehouse Management>> Extended Warehouse Management>> Cross-Process Settings>> Batch Management>> Define Setting for Delivery – Warehouse Request
Remember that Batch needs to created in either ERP or EWM. Don’t think of creating the batch in the background and then adding the characteristics in EWM when the delivery flows. This is not going to work !!!
Create batches and add characteristics in ERP or EWM, only then system will accept the data. Else the delivery will get stuck in the queue.
In transaction OMJJ, add the following entry in movement type 101. This will update the characteristics in Batch when you’ll view MSC3N
Material Master Setting
Create the Inbound Delivery using VL31N and create Batch.
In my case, I am creating batch and filling the date of manufacturing in Inbound Delivery itself. You can create the batch and fill the Date of Manufacturing/ Date of production at the time of receiving in RFUI also.
Batch gets created in Inbound Delivery itself
This delivery will flow to EWM. Create the task and do Putaway
After GR and Putaway are complete then ERP delivery gets updated and Batch data starts appearing in transaction code MSC3N
The classification data also starts appearing
In order to create the inspection lot for the products for which recurring inspection is due. Goto transaction SE38 and run the program /SCWM/R_STOCK_TYPE_CHANGE
In the next screen choose the second option as “Create Insp. And Post Stock to QM stock” and don’t forget to check mark Consider Next InspDate (Batch) and enter the number of days Plus and Minus for which valid data is picked.
I have taken the number of days as 12 as the next inspection date is 12 days away.
Also don’t forget exception code as CRID and uncheck Simulate
Once you execute the program, the following screen appears and details in the logs will show
This will move the stock in Q4 and will also create Inspection lot for further processing.
Nice blog, thanks for the share.
One question: How does value of LOBM_QNDAT gets updated in the batch? Is that automatically updated based on some parameters?
From the Material Master
Nice blog, thansk for sharing.
One questions: How does value of LOBM_QNDAT get updated? is that automatically based on some parameters?
Nice blog with helpful screenshots. In the SAP ECC world, we had QA07 transaction for recurring inspection as well as blocking batch stock and now in SAP EWM we have program /SCWM/R_STOCK_TYPE_CHANGE which will be critical for recurring inspection.
Nice Blog !!!
Since SAP S/4HANA 2020 FPS01, new transaction has been introduced for SE38 and run the program /SCWM/R_STOCK_TYPE_CHANGE ( Change Stock Attributes /SCWM/STOCK_ATT_CHG)
I am using Decentralized EWM very 1st time. We are using QA07 in ECC and just moving batch to restricted stock in opening period of 7days but we not creating insp lot 09 there. Can we achieve same for EWM storage location using /SCWM/R_STOCK_TYPE_CHANGE in EWM. So some enhancement or SAP note is required to be implemented. Can you pls guide how to achieve this.