Differeence between Lock object and enqueue_e_table

Former Member — Sun, 14 Mar 2010 14:19:21 GMT

Hi ,

what is diff between Lock object and enque_e_table. Where to use enqueue_e_table and where to use lock object.

I think with a lock object i can lock more than one table (passing tables in secondary table). Please correct me.

Re: Differeence between Lock object and enqueue_e_table

Former Member — Sun, 14 Mar 2010 14:41:06 GMT

This message was moderated.

Re: Differeence between Lock object and enqueue_e_table

Sandra_Rossi — Sun, 14 Mar 2010 20:51:51 GMT

A lock object does not really "lock a table" though most of lock objects refer to a database table.

I explain:

The principle is that when 2 programs lock at the same time with the same lock object, only the first will succeed.

If you have a program which does not use the lock, it may update the database table without any problem.

All programs which update a table have to use the same lock object. Note that users are always able to update this table via SM30 as they don't know the lock object to be used.

enqueue_xxxx is the name of the generated function module used to lock the xxxx lock object. E_TABLE lock is ONLY used by SM30 if I remember well, so that to prevent one table from being updated via SM30 by 2 persons at the same time. But it is not related at all with programs which would also update this table.

Edited by: Sandra Rossi on Mar 14, 2010 9:53 PM

topic Differeence between Lock object and enqueue_e_table in Application Development and Automation Discussions

Differeence between Lock object and enqueue_e_table

Re: Differeence between Lock object and enqueue_e_table

Re: Differeence between Lock object and enqueue_e_table