topic Re: Want how the Commit work statement behaves. in Application Development and Automation Discussions

Want how the Commit work statement behaves.

Former Member — Tue, 29 Aug 2006 10:55:16 GMT

Want how the Commit work statement behaves.

Like if 2 programs are updating the same table and they have read the same record and are trying to update the same . One is using commit work immediately and the other is using commit work afterwards. Which of these changes will get reflected.

These are 2 different programs.

Re: Want how the Commit work statement behaves.

Former Member — Tue, 29 Aug 2006 11:16:22 GMT

Hello ,

Obviously the fist commit will update the table.

But here they might be updating the values in the table as it is a same record. Insertion is not possible as it will leads to dump.

1. Commit work :

Commit work performs a database commits and closes the Logical unit of work in a asynchronous way.

2. Commit work cannot be used in call function update task.

3. a commit work can use for calling performs also.

Thanks,

Krishnakumar

Re: Want how the Commit work statement behaves.

Former Member — Tue, 29 Aug 2006 11:29:21 GMT

they will be sequently, but they don´t allowed to insert the same record, if you want to solution this problem, you can use the "que" and "deque" functions.

regards

Re: Want how the Commit work statement behaves.

Former Member — Wed, 30 Aug 2006 07:23:45 GMT

check the sap help on LUW

http://help.sap.com//saphelp_crm40sr1/helpdata/EN/fc/eb3b64358411d1829f0000e829fbfe/frameset.htm

Kind regards, Rob Dielemans