topic Re: Performance Issue with BAPI_TRANSACTION_COMMIT in Application Development and Automation Discussions

Performance Issue with BAPI_TRANSACTION_COMMIT

Former Member — Wed, 19 Sep 2007 16:35:00 GMT

Which is better performance wise?

I'm doing a mass change of final confirmation using BAPI_ALM_CONF_CREATE. I have more than 100 records for processing.

Should I do a commit work for each record processed?

LOOP AT ITAB.

CALL FUNCTION 'BAPI_ALM_CONF_CREATE'

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

ENDLOOP.

Should I do the commit work after processing all the records?

LOOP AT ITAB.

CALL FUNCTION 'BAPI_ALM_CONF_CREATE'

ENDLOOP.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Thanks in advance!

Re: Performance Issue with BAPI_TRANSACTION_COMMIT

Former Member — Wed, 19 Sep 2007 16:45:11 GMT

You might get better performance by doing it at the end, but you might also end up with inconsistent data. You should do a commit after each LUW.

(You might not get any performance improvement by putting it at the end either. The COMMIT still has to do the same amount of actual work, less some overhead.)

Rob

Re: Performance Issue with BAPI_TRANSACTION_COMMIT

JozsefSzikszai — Wed, 19 Sep 2007 16:55:03 GMT

hi JB,

I would do it for each record separately. In case of doing it in one go, could lead to problems, if the update is asynchronous. On the other hand, if one reocrd is wrong, than you loose all changes.

Re: Performance Issue with BAPI_TRANSACTION_COMMIT

Former Member — Wed, 19 Sep 2007 17:34:54 GMT

But is it ok do the COMMIT for each order or is it better to do it for each order and operation?

Re: Performance Issue with BAPI_TRANSACTION_COMMIT

Former Member — Wed, 19 Sep 2007 18:24:11 GMT

After each LUW (each BAPI call).

Rob