topic BAPI_MATERIAL_SAVEDATA & BAPI_PRICES_CONDITIONS in Application Development and Automation Discussions

BAPI_MATERIAL_SAVEDATA & BAPI_PRICES_CONDITIONS

Former Member — Mon, 31 Jul 2006 12:23:34 GMT

Hi Friends,

Iam calling these functions in one of my custom function.

As I understand that for any BAPI, we need explicit commit after we call BAPI. If not data will not change in database.

But in my case these two functions are commiting the changes sucessfully in database then and there. I don't want to happen this.

Are there any parameters, for these functions to stop updating instantly and update only when we call "bapi_transaction_commit"?.

Thanks

Message was edited by: Hariprasad Gangavarapu

Re: BAPI_MATERIAL_SAVEDATA & BAPI_PRICES_CONDITIONS

Former Member — Mon, 31 Jul 2006 12:35:42 GMT

Are you sure these are committing every record ? A BAPI should require the explicit call t othe commit function module.

How are you running the program ? How much data are you running it with?

Re: BAPI_MATERIAL_SAVEDATA & BAPI_PRICES_CONDITIONS

Former Member — Mon, 31 Jul 2006 12:43:14 GMT

Hi JJ,

I call these functions from my custom function module and every time I handle only one material save/change and few candition records for the material (This function will be called from custom Material Master). I did not have commit work in my function. Iam testing my function from SE37.

when I look in debug mode as soon as these BAPIs execute and still Iam in debug mode in my function and I found the relavent sap tables changed with my new data.