topic Re: Lock Object Concept required in Application Development and Automation Discussions

Lock Object Concept required

Former Member — Fri, 13 Jun 2008 06:54:28 GMT

Hi Everybody,

I have a quary. I have created a custom table which will be used to store master data entered by multiple Users through a module pool program. The program has following functionalities stated below:

CREATE : Entry of new data.

CHANGE: Changing of existing record.

DELETE: Delete existing record

I need to implement lock system inside the module pool program while performing the above operations. In CHANGE and DELETE mode I have implemented record lock system. But in case of CREATE mode which lock mode should I use, ie should I use whole table lock or particular record lock? agerly waiting for reply.

Regards,

Pulokesh

Re: Lock Object Concept required

Former Member — Fri, 13 Jun 2008 07:02:11 GMT

please find below links will be helpfull.

http://help.sap.com/saphelp_nw70/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/af/22ab01dd0b11d1952000a0c929b3c3/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/cf/21eef3446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ef0d446011d189700000e8322d00/content.htm

Re: Lock Object Concept required

Former Member — Fri, 13 Jun 2008 07:08:58 GMT

Hi,

To create a new entry you need not lock the table. But still if you want to lock the table and dont want any one else to modify table while you are creating the lock it has to be on table level. You can not put lock on record level for a new entry.

Hope this clarifies your doubt.

Regards,

Lalit Kabra