Skip to Content
0
Former Member
Apr 29, 2005 at 02:20 PM

Locking records for update in backend system?

54 Views

Sofar I have only used Web Dynpro for viewing data and inserting new data.

Now it is time for me to use some BAPIs for changing data.

What is the recommended way to update existing records?

To clarify what I am looking for:

Something like SELECT FOR UPDATE.

When I do a BAPI_*GetDetail I will get data that is presented to the user. I would like to lock that record, so that when the user has updated the data and has pressed submit, the update BAPI and the commit will release the record, so that other users can work with that very record.

If I don't do any locking, there is a risk that the following scenario becomes true:

1. User A retreives the record and starts to update the record on the screen.

2. User B retreives the same record and starts to update the record on the screen.

3. User A presses submit, the record is updated.

4. User B presses submit, the record is updated and all the changes that A made has been overwritten by B, even the ones that B didn't change.