Background work item error ( work item xxxxx locked by user xxxxx ) enqueue error

[former_member249671]

Hi,

I have come across with an error in one of the workflow background step.Please refer below and guide me to proceed further.

I have a user decision step in a workflow and in approve branch of the step has a background task which copy the attachments of parked document.Here issue is when the user approves at user decision step ,and processing moves further to approve branch of the step which has a background step which is supposed to be executed by workflow system ( WF-BATCH )  goes to error due to the  work item locked by Dialog user who approved the user decision.  However,this error-ed work item is cleared when the  background job SWWERRE is executed but this delays the posting process for sometime.

Why the background work item is locked  with dialog user who completed the preceding step of a workflow ? Is there any way to avoid this situation to accelerate the document processing ?

Thanks in advance.

[Former Member]

Hi Sunil,

If the same document is opened by any other user at the same time, the workflow will show that message, this is a part of standard workflow process (for some workflows) but it should be an information not an error & the workitem will not be available for the next user. Check any user opened the same document using any SAP transaction,(you can check the user in SM12).

Check workflow log, step history tab, what happened to that process.

Regards,

Murali Krishna.

[Former Member]

Hello.

Although it may seem weird this happened to me TWICE in my system.

Both times happened in Development Server.

When a user performed a Dialog Task and the system creates the next background task, sometimes the lock of the user is active and BLOCKS the next Workitem (The Background Task) from being executed.

After a while, when job SWWERRE is launched, it gets the Workitem and now that the lock is lifted, it can be executed again.

There is a sap note:

1057585 : Work item <xxx> locked by user

It didn't solved the problem for me, but it may work for you.

As stated, this is a enqueue problem.

Regards.

[rajeshkothamasu]

Hi,

execute the sm12 for locked things. Delete all the locked items.

If the WI is not locked anymore (check SM12), use txn SWIA-> Supply the ID, Select the line and click on Execute without check to execute the work item.

Do not delete it

It will tell the characterisitics of workitem.

[former_member249671]

Hi Rajesh,

Thanks for reply.

User completes the user decision step. Users will not be knowing that the subsequent background work item goes to error . The were just wondering why posting is not happening after approve also ?

This issue happens often not to every document as well.

[I042439]

Hi Sunil

Are your steps - Decision and then the background step (going in error) placed in a Fork? 1 of 2 fork? If yes, what is happening in other branch(es)?

It would be good to see your workflow design as a screen shot.

regards,

Modak

[former_member249671]

Hi

Its not in Fork step.

screen shot attached . Task under approve branch is a background one which goes to error after approve due to en queue error by the user who approved .

Thank you.

[I042439]

Hi Sunil

Can you give a screen shot of the error (Step History from technical WF Log)? Which "workitem" is referenced in the error? The Dialog WI or the WI of the background step?

Are there any events getting triggered on Approve in the WF?

Is there any other processing which renders this branch obsolete? [that was the purpose of asking for the fork]?

Also, what is the purpose of this background step? can you give details of this step and any specific settings?

And, it is good to see the whole of the WF instead of just two steps.

regards,
modak

[anjan_paul]

Hi,

What lockin behaviour maintained in SWDD-> BasicData - Version Dependent-> Lockin Property maintained. Is it standard behaviour anythin else

[Former Member]

Hi. maybe it is usefull. I resolve this issue, if agent that execute workitem is not an admin of the workflow. in other case i get this error

Error processing following event linkage:
IDOCCONDA2 INPUTFINISHED WORKITEM

Following error occurred:
WL 605
000000004004
KS0000000020

Message text:
Work item 000000004004 locked by user KS0000000020 (enqueue error)
SAP System: RHD
Client: 200

Event container contains following data:
_EVT_CREATION_DATE              000000008D20140905
_EVT_CREATION_TIME              000000006T110916
_EVT_CREATION_TIMESTAMP         000000008P20140905070916
_EVT_CREATOR                    000000014CUSKS0000000020
_EVT_ID                         000000020N00000000000000000001
_EVT_LANGUAGE                   000000001CE
_EVT_NAME                       000000032CINPUTFINISHED
_EVT_OBJECT                     000000090oRHDCLNT200IDOCCONDA20000000000004004
_EVT_OBJKEY                     000000070C0000000000004004
_EVT_OBJTYPE                    000000032CIDOCCONDA2
_EVT_RECEIVER_ID                000000032C000000004004
_EVT_RETRY_COUNT                000000002N00
_REQUESTER                      000000090oRHDCLNT200WORKITEM  000000004004
_SOURCE_MANDT                   000000003C200
_SOURCE_SYSID                   000000008CRHD
_TCODE                          000000020CSBWP
Event container appended as attachment.

Event linkage not changed.
Event stored temporarily.
Events can be redelivered via event queue
administration (transaction SWEQADM).