Hi Yaz,
Let me try answering your questions.
Answer - Part 1:
* Unless there is any logistic movement happening, batches for materials available under unrestricted stocks can't be pushed into inspection stock.
* But you have an option to put the materials of unrestricted stocks in 'Restricted' usage using MSC2N.
* You can manually create a inspection lot of type 89 [which is not linked to stock posting], for the same material + batch.
* Else, you can check the feasibility of creating an enhancements in such a way that once MSC2N is executed to change the batch status to 'restricted', it should trigger inspection lot creating functionality for the same material/batch/plant combination and create inspection lot of type 89 in the background.
* Then perform Result recording, UD posting.
* Use a Follow-up action linked to UD code. Once UD is done then this follow-up action should be triggered to call MSC2N and update the batch status form "restricted" to "unrestricted" if UD = A. Else, if UD = R, the call the transaction MB1B/MIGO + MvT 344. to post the material stock to 'blocked' stock type.
Answer - Part 2:
* In case you are trying to copy already result recorded MIC values form one inspection lot to another inspection lot [normally same inspection plan related], then there are already several threads in SCN speaking about result copy functionality. Please explore. This is possible.
* In case while copying results for Inspection lot 1 MIC values linked to inspection plan 1, to inspection lot 2, having different inspection plan, then only the MIC's which are common would be copied to the 2nd inspection lot.
* In case you still wish to copy the results for the MIC's form inspection lot 1, which are not available in inspection lot 2, then there is a mechanism available to first add these new MIC's in QE01 as 'Ad Hock' MIC. After that copying all the results form 1st insp lot to 2nd insp lot will be possible. While adding these new MIC's in inspection lot, their position number will follow the series 0800 as far as I remember.
* But here is a catch. ONLY COMPLETE COPY MODEL or REFERENCE CHARACTERISTIC type MIC can be added by such case. MIC's which are INCOMPLETE COPY MODEL can be used in the above mechanism.
Thanks,
Arijit