SAP Automation RFC and BAPI Interfaces 

The following tables list the SAP Automation tools, components, and libraries that use the RFC interfaces. The tables describe the function of these products and lists the programming language(s) with which you can use each of them.

Use the links from these tables to access the detailed documentation of the various products.

Underlying Library

Tool

Type

Function

Language(s)

RFC API

C API

A set of C routines that allows you to write external applications that communicate with an SAP system through remote function calls (RFCs).

The external application can act as either a client or a server to the SAP system.

C

SAP Automation RFC-based Class Libraries

Tool

Type

Function

Language(s)

RFC C++ Class Library

Class library

Provides a framework for the RFC API.

Makes it easier to use RFCs in C++ programs by providing pre-built functions for some common tasks, such as establishing a connection to R/3.

C++

Java RFC Class Library

Class library

Provides an object oriented Java view over the RFC API.

Makes it easier to use RFCs in Java programs by providing pre-built functions for some common tasks, such as establishing a connection to R/3, or performing data type conversion.

Java

IDoc C++ Class Library

Class library

Provides a framework for processing inbound and outbound IDocs.

Makes it easier to use IDoc technology in C++ programs by providing pre-built functions for some common tasks, such as creating and appending IDoc segments, accessing segments and fields by names, and working with fields.

C++

ActiveX Controls and Components

Tool

Type

Function

Language(s)

Logon Control

(Documented with the SAP Automation RFC and BAPI Interfaces)

ActiveX Control (OCX)

Allows you to create a connection object with which you can establish a connection to R/3.

Note that for programs using the SAP DCOM Connector, we recommend that you use the DCOM Connector Logon Component instead of the Logon Control.

Any COM-compliant application

Function Control (Documented with the SAP Automation RFC and BAPI Interfaces)

COM Server

Provides COM objects for handling RFC functions and their parameters. This allows you to create external applications that call RFC function modules in an SAP system.

Any COM-compliant application

Table Control (Also called Table Factory Control. Documented with the SAP Automation RFC and BAPI Interfaces)

COM Server

Allows you to create a Table object representing a table parameter of an RFC function.

Works with the Function control to manage tables attached to Function objects.

Any COM-compliant application

Transaction Component

(Also called Transaction Control, which is documented with the SAP Automation RFC and BAPI Interfaces)

COM Server

Exposes R/3 batch input capability to COM-compliant programs and applications.

Allows an external program to send input field values to an R/3 screen (output field values are not returned).

Makes using batch input easier by eliminating the need to populate the fields of the BDC table, which is a prerequisite to using the standard R/3 batch input method.

Any COM-compliant application

BAPI ActiveX Control

ActiveX Control (OCX)

Allows you to develop external client/server applications (with R/3 as a server) that access business functions in the SAP system by calling BAPIs (Business APIs) through OLE Automation.

Achieves this by allowing you to create (on the client) local instances of business objects, which act as proxy objects for the business object in the SAP system.

Any COM-compliant application

DCOM Connector-based Components and Tools

Tool

Type

Function

Language(s)

IDoc Connector for XML

COM Server

Provides an XML interface for working with IDoc documents.

The IDoc Connector for XML component accepts your XML documents and sends them as inbound IDocs to a specified R/3 system. Conversely, it can receive outbound IDocs and it translate them into XML documents for your application to use.

Any COM/DCOM-compliant application

DCOM Connector Logon Component

COM Server

Helps programs that use the SAP DCOM Connector handle the connection parameters of the COM objects created by the SAP DCOM Connector.

The DCOM Connector Logon Component provides a logon dialog with which you can get the necessary connection parameters from an end user. It also allows the end user to create and maintain destination definitions.

The DCOM Connector Logon Component also allows you to easily copy connection parameters into a DCOM Connector COM object.

Any COM/DCOM-compliant application

Repository Services

COM Server

Provides read access to the metadata of business objects, RFC function modules, tables and structures in an R/3 system to COM-compliant programs and applications.

Also allows you to save a copy of the metadata in a local database. Using a local database allows you to access the same metadata faster and without connecting to R/3.

Any COM/DCOM-compliant application

BAPI Gateway

COM Server

Allows you to dynamically call BAPIs and RFCs through the DCOM Connector, that is, it allows you to determine at run time which BAPIs or RFCs you call.

Eliminates the need to use the SAP DCOM Connector wizard for creating a DCOM Connector proxy component.

You can use the SAP Automation Repository Services component in conjunction with the BAPI Gateway to obtain the metadata for the BAPIs or RFCs you wish to call at run time.

Any COM/DCOM-compliant application

Repository Browser

(Also called the SAP Browser Control, which is documented with the SAP Automation RFC and BAPI Interfaces)

ActiveX Control (OCX)

A control that can be hosted by any ActiveX container. It consists of a window with two panes for browsing SAP BAPI and RFC metadata information.

Allows online calling of RFC functions from within the control.

Also exposes several methods to enable the container application to control and automate metadata browsing.

Allows you to export metadata information to an Excel spreadsheet.

Any COM/DCOM-compliant application

SAP Assistant

(documented with the SAP Automation RFC and BAPI Interfaces)

Stand-alone executable

A tool for browsing (viewing and searching) the metadata of SAP RFC functions and SAP business objects and their methods (BAPIs). Uses the SAP Browser Control (see above).

Allows you to call RFC functions directly online.

Also allows you to generate either Java or C++ classes for working with SAP business objects and their BAPIs.

You can use the code generated with the BAPI Wizard tool for Java or C++ programming.

The SAP Assistant window itself is not programmable.