Pending tasks of WF-BATCH after SWU3 fix
I am working on ECC6.0. We have the following situation.
The SWU3 with proper authorizations for WF-BATCH was configured and was running fine till last week. But, during some system build activities, something went wrong and WF-BATCH got locked. And so, all the background processes pertaining to wflow got affected.
In this, one of the situations was, an approver approving work item from Portal. We had a workflow instance started 1 week back and the approver just approved the task. And the wflow log shows that the witem was approved (with container element _RESULT = 001), corresponding to decision choice 1.
After this the next witem needed to be generated and the next step is a background task(to be done with WF-BATCH itself).
But, due to WF-BATCH locking( the "Configure RFC Destination" tab was NOT OK), this didn't happen.
Now, our Basis fixed this by resetting the pwd for WF-BATCH. But, the creation of next work item and also the next step of background task,both are not getting picked up automatically.
My understanding is that this is normal as the WF-BATCH DOESN't AUTOMATICALLY pick up all the pending witems (like generating next witem, performing background tasks et.,).
Is this correct ?. IF not, can somebody explain how it works.
Also, in situation like this, what's the solution to generate the next work item ?
To be more clear, actually what happened was, though the work item status is shown as COMPLETED, it's result has not actually not got processed by WF-BATCH as it should at the end of any workitem action.
Can somebody tell me how to fix this kind of issue.
Thanks in advance
Edited by: Venugopal Jogi on Sep 2, 2008 9:30 PM