topic Re: Does it needs COMMIT WORK explicitly every time? in Application Development and Automation Discussions

Does it needs COMMIT WORK explicitly every time?

former_member202077 — Wed, 13 Jun 2012 12:20:15 GMT

Hello

Does ABAPers need to put/use COMMIT WORK statement after each and every DB statement if the data base is DB2?

As far i knew, in Oracle we use COMMITM WORK only when we do a INSERT/UPDATE/MODIFY/DELETE to Oracle DB.

But, for DB2 we need to use COMMIT WORK after each and every SELECT SQL? like other data base associated staements?

Thank you

Moderator message: please find and study available information/documentation on SAP LUW concept.

Message was edited by: Thomas Zloch

Re: Does it needs COMMIT WORK explicitly every time?

Former Member — Wed, 13 Jun 2012 12:35:34 GMT

As far as I know, COMMIT does not depend on the underlying database. COMMIT is part of SAP Transaction concept.

http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4b6a79e11d1950f0000e82de14a/content.htm

The Native SQL drivers in SAP takes care of writing the data to the database.

So what ever native SQL operations that must be performed for each DB will be performed by SAP Sql drivers and you just have to worry about the OPEN SQL commands.

Thanks,

Shambu