Version 2.3.1.18
 —  SAP R/3 Gateway Documentation  —

Integration Scenarios


Custom Application calls SAP Function

This synchronous integration scenario makes it possible to call an SAP R/3 business function from your mission-critical application.

integration scenario 1

The SAP R/3 business function is implemented as a remotely enabled ABAP function. You can call a standard BAPI or your own implemented RFC function. In either case, the development kit in this scenario supports the generation process to retrieve the business interface for your mission-critical application. See the section Develop a Client Call to SAP/R3 (Rpc2Rfc Kernel).

Top of page

SAP calls Custom Application Server

This scenario makes it possible to call your existing functions from SAP R/3. This synchronous method reuses the business interfaces, for example, if you already have complex evaluation algorithms implemented that should send calls from your own SAP R/3 application.

integration scenario 2

Use the development kit to implement this type of integration. See the section Develop an SAP Call to an External Application (Rfc2Rpc Kernel).

Top of page

Custom Application sends IDoc

SAP R/3 delivers several document types for asynchronous exchange.

integration scenario 3

This scenario supports the updating of mass data in SAP R/3. The IDoc XML Gateway helps you to implement the interface provided by IDoc to your business application.

Top of page

SAP delivers IDoc to Customer Application

To notify your business application of a change to mass data, your application can receive IDoc documents. The business application will be notified by a subprogram call and receives the data with your business interface.

integration scenario 4

The IDoc XML Gateway helps you to implement this scenario.

Top of page