Inspection Plan Migration strategy/methods

[Former Member]

I have been through multiple iterations of loading inspection plans via the standard LSMW objects and I am still looking for an effective way to load inspection plans that have common inspection characteristics but different specifications and/or control indicators.

I have tried loading plan-specific specifications using preset indicators and updating the specifications directly in the creation load.  This still causes the batch input to require running in display errors mode because when the indicators differ from the master inspection characteristics, SAP calls screens that have different field combinations than the batch input.

I have also tried loading all inspection plans with the same indicators, then doing recordings of QP02 for updating control indicators and specifications.  This requires extracting data from PLMK so ensure that the correct records are selected in the recording, and multiple recordings to allow for the different screens that are called after changing indicators (for example, allowing for a screen with only an upper limit field then another recording allowing for a screen with an upper and lower limit).  I don't consider this method stable at all.  There are too many recording and too much manual data manipulation.

Does anyone have a good method for loading inspection plans with common characteristics but plan-specific specifications?

[former_member214131]

Hi, I have used SAP standard BI method to load quite complex plans (in data migration - load perspective) which comprised of header details with Long Text (LT) & Material & Vendor assignament, operations with LT, MIC (Standard & Local with Qualitative / Quantitive) with LT.

It works fine and I have NOT faced any problems as such.

Hope it helps.

Best Regards, Murugesh

[nitin_jinagal]

Hi Nick,

Im not sure if I could follow you correctly. But did you try loading the task list using CWBQM?

Using this Tcode, you can load all the inspection plans for a specific MIC.

ntn