Enqueue for work item <n> deleted by called application

[Former Member]

Hi All

We upgraded from 4.6C till ECC6.0 and from then we receive occasionaly messages in SM21: Enqueue for work item 000001198539 deleted by called application.

This results in problems when 2 dialog task are executes after each other. Somethimes the second taks is not executed. I find in the log the following errors:

- Temporary error in result processing of work item 000001199739

- Error when loading component: Work item 000001198388 locked

- Work item 000001198388 locked by user WF-BATCH (enqueue error)

This is the head of the WF that's locked..

We implemented all relevant OSS notes regarding the message, but still we receive those messages (notes 1040693 - 1050793 etc) We are on support package SAPKB70012.

I have checked the code in our custom WF and in some background task we use a DEQUEUE_ALL. Can this be the problem? The WF worked perfectly in 4.6C.

  CALL FUNCTION 'ENQUEUE_EFBKPF'
   EXPORTING
*   MODE_BKPF            = 'E'
*   MANDT                = SY-MANDT
     bukrs                = i_bukrs
     belnr                = i_belnr
     gjahr                = i_gjahr
*   X_BUKRS              = ' '
*   X_BELNR              = ' '
*   X_GJAHR              = ' '
*   _SCOPE               = '2'
     _wait                = 'X'
*   _COLLECT             = ' '
   EXCEPTIONS
     foreign_lock         = 1
     system_failure       = 2
     OTHERS               = 3
            .

  IF sy-subrc <> 0.
    RAISE locked.
  ENDIF.

  UPDATE vbsegk SET zlspr = i_zlspr
                WHERE ausbk = i_bukrs
                  AND belnr = i_belnr
                  AND gjahr = i_gjahr.
*                and ( zlspr = 'A' or zlspr = 'Y' ) .


  COMMIT WORK AND WAIT.

  CALL FUNCTION 'DEQUEUE_ALL'
       EXPORTING
            _synchron = 'X'.

Any help appriciated

Kristof

[Former Member]

I have send an OSS tot SAP and there development team is looking to this problem

Kristof

[Former Member]

Hi Kristof,

did SAP solve the problem?

Thanks

Fero

[Former Member]

Hi Frantisek Vojtek

SAP has answered that because in the log of their standard program RSWERRE there are no entries, so they say that it is nog a bug in the program of the workflow engine.

That's the answer of SAP

[Former Member]

The entries we have solved by removing the DEQUEUE_ALL function in a method.

Still we receive somethimes errors in the workflow log

Temporary error in result processing of work item <n>

Message no. SWP030

Error when loading component: Work item <n> locked

Message no. SWP034

Work item <n> locked by user WF-BATCH (enqueue error)

Message no. WL605

[Former Member]

Kristof,

We are occasionally getting a similar enqueue error message sent to the workflow admin account. The workitems seem to have processed normally...the error message is generated for some reason. We get a normal userid instead of WF-BATCH but everything else is the same.

Have you found any reason/solution for this?

[Former Member]

Hi

Yes we have solved the issue. We have changed or workflow. The reason is that in our workflow we have a branch where task run simultaneously and SAP do not garentee in ECC60 that 2 dialogue task will run in dialogue...

So we had to change on WF and combine the 2 taks in one taks...

Kristof

[Former Member]

Well I'm getting it when running a task to store an image with archivelink. There is only one task.

[Former Member]

Check this Thread

[Former Member]

Hi Arghadip

Thanks for your reply

I have read the Thread but this doesn't help me.

The 2nd task is created and moved to a new folder in the SBWP and there the user can execute the task. But this should be a advance in dialog task. The actual agent is found and linked to the second task.

When this occurs I see messages in SM21.

Kristof

[KKilhavn]

Take away the COMMIT statement.

[Former Member]

Hi Kjetil

Thanks for your reply. Could you give some explanation why to remove the commit statement?

Thanks

[KKilhavn]

If I recall correct it is a no-no to call COMMIT WORK inside methods. Sorry, I can't give you a reference for that off the top of my head.

Unless my memory is playing tricks on me I most likely recall it either from the ASUG mailing list for workflow or from the workflower's bible (Practical Workflow for SAP).