cancel
Showing results for 
Search instead for 
Did you mean: 

Locking concept

Former Member
0 Kudos

Hi All,

If i make correction in the webdynpro for the particular transaction and the same time i am making some correction in the same transaction in R/3 .

how does the lock object will work in this scenario.

Thanks & Regards

Ganesan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

you should call same lock function as system transaction.

See sm12 to see what is locked by standard transaction.

Now look at se11 for lock objects matching this entry.

Display Lock object.

See menu option Goto implementing modules in se11 to get function name.

You should call this function in you model class (or in the comp controller if it is small

quick and dirty.) to lock the object.

cheers

Phil.

Former Member
0 Kudos

Hi

Thanks for reply, if multiple person using a same webdynpro application . how the

locking concept will work. or as a developer how should i handle this scenario ?

Regards

Ganesan.k

Former Member
0 Kudos

Hi Ganesan,

Phil's reply has a clear answer.

See, before performing any DATABASE(CREATE/CHANGE/DELETE) operations, we normally lock the object. This can be done by using the <b>lock Function module</b>.

Phil has clearly told the process to identify this LOCK FUNCTION MODULE.

Regards

<i><b>Raja Sekhar</b></i>

Former Member
0 Kudos

locks can if the LOCK OBJECT is generated in SE11 appropriately

allow the same user in SAME session to attempt multiple locks. If this is really required.

Avoid, but sometimes useful.

The same user in another session should be treated like any other user. Lock out.

Cheers

Phil

Former Member
0 Kudos

What happens to the lock if the client (the browser) gets lost? Then no data will be sent to the application server and the lock will stay forever? I assume not, but cant imagine how this problem is solved by WebDynpro for ABAP.

Thanks

Rene

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Let's say we are using PA30 and maintaining Address Infotype.

So, you have opened PA30 for a particular employee in CHANGE MODE.

And when you try to access the same employee's Address Infotype data, you will obiviously your Lock function module say ENQUEUE_EPPRELE will not get a lock for that object. It returns an error.

So, you will not be achieve lock through WD Application.

Regards

<i><b>Raja Sekhar</b></i>