topic Re: Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM in Application Development and Automation Discussions

Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM

Former Member — Mon, 08 Dec 2014 17:18:47 GMT

We need to create a BAPI/Remote enabled Function Module for creating Sales Order for integration with 3rd party application. We are using the standard BAPI BAPI_SALESORDER_CREATEFROMDAT2 for creating SO, after the successful execution BAPI_TRANSACTION_COMMIT is needed to be called for updating the database because of which we have created a wrapper remote enabled function module inside which we have called both the above BAPIs.

Now I recently read the documentation of creating BAPI where it is written COMMIT WORK should not be called inside a FM.

Please let me know what is the SAP recommended best practice in such case.

Re: Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM

paul_bakker2 — Mon, 08 Dec 2014 23:31:22 GMT

Hi,

When SAP provides BAPIs they do not put a COMMIT WORK inside them.

This is so that you can call multiple BAPIs in a row, and then COMMIT the whole lot at once.

You are free to do whatever you like in your own FM/BAPI.

cheers

Paul

Re: Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM

Former Member — Wed, 11 Feb 2015 06:04:04 GMT

Hi Paul

Thanks for the reply.

So I am assuming this is one of the best ways to go ahead for integrating SAP with other apps.

Re: Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM

paul_bakker2 — Wed, 11 Feb 2015 07:26:04 GMT

Hi,

Sure, but use standard BAPIs wherever you can!

cheers

Paul

Re: Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM

kairatalaichi — Tue, 26 Oct 2021 15:00:25 GMT

BAPI_EQMT_MODIFY is an example of SAP putting COMMIT WORK inside

Re: Commit Work in Custom BAPI | BAPI Documentation says NO COMMIT inside FM

RaymondGiuseppi — Wed, 27 Oct 2021 14:05:40 GMT

Some BAPI modules created until Release 3.1H usually executed the COMMIT, this changed in Release 4.x (6?)

For compatibility reason SAP didn't remove those COMMIT, but there is a comment in the BAPI source, look at FM IWWW_SET_NO_COMMIT of the same function group to deactivate the commit.