topic Re: BAPI IN ABAP in Application Development and Automation Discussions

One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.

Some of the BAPIs are better documented and easier to use than others.

You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.

The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.

You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.

BAPIs probably have better performance since they don't do the screen flow processing.

In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.

This is just from my experience working with both BAPI and Call Transaction. I have had some very good successes with BAPIs, but very occasionally found that I could not get the BAPI to perform the update I needed.

Refer the transaction BAPI for detail information.

You can also refer to below links:

http://www.sapgenie.com/abap/bapi/example.htm

Basic learning guide:

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

BAPI intro:

http://www.sappoint.com/abap/bapiintro.pdf

Overview:

http://www.planetsap.com/Bapi_main_page.htm

Also have a look at the following link :

http://www.planetsap.com/LIST_ALL_BAPIs.htm

Regards

Anver