BAPI_MATERIAL_SAVEDATA

[Former Member]

Hello Experts,

As adviced by SAP itself that you should use BAPI_TRANSACTION_COMMIT

after execution of every BAPI .

Our client is using BAPI_MATERIAL_SAVEDATA to create a material from a NON-SAP backgroud(say middleware)

as we have observed that there is no need to use BAPI_TRANSACTION_COMMIT

to create a material as without executing Commit we can create a material.but as suggested by SAP

they ary using BAPI_TRANSACTION_COMMIT after BAPI_MATERIAL_SAVEDATA .

so now they want to know that if we want to minimise calls to SAP so will it create any further problem in future if we dont use BAPI_TRANSACTION_COMMIT everytime......

well expecting a dinite answer from u experts rather than may me type of answer.

i will be really helpful to u people.

thnks in advance.

[Former Member]

Hi..

It is Not Mandatory that Every time you have to call Bapi_transaction_commit.But Some Bapi's Does't have Commit Eg:PO and some Bapi's . we have to call commit.so thats SAP saying that if u have make commit for every bapi it should be good.

Madhu.

[Former Member]

Hi Abhijeet,

Some BAPI will change some data in SAP table, but the change won't be effective, untill you call BAPI_TRANSACTION_COMMIT. And if you call BAPI_TRANSACTION_ROLLBACK, the change will be ineffective.

Check the Function module documentation itself.

This method executes a COMMIT WORK command. It is required for transactions developed outside the SAP system that change data in the SAP system by using BAPI calls.

When you call BAPIs in your program that change data in the SAP system, you must then call this method to write the changes to the database.

So, always prefered to use.

Sachin