Help: Error Work item xxxxxxxxx currently locked by user 'WF-BATCH' ()

[glauco]

Friends,

Here we are using SAP 4.6C and we have a workflow in production system that is giving error messages on its log indicated by a red semaphore. <b>By clicking on the semaphoro</b> it gives me the message:<b> "Work item xxxxxxxxx currently locked by user 'WF-BATCH' ()."</b>

This is a dialog task processing with a terminating event. When the user is completing the task, the abap custom code (we are using a Z-program) trigger the event so this task can receive this event and the workflow can continue.

But <b>when this terminating event is triggered (Terminating event received), occurs this error showed above.</b>

Until now I didn't found any explanation about it and I know that the database is get dumps a lot. I've studied and found out that the dumps happened in the moment that the sub-workflow was on a fork and one wait for step listenned a event and probably tryied to kill others fork's legs. I know that because on workflow log, on this workflow log's line show messages saying that was impossible to change task (one of the task that is in another leg in the fork) status to cancelled...with red semaphoro.

p.s.: This error don't happen for all workflows initiated. It's happening with some workflows only.

p.s2: I've forgot to say that the production system here is very heavy, and all the tests in Developing system was alright!

thanks.

Message was edited by:

Glauco Kubrusly

[Former Member]

Hi Glauco ,

Im facing the same issue , the log says that ,<b> WORKITEM xxxxxx CURRENTLY LOCKED BY USER 'WF-BATCH()"</b>

I am dealing with Purchase Order Approval Workflow, this type of error often comes but when i try to manually approve it, it works.

But these days this error is common and client wants me to fix this..

I am new to workflows , so when I look at the conversation between u and Mike , I couldnt get it properly.. Can U please Guide me regarding this so that it would be handy for..

[Former Member]

Hi Glauco,

What are the dumps you have been having?

Gareth

[glauco]

I don't know why yet, but I'm think that it is happening for some things...

I'm thinking now that it can be the task hold by wf-batch, because I use a AFTER method configured in the task. Then, after completed, this AFTER method is executed in background.

I'm using terminating tasks to cancel the workflow too after had executed a wait fot event task, but I think its a lot of them.

[former_member186746]

Hi,

could this be caused by the advancing with dialog option on for wf steps and an incorrect agent assignment?

Kind regards, Rob Dielemans

[glauco]

Hi Rob,

While I oppened this question, there are so many extrange things happening here on the system as some lost (terninating) events (the most of my work items wait to terminating events).

It is very strange for me. Now I think that it is a infra-structure problem.

I've just changed the workflows and take out the Process control tasks. Because in my studies and comparing with database erros and deadlocks I saw that this problems happened in the same momment that Process control were executed.... and in the workflow tecnical log there are so many red semaphorous after Process control tasks were executed.

Another problem are ... imagine !!! Lost events... I've already read in workflow book (Practical workflow for sap) that there is a configuration to a maximum quantity for events in a system or database and I think if the quantity supported to events is exceeded, these events can be lost or ignored by the system.

I'll close this question here and open a new to discuss about lost events and queue management and infra-structure. Do you understand when I talk about infra-structure ??? When I'm saying it I mean the database and database management staff.

Message was edited by:

Glauco Kubrusly

[former_member186746]

Hi Glauco,

I remember we had the same problem of loosing events in 4.6c

This was caused by a program error of SAP when using the event queue for HR events.

Try searching OSS for that.

for the rest of the system, check sm21 regularly try to see if more strange things happen at the same time when loosing events.

Kind regards, Rob Dielemans

[glauco]

That's it. Here we're using 46C.

But here I saw a lot of workflows activated and not in use and both of them are triggering events. I think we have to deactive all those becuse they are concurring with my workflow.

But I'll try to see about this HR events... Are they the kind that I can see on SWEL too ?

I've tryied to use sm21 but I didn't understand how to interpret.

[pokrakam]

Hi Glauco,

You talk about terminating events and process control... are you trying to do both at the same time?

In other words a terminating event will complete a step, but if you have a wait step in another fork/calling flow/whatever that then tries to terminate the task via a process control step you will end up with two functions competing for your WI at the same time, which could cause some of the problems you describe.

Cheers,

Mike

[glauco]

Hi Mike,

Yes, some sub-workflows have forks with a leg with wait for event with a process control after that and the WF is waiting for the same event in the other fork's leg that is configured as a terminating event to a task (WI). But this configuration is not the same to all of the sub workflows.

I've already had take out the process control from all the forks that had these.

By the way I'm having problems with lost terminating events...that appear on SWEL but don't terminate the task. I'm seaching for SAP notes.

thanks.