We are upgrading from R/3 4.7 to ECC 6.0.
There are around 25k active workflows.
It is practically impossible to bring all the active workflows to a logical closure
1. I would like to know the best practices to handle the active workflows during upgrade.
2. Can we put the workflows in some inactive state or suspend mode & restart it from that point after upgrade ?
3. If the answer is to bring them to a logical closure or terminate them then, we might have to terminate few workflows. If we terminate a workflow at step 10(out of Step 20), is it possible to restart the workflow from Step 10 or we have to restart from Step 1.
4. If we restart from Step 1, wont there be any business impact wrt the terminated workflow which was already processed till step 10.
Would appreciate for any pointers or answers to above queries.
Rick Bakker replied
>1. So the only option is to bring all active workflows to a logical closure or complete them manually ?
It's not the only option but it is the most sensible one. As I said on another thread, the best way to avoid problem is to go into the upgrade with as few running workflow instances as possible.
>2. When we say manually, do we run the FM to complete each workitem ?
Or you could do it from a transaction, like SWIA
>3. Is there any possiblity of mass manual closure ?
There is, you could write a program to run the relevant FMs.
>4. If we complete manually, post-upgrade will it be restarted from scratch or from the step where it was manully closed ?
If it's been completed then (of course) it won't restart.
I would say there is something very wrong with a workflow environment with so many uncompleted workflows, possibly a design error. You should write a report to analyze the outstanding workflows, split them into different WS numbers, split again into which step(s) they're waiting at. It could be that a large number of them can just be completed without any problem, but you won't know until you look.