Skip to Content

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


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.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • author's profile photo
    Former Member
    Posted on Sep 10, 2014 at 09:19 AM

    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:

    Following error occurred:
    WL 605

    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_OBJECT 000000090oRHDCLNT200IDOCCONDA20000000000004004
    _EVT_OBJKEY 000000070C0000000000004004
    _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).

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 10, 2014 at 09:46 AM


    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.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Oct 14, 2014 at 10:29 AM


    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.


    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 14, 2014 at 12:18 PM

    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.


    Murali Krishna.

    Add comment
    10|10000 characters needed characters exceeded