cancel
Showing results for 
Search instead for 
Did you mean: 

DEQUEUE

Former Member
0 Kudos

Hi,

I am doing dequeue on vbak table.

From the second screen if i select F3 (ucomm = 'back').

I am doing dequeue.

even in debugging i am getting sy-subrc 0.

But the lock is not released.

CALL FUNCTION 'DEQUEUE_EVVBAKE'

EXPORTING

mandt = sy-mandt

vbeln = likp-vbeln

EXCEPTIONS

foreign_lock = 2

system_failure = 3.

any suggestions.

Message was edited by: raja gurrala

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi christian,

is that gud to use dequeue_all.If any body is running the same txn what wud be their status??

i wrotedown rollback work ,now the lock is getting released..

Is that ok to write?

please suggest.

Thanks,

Raja.

christian_wohlfahrt
Active Contributor
0 Kudos

Hi Raja!

If you did not do any DB changes up to the F3-moment, a commit work might be better than rollback work - but it's just a feeling.

Dequeue_all sounds dangerous (really all? No!), but is in fact restricted to the actual transaction or session (here I'm not 100% sure, but most times that's identical). Same user, different sessions, other users are not touched by dequeue_all.

I think, implicit a dequeue_all is anyway included in a commit work (or rollback work).

Regards,

Christian

Former Member
0 Kudos

Hi,

Check whether UR locking only one entry or the

entire table.

If UR using

call function 'ENQUEUE_EVVBAKE'. then use

call function 'DEQUEUE_EVVBAKE'.

Hope this works.

Can get some info in SAP Note : 659081

Regards,

GSR.

christian_wohlfahrt
Active Contributor
0 Kudos

Hi,

check if your lock arguments are really identical in enqueue and dequeue. Also check, if this lock is really hold by this session (double click the line in SM12 to see details).

If nothing else will help, use DEQUEUE_ALL (and a commit work).

Regards,

Christian

Former Member
0 Kudos

Hi,

Don't pass the mandt parameter.

Thank you.

regards,

Karun M