Test Your BAPIs for Safe Data Transfer to the FI/CO Interface
- by Kiran Bapat, FI, SEM-BCS, EC-CS Consultant
- February 15, 2007
Before running a Business Application Programming Interface (BAPI) in your programs, you should test it. See how to test your BAPI and how to get a report that shows you its details.
A Business Application Programming Interface (BAPI) is a standard interface that facilitates the integration of R/3 or mySAP ERP Central Component (ECC) with the processes and data of other business application systems. BAPIs are the standard SAP interfaces, playing an important role in the technical integration and exchange of business data between SAP and non-SAP components. They are an important part of developing integration scenarios where you connect multiple components to each other, either on a local network or on the Internet. You can implement and store BAPIs in R/3 or ECC as Remote Function Call modules.
Customers and third parties use Business Application Programming Interfaces (BAPIs) as the standard SAP business objects for integrating their software components with the SAP system. Once you implement a BAPI, its interface definition and parameters remain stable in the long term, which in turn stabilizes your application programs. The performance of BAPIs is also higher compared to the batch data creation (BDC) process many companies implement.
Let me discuss two ways that functional consultants commonly use BAPIs and give an example of how they identify and test them. Testing BAPIs aids in the technical development process. Normally technical consultants with ABAP expertise use BAPIs, but functional consultants should know how to test BAPIs to retrieve the output before the technical consultants use them in a program.
Take the example of transaction MIRO, posting for vendor invoice verification. In many cases, you have to change the standard invoice verification process, such as changing the price of the material if the price of the material that the finance department processed differs from the price that the PO originally listed. This is not available in standard SAP — you have to create a custom program to post the invoice. In this case, you can use the BAPI CREATE_VENDOR_INVOICE to post the MIRO transaction. BAPIs can drastically cut the time it takes to post an invoice because of the numerous line items you have to use with BDC.
Would you like to see this full item?