topic Re: When to use logical database locking? in Application Development and Automation Discussions

When to use logical database locking?

gopalkrishna_baliga — Fri, 09 Jul 2010 06:05:42 GMT

Hi Experts,

I have a custom table in one SAP R/3 system A. I am updating this table from another SAP System B from two different programs ( one an user exit and another one a function module). Suppose user exit code is updating the table and at the same time the Function module also tries to update the same table. I think SAP automatically takes care of locking the table and unlocking it. I hope we don't have to explicitly code it right?

Then why SAP has provided ENQUEUE and DEQUEUE function modules? When exactly do we need to use them?

Please help.

Thanks

gopal

Re: When to use logical database locking?

Former Member — Fri, 09 Jul 2010 08:56:11 GMT

Hi,

SAP will not automatically takes care of locking the table and unlocking it. you need to explicitely create ENQUEUE and DEQUEUE function modules.

Regards,

Preetham

Re: When to use logical database locking?

SuhaSaha — Fri, 09 Jul 2010 09:10:13 GMT

Why don't you [Google|http://tinyurl.com/2ubgkb2] it ?

Re: When to use logical database locking?

ThomasZloch — Fri, 09 Jul 2010 10:35:23 GMT

Please search for available information before posting, don't post basic or generic questions.

Thread locked.

Thomas