lock objects

[Former Member]

plz explain this lock mode with e.g.

Exclusive but not cumulative

[Former Member]

Exclusive but not cumulative lock

X (eXclusive non-cumulative)

Whereas exclusive locks can be requested several times by the same transaction and released one by one, an exclusive, non-cumulative lock can only be requested once by the same transaction. Each further lock request will be rejected.

[Former Member]

Hi,

Direct extract from help.sap.com

Exclusive but not cumulative: Exclusive locks can be requested several times from the same transaction and are processed successively. In contrast, exclusive but not cumulative locks can be called only once from the same transaction. All other lock requests are rejected.

Thanks,

Sriram Ponna.

Edited by: Sriram Ponna on Feb 8, 2008 1:15 PM

[Former Member]

hi,

The ABAP Dictionary provides support when you set and release locks. To do so, you must create lock objects in the ABAP Dictionary. Function modules for setting and releasing locks are automatically generated from these lock objects; these can then be linked into the application

program.

You set a lock entry by calling an ENQUEUE function module for an appropriate lock object. You can find out which lock objects are available for a database table from the table's where-used list in the ABAP Dictionary. The "lock" and "unlock" function modules for the selected lock object require only the ENQUEUE_<Name of lock object> and DEQUEUE_<Name of lock object> naming conventions. In

general, you need only pass the interface key fields. Default values are passed to all the other parameters.

Exclusive but not cumulative lock

X (eXclusive non-cumulative)

Exclusive locks can be requested several times from the same transaction and are processed successively. In contrast, exclusive but not cumulative locks can be called only once from the same transaction. Each further lock request will be rejected.

Hope this is helpful, Do reward.

[Former Member]

resolved