# of commits using BAPI_TRANSACTION_COMMIT in integration?

[Former Member]

Hi all,

my question is how many times can use BAPI_TRANSACTION_COMMIT BAPI for commiting data in SAP Standard tables? curently I am calling BAPI_TRANSACTION_COMMIT for every BP created in CRM. Ours is integration from legacy to CRM, and this job runs daily. Can we bundle 5000 or 6000 BP's created or processed successfully and then call BAPI_TRANSACTION_COMMIT bapi? what is the SAP recomendation for using this? I tried to see some documenation on this, unable to get any document which describes this.

Thanks for the help in advance.

Regards,

Srinivas

[gaursri]

Hi Srinivas,

BAPI_TRANSACTION_COMMIT is nothing but a saving device for the used BAPi in the transaction.So i have never heard of limits.Yes of course i heard many BAPi which needs to call commit work rather then BAPI_TRANSACTION_COMMIT .It may be possible if there is a limitation in any BAPI then the number may play his part.But uptill now i have never heard that BAPI_TRANSACTION_COMMIT has limitations.

Hope your query resolves quickly.

have a best day ahead.

[Former Member]

Hi Srivastava,

Thanks for the quick reply. We need to call BAPI_TRANSACTION_COMMIT when we finish one LUW or transaction so that the data gets commited in database. if any error then you can rollback using BAPI_TRANSACTION_ROLLBACK. So my question here is if you start commiting for every single record then what if the import on system performance? is it going to be impacted or is it ok? If you take other languages like PL/SQL and any batch integrations suggested way of using commit is for every 5000 or 10000 record we need to commit.

Hope I have given enough info on this?

Regards,

Srinivas

[gaursri]

Hi,

Well i have uploaded thousands of data using Bapi and i never used rollback in that rather i gave condition in which if the entry is true then BAPI_TRANSACTION_COMMITyou can catch the error using bapiret2 table.as per performance BAPi is consider to be good for mass data transfer in some scenario we might preffer another options like BDC and all.You can check the runtime analysis to get the picture of performance.

Hope you query resolves soon.

Have a best day ahead.

[Former Member]

Hi Srivastava,

Thanks for the quick reply. We need to call BAPI_TRANSACTION_COMMIT when we finish one LUW or transaction so that the data gets commited in database. if any error then you can rollback using BAPI_TRANSACTION_ROLLBACK. So my question here is if you start commiting for every single record then what if the import on system performance? is it going to be impacted or is it ok? If you take other languages like PL/SQL and any batch integrations suggested way of using commit is for every 5000 or 10000 record we need to commit.

Hope I have given enough info on this?

Regards,

Srinivas