The Relationship between BAPIs and the BOR
BAPIs are defined as API (Application Programming Interface) methods of SAP business objects. These business objects and their BAPIs are described and stored in the BOR (see Chapter 12, 'SAP's Business Object Repository'). Currently within SAP, a BAPI is implemented as a function module that is stored and described in the Function Builder.
As of release 4.5A, BAPIs can also describe interfaces (definitions of functions) that are implemented outside the R/3 system. This type of BAPI is known as a BAPI for outbound processing. The target system is determined for the BAPI call in the distribution model of ALE (Application Link Enabling). BAPIs used for outbound processing are defined in the BOR as API methods of SAP interface types. This approach allows functions to be implemented outside the R/3 system in a standardized fashion.
To define a BAPI to an object in the BOR, the function module must be fully developed. BAPI development is accomplished using a combination of the Function Builder Tool and the Data Dictionary (as required).
One of the nice aspects about BAPIs is that if an underlying change occurs in the BAPI itself, the calling programs do not have to change the way they call the BAPI. However, SAP upgrades may require a change in the way a BAPI is called. If a released BAPI is to be replaced by a different BAPI, the new BAPI should be given a new name and the old BAPI should be marked as obsolete. Thus many SAP BAPIs end with a 2 (for example, AddItem2).
Team-Fly |
