This method of connecting to SAP allows you to use all SAP functionality that is incorporated around business objects through the use of BAPIs. Through SAP, you can generate the stub for either server or client code for an existing RFC. Examples of the languages that can be supported appear in Figures 16.1 and 16.2.
Figure 16.1: The first step in the creation of a stub to an RFC, showing default language choices
Figure 16.2: Programming languages supported in stub creation
This technology provides both synchronous and asynchronous communication to SAP and does not require the programmer to know anything about ABAP. By using BAPIs, you can perform entire business operations with a single function call, such as Create Sales Order.
This approach also shields you from any changes that might occur from an upgrade to the SAP system. BAPIs, by definition, have defined deprecation plans, and must be available for at least two major SAP version upgrades.
To use RFCs and BAPIs, you need more knowledge of SAP's business logic than if you used a GUI-based solution. In addition, you must still come up with a way to call the RFC. You can accomplish the call with a tool like the Orbix server or with the SAP RFC gateway, but this step still requires some setup.
You can avoid calling up the RFCs directly (even when using the DCOM connector) if you approach the SAP system from outside the corporate firewall.
Team-Fly |