Technical description of the interface

In the current release 4.02 the interface between SAP Banking BCA and delivery channel products is based on the Remote Function Call (RFC). From a technical point of view, RFC is a library (in the C programming language) which is available on nearly all operating system  platforms.

How it works.

RFC is a general concept, allowing communication between R/3 Systems or between an R/3 System and external programs. In the case of an external system management tool we are dealing with an example of the latter, in which the program adopts the role of a client in relation to the R/3 System. The service offered by the application server involves the delivery of internal system information or carrying out individual system management activities. RFC works in sessions. In other words, the user opens an RFC, carries out RFC tasks and then concludes the session. In opening the session, the R/3 logon procedure, with user ID and password, must be carried out. The user must be identifiable to and authorized by the R/3 System. In other words, users must exist within the R/3 System, which are then used by the external agent. Obviously, you need to set up authorizations for these users which correspond with the activities that they are to carry out.

RFC recognizes synchronous, asynchronous and transactional calls. The following examples use synchronous calls. For further details on the other types of call, see the appropriate RFC documentation.

SAP Business Framework (future SAP Banking release)

In a future release the interface between SAP Banking BCA and delivery channels products will be is based on the SAP Business Framework. Banking specific Business Objects will be defined in the SAP BOR (Business Object Repository).

Examples for Business Objects:

1. Business Partner (i.e. customer data)
2. Account
3. Payment item
4. Payment order
5. Check
6. Standing order

Methods define the access from external systems to the SAP Banking Business Objects. A method for a Business Object in the SAP Business Object Repository is called 'BAPI' (Business Application Programming Interfaces).

Examples for BAPI's in SAP Banking:

- Get account master data details
- Get account balance
- Create payment item
- Create Standing order

The SAP Business Framework is an open platform for the integration of external systems. Object-oriented access technologies like CORBA or COM/DCOM are supported. The BAPI's can also be called by any external system which can handle Remote Function Calls (RFC) of SAP function modules. For technical details of the SAP Business Framework we refer to the SAP basis training or the standard R/3 documentation.

In the current SAP Banking release 4.02 there are no real BAPIs in SAP Banking BCA:

Currently SAP Function Modules can be accessed via RFC (Remote Function Call). Technically BAPI's and function modules are equivalent, the main difference is that BAPIs are defined as stable and available for a longer term. BAPIs are planned for the next major SAP Banking release which will be shipped in May 2000. It will be based on the SAP R/3-Release 4.6.

Reference:
http://www.sap.com/turkey/partners/icc/scenarios/pdf/isb_dch_402.pdf