Lock Objects

[Former Member]

If I want to lock any entry of any database Table without creating the Lock Objects in SE11, then how can I do that???

[Former Member]

i guess that isnt possible.

Message was edited by:

Kaluvala Santhosh

[Former Member]

hi,

You would need to create lock objects using SE11 Transaction without which you cant lock any entry

[Sandeep_Panghal]

Hi,

If u have to lock any table , then u should follow the Lock approach else i dont think this is possible.

[Former Member]

Hi Anurita,

Kindly close the thread and reward helpful answers

[Former Member]

hi,

You can check for available locks in R/3 for your table. Search the lock object in R/3 and If you can find the lock you can simply use this already existing lock.

Regards,

Richa

[abdul_hakim]

hi

itz not possible at all.

Cheers,

Abdul Hakim

Mark all useful answers..

[Former Member]

SELECT FOR UPDATE would lock the row befor the DB transaction will be commited.

[Former Member]

select for update - it's a DB-level lock.

Means - if you want to lock a record to prevent DB updates - that is fine, but if you use it to prevent access to this record - it's not going to help here.

Like if you use select for update but other programs use enqueue -> they will not see your lock and will think that data is NOT locked, they can read it into any internal structure, then you finish your update for one field for example.... BUT the other program can save the same record after your update is finished and it will actually reset your value back.

In other words - either ALL programs should use SAME locking technique (either select for update or enqueue) OR you may have a problem with "disappearing" updates.

[Former Member]

Hi all,

Does anybody know how long an object stays locked in SAP?

(transaction SM12)

Thanks

Kris