The Following approach is suggested by the ABAP team:

RFC: An approach under the classic model is a remote function call. RFC interface is
used to set up the communication between SAP and non-SAP, also between two SAP
systems. It runs on the concept of Client and Server. The client seeks for a function to
perform and makes a call to the RFC server. The function is executed at the remote
system on the server-side, and it can be synchronous. 

Under the RFC interface concept, SAP came up with BAPI (Business Application Pro-
gramming Interface). The idea was to expose the business objects (BO) to the exter-
nal systems. So, a java-based system can access the instance of the exposed business
object (Customer, Orders, Employee, etc.) through exclusive methods provided by
the BO. An RFC connection is created in SM59 for setting the connection between SAP
and Non-SAP systems.

RFC Interface

The Approach:

Data Push from SAP to Non-SAP System:

- New RFC FM (Remote Function Call Function Module) will be developed and called
to transfer data from SAP to any external application.
- To transfer Data from SAP, external RFC connection is to be created by Basis
team of the client.
- External System will receive data sent by SAP and will be stored in the application.

Data Push from Non-SAP to SAP:

- New RFC FM will be developed and this RFC will be called from the external system
to transfer data to SAP.
- Here also the client's responsibility is to create RFC connection.
- External system will call the given RFC function and SAP will receive data from Non-
SAP system.
 
Configuring programs to run in the background

We can configure the generated ABAP program to be run as a background process

by the SAP system. When the ABAP program is configured for background process-
ing, additional features specific to SAP such as logging, and status reporting are en-
abled. We can also use the SAP transaction SM37 to monitor the background jobs.
The job name is same as the name of the generated ABAP program.