Business Application Programming
BAPIs (Business Application Programming Interfaces) are open,
business orientated interfaces for accessing R/3 business processes
and data from external systems. In the Business Object Repository
BAPIs are defined as methods of SAP Business Objects. They provide
an object orientated view of R/3 application modules.
New developments in the area of BAPIs in Release 4.0A
Integration of BAPIs into Application Link Enabling (ALE)
In Release 4.0A BAPIs can also be used for asynchronous data
transfer within the context of ALE (Application Link Enabling). For
further information see the ALE Release Notes.
Enhancement of the development environment in the R/3
The development environment for BAPIs has been enhanced in Release
You can access all SAP Business Objects and their BAPIs in the
BAPI Browser and integrate them into your
application programs. All Business Objects for which BAPIs have
been implemented are clearly displayed in the R/3 application
hierarchy in the BAPI Browser. The interface information required
for calling BAPIs and documentation are also provided.
The Business Object Builder is provided for
developing BAPIs. In the Business Object Builder you can, for
Implement a BAPI as a method of a Business Object using the
Test a BAPI in the test environment.
Modify the status of a BAPI within the framework of the release
procedure. Possible status values are: modelled, implemented,
released or expired.
Other functions are also provided,
for example, for ALE integration.
The section below "Changes to the
Interface" describes how to access these functions.
BAPI C++ Class Library
In Release 4.0A a BAPI C++ Class Library for Windows NT and Windows
95 is provided enabling object orientated access to BAPIs from
external systems. In the BAPI C++ Class Library every SAP Business
Object for which BAPIs have been implemented has a proxy class and
every BAPI has an associated function. The native data and
structures in C++ can be used for calling BAPIs in place of SAP
internal data types and structures.
A dynamic proxy class allows access to those new Business Objects
and BAPIs, for which there is not yet a static proxy class in the
BAPI C++ Class Library.
Application programs that use the BAPI C++ Class Library must be
compiled with Microsoft Visual C++ 5.0 and should use the standard
C++ library (not iostream or <string.h>).
In Release 3.1 more than 150 BAPIs were provided. In Release 4.0A
the number of BAPIs has grown to over 360. These are listed below.
You can access any released BAPI in the BAPI Browser.