ENQUEUEs and COMMITs

[Former Member]

Hi everybody!

I have the following problem:

I have to make sure that my program - which has a long running time - is running only once at a time.

My first idea was to create (or use an existing) lock object and call the appropriate ENQUEUE_xxx function module. However, I just read in the online documentation that a COMMIT statement will clear and release all lock entries made by my program. My program calls various BAPIs and therefore I COMMIT quite often. Will this clear the locking entry?

I. e. if my program reaches the first COMMIT statement will it be possible to execute the program in another process again? If so: Are there any alternatives?

Regards,

Joerg

[Former Member]

I guess BAPI_TRANSACTION_COMMIT will just commit the changes in R/3 via BAPI calls, so it should not effect the locks

[Former Member]

Hi everyone!

I just did some debugging and confirmed that the first COMMIT in my program clears the lock (I used FM ENQUEUE_E_TABLE for this purpose).

Is there any other way to set s system-wide lock?

Regards,

Joerg

[former_member194669]

Hi,

You are using ENQUEUE_E_TABLE for locking , by giving the table name, my suggestion is why don't you create lock objects for the tables as trying to lock.

I checked with ENQUEUE_EANLA (for my testing) after giving commit/bapi_transaction_commit still lock will be there in the table level upto DEQUEUE is applied.

a®

[Former Member]

It releases the database locks, not the SAP locks.

Rob

[Former Member]

hi

chk this thread

https://forums.sdn.sap.com/click.jspa?searchID=4820751&messageID=839219

if helpful, reward

Sathish R

[Former Member]

Hi,

Thanks for the link, but it still doesnt work for me...

Conceptually, my program looks like this:

START-OF-SELECTION.

CALL FUNCTION 'ENQUEUE_E_TABLE'
...
LOOP AT it_veeery_biiiig_table.
  CALL FUNCTION 'BAPI_xxx'
  ...
  COMMIT.

  CALL FUNCTION 'BAPI_xxx'
  ...
  COMMIT.
ENDLOOP.

The first COMMIT clears the lock. From that moment on it would be possible to start the program again - this should not be allowed, though.

Any other ideas?

Regards, Joerg

[Former Member]

Hi Joerg,

We had a requirement like this. As you said the first COMMIT deletes all SAP and DB Locks.

For this we created a customized DB Table with MANDT and PROGNAME fields. As soon as the program execution starts we check if there is an entry in this table. If NO we make an entry and proceed. If there is an entry we come out of the program.

Once the execution is completed (for the person for whom the INSERT was succesfull) we delete the entry from the DB table. This is not a GOOD Solution but yes, this is the way we made it worked. At the END OF THE PROGRAM PUT A DELETE STATEMENT TO DELETE THE ENTRY MADE FROM THE DB TABLE. Try to use a customized table for this purpose.

Please let me know if further details are required.

Regards,

Goutham.