Hi all,
Big thanks for your quick answers and confirming my expectation on the implicit commit.
The problem is that I have multiple programs updating the exact same record in a custom table (@Ashish: No std module with commit parameter). (with identical information but unknowingly of eachother's updates). I do not mind the multiple updates, but my original implementation (direct update in the program itself) resulted in physical locks which lasted so long that there was another program kicking in and trying to update the same record.
My initial thought was to fix this by NOT creating a physical lock but moving the actual update into a self developed specific update task FM. Unfortunately, the updates also need to happen in programs lacking an explicit commit.
@Clement put me on an interesting other angle: if the updates are identical than a lock operation would work fine, as the update could be skipped in that case...
Thanks Clemens!
mh