Use of COMMIT WORK in performance improvement

[Former Member]

Hi all,

Iam working on a report to improve it's performance and i got a tip from colleague to use commit work statement after any costly select statement so that it will be helpful in improving the report performance.

But i couldn't believe how these commit work statement is related to perfomance improvement.

Please give me some inputs.

Thanks in advance,

Raju.

[Former Member]

Hi all,

Iam working on a report to improve it's performance and i got a tip from colleague to use commit work statement after any costly select statement so that it will be helpful in improving the report performance.

But i couldn't believe how these commit work statement is related to perfomance improvement.

Please give me some inputs.

Thanks in advance,

Raju.

[qamar_javed]

Hi,

Check this link :

http://help.sap.com/saphelp_nw70/helpdata/EN/41/7af4bfa79e11d1950f0000e82de14a/frameset.htm

http://www.abapprogramming.net/2008/05/sap-abap-syntax-for-commit.html

Hope this helps.

Regards,

Qamar.

[Former Member]

hi,

see this

http://help.sap.com/saphelp_nw70/helpdata/EN/41/7af4bfa79e11d1950f0000e82de14a/frameset.htm

you sholud use commit work statement after INSERT ,UPDATE and DELETE commands

thanks

[Former Member]

Hi Raju,

In addition to above replies, Use the F1 help for Commit work, in Se38 write COMMIT and press F1...

Read the parent node brief info on SAP LUW(logical unit of work) and then read Commit Work, you will get a clear picture... as this says:

The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the current SAP LUW in the process.

Sachin

[Former Member]

The COMMIT WORK is not a tool to improve performance. The COMMIT should be used to achieve

consistency of the data, that determines when it can be used.

That holds transcational processing, if you do mass changes of data, it can be bit different, there it

makes sense to use the COMMIT WORK regularly, not after a few changes, but after about 10 thousand.

Also there data consistency must be a goal, but maybe it is sufficient if it is fulfilled at the end of the process, and not in every step in between.

Siegfried