Hi Navdeep,
In your case, it seems a complete custom solution for result upload (RR) followed by UD (if desired business condition matches) could be a solution.
In one of my last projects, we were working in such a result upload interface program, where if all results for all MIC's (Required/Optional) are having some results, then those results should be valuated to "A" with MIC system status "5", for all operations, then UD = A is being pushed by this interface program itself.
You be you can think of building similar program which uploads MIC results, valuates the uploaded MIC results, closes the MIC results for all MIC's. And, if all the business conditions (Z-field as you mentioned) are satisfactory, the same program calls the UD BAPI and do the UD = A. So no further manual interference is required for those conditions.
If there is any issue in any of the results uploaded for any of the operations involved, then UD = A will not be set programmatically, and user needs to do UD for that specific inspection lot.
Hope this process may help you.
Thanks,
Arijit
