Lock created using Function 'ENQUEUE_E_TABLE' fails after some time!

[Former Member]

Dear Abaper's,

I am using function "ENQUEUE_E_TABLE" to create a lock entry for a Z table when executing an Z report. And, in fact the function works. When I look up entries in transaction SM12, there is the entry.

My problem is, that the lock entry seems to disappear without any reason. It seems to me, that there must be something that delete's the entry even before I force the dequeue using function "DEQUEUE_E_TABLE". Does anybody knows, if there is any statemente that could be responsible for eliminating a lock entry in transaction SM12? Something like a commit work, other function call's or even BAPI's?

Thanks,

Marcelo Moreira

Points will be awarded.

[Former Member]

Hi Marcelo,

Only a DEQUEUE_E_TABLE can unlock the table.

Try to debug your report to see if somewhere it has a dequeue.

[Former Member]

Dear Ytamar,

This is what I expected to happen, but it isn't!! My report is not that long, and there is nothing that seems to unlock my table. But during debug I monitor also the lock table, but after some time the lock of my table is eliminated.

my report is something like that:

" call of the enqueue function for z_db_table
loop at itab.

" inside the loop statemente I call some BAPI's, one of them is the BAPI_TRANSACTION_COMMIT

endloop.

update z_db_table from table itab.

" call of the dequeue function for z_db_table

In debug, at least when I reach the update statement lock is gone!!

Any more suggestions?

Thanks