10

Recurring Inspection (IOT 5) in SAP EWM

 2 years ago
source link: https://blogs.sap.com/2022/05/18/recurring-inspection-iot-5-in-sap-ewm/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
May 18, 2022 3 minute read

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

1

Inspection Object Type Version

SPRO>>SCM Extended Warehouse Management>>Extended Warehouse Management>>Cross-Process Settings>>Quality Management>> Define and Activate Warehouse-Dependent IOTs

Activate%20IOT

Activate IOT

Picture3-19.png

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.

Picture4-19.png

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

Picture6-20.png

Material Master Setting

Picture7-17.png
Picture8-15.png
Picture9-8.png

Process cycle

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.

Picture10-10.png

Batch gets created in Inbound Delivery itself

Picture11-9.png

This delivery will flow to EWM. Create the task and do Putaway

Picture12-8.png

After GR and Putaway are complete then ERP delivery gets updated and Batch data starts appearing in transaction code MSC3N

Picture13-9.png

The classification data also starts appearing

Picture14-6.png

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

Picture15-4.png

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.

Picture16-4.png

Also don’t forget exception code as CRID and uncheck Simulate

Picture17-3.png

Once you execute the program, the following screen appears and details in the logs will show

Picture18-3.png
Picture19-3.png

This will move the stock in Q4 and will also create Inspection lot for further processing.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK