cancel
Showing results for 
Search instead for 
Did you mean: 

Possible reasons for SAPLSENT (ENQUEUE_READ) time out

former_member197445
Contributor
0 Kudos
1,629

One of our most frequent time out runtime errors found in ST22 is in program SAPLSENT (ENQUEUE_READ).

The line it always times out on is line 191, "CLEAR ENQ."

  REFRESH ENQ.

  LOOP AT raw_enq.

>>>   CLEAR ENQ.

    MOVE-CORRESPONDING RAW_ENQ TO ENQ.

Other information provided.

  Program............. "SAPLSENT"

  Screen.............. "SAPMSSY1 3004"

  Screen Line......... 2

  Transaction......... " "

  Call Program........."SAPLERFC"

  Function Module..... "ARFC_DEST_SHIP"

  Call Destination.... "NONE"

Any ideas that could help me address this situation?  Let me know if I can post more info that would help troubleshoot. 

I appreciate it!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Also, this points to trfc entries. Please check if there are long running entries in SM58.

former_member197445
Contributor
0 Kudos

You're right, I do show problems from a Z program in SM58.  Is this something that the Note referenced above will help with?  Or are there changes that can be made in the Z program responsible.  (Apologies if this should move to the ABAP community forum.)

P.S. I am on 700 support pkg level 333.

Former Member
0 Kudos

That note can be a general one, but for this issue the developers should investigate how the locks are handled in the program. They should fix it.

Thanks,

Samik

former_member197445
Contributor
0 Kudos

Thanks a bunch.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Case,

What is your Basis support package level.

Check if this not is applicable for you -

Note 1705027 - ENQU: Cleaning up resources in ENQUEUE_READ

Thanks,

Samik