cancel
Showing results for 
Search instead for 
Did you mean: 

Enqueue for work item XXXXXXXXXXX deleted by called application from sm21.

Former Member
0 Kudos

Hi,

In my R/3 System every i am getting " Enqueue for work item XXXXXXXXXXX deleted by called application" errr message from transaction SM21, login WF-BATCH. I am unable to find out the root cause of this error message. Can someone please give me idea what would be the possible cause.

Thanks in advance.

Regards,

Krushna Biswal

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Here is pair of fresh notes helped to me:

Note 1311626 - LEA WD:Creation of Leave leads to message H0/1 in system log

General situation with H0/1 system log entries is descibed here (see referenced notes as well)

1569475 - Enqueue of work item xxxxxxxx deleted by called application

Former Member
0 Kudos

Hi Krushna

How are your dear?

I have the similar issue in my R/3 System, but the note you have suggested is for Release 700. Our R/3 already on 701 SP5. Do you have any idea how could we resolve this issue.

Regards

Lukesh Bansal

Former Member
0 Kudos

Dear Krushna,

Sorry to bother you. I also got the same problem in my R/3 System and XI system. Could you tell me where you implement the notes ? In R/3 or XI ro both system ?

My support package is less then SAPBasis700 so I will implement some prerequiment notes. hope I can solve the problem. Thank you so much.

Mason Liu.

Former Member
0 Kudos

Hello Mason,

I had applied the given notes in R/3 System only and i dont have any XI system. If these system logs are coming through from R3 then youn need to apply in R3 System only. I have given all complete datails in my previous message. Please refer the sequence of notes. Or create message to SAP.

Regards,

Krushna Biswal

Former Member
0 Kudos

Hi Krushna,

That kind of problems occurs commonly on workflow processes (possibly XI). Implement OSS note, below;

BPE-RUN: H0/1 system log entries for transient processes

SAP Note Number: 1036061

Best regards,

Orkun Gedik

Former Member
0 Kudos

Hi All,

I have solved the same problem after apply the following SNOTE:

Note 1125717 - Enhanced analysis for DEQUEUE_ALL

Regards,

Krushna Biswal

Edited by: Krushna Biswal on Jul 15, 2008 2:30 PM

Former Member
0 Kudos

Hi,

We have a similar problem as Krushna did, but after applying note 1125717, it did not fix our problem as it was still putting entries into SM21 when leave was unlocked via workflow. It is only leave that it is doing it for. When we applied the note it did not create the WF_DEQUEUE_ALL checkpoint group entry. After creating it we left all parameters as inactive, but did activate the checkgroup. Can anyone help me determine whether these parameters are correct, as this note may not work for the simple fact that we have not configured the checkpoint group correctly and I can not find anywhere in the note to say how to configure it except to say to use SAAB to activate it.

Thanks in Advance,

Raymond Bates.

Former Member
0 Kudos

Hello Raymond,

After applied the SAP Note "1125717 -Enhanced analysis for DEQUEUE_ALL" i was not getting the system log entries " Enqueue for work item XXXXXXXXXXX deleted by called application" in SM21 but another short dump was started " SYNTAX_ERROR" so create a message to SAP they have suggest me to apply another two notes after that my problem has been solved.

Please apply the notes as per the sequence.

1. When you will aply the SAP Note 1125717, there are some pre requisite notes need to apply.

a. 1036181 Unauthorized syslog entry of type H0/1

b. 973013 Work item not completed

c. 1040693 Unauthorized syslog entry of type H0/1

d. 1152956 Unauthorized syslog entry of type H0/1

e.1125717 Unauthorized syslog entry of type H0/1

If you are having support pack level " SAP_BASIS 700 0011 SAPKB70011 SAP Basis Component" then you will not get the Syntax_error; if you are having less than that; then please apply

SAP 1016171 and 1050793.

Hope your problem will be solved. No need to activate the checkpoint by using the SAAB transaction. I have also tried to activate the same but i dont what is the appropriate package for it.

The most important thing is i asked to SAP what is the root cause for this they have simply said it is program error.

Regards,

Krushna Biswal

Former Member
0 Kudos

Hi Krushna,

Thanks for your response to our problem, but unfortunately we had those notes applied beforehand. We are up to SAPKB70014. SAP are now currently looking at trying to resolve the problem.

Thanks,

Raymond.