2 the sap bapi eway data flows, Outbound data flow: java caps to sap r/3, Inbound data flow: sap r/3 to java caps – Sun Microsystems eWay SAP BAPI User Manual
Page 9: The sap bapi eway data flows
Chapter 1
Section 1.2
Introducing the SAP BAPI eWay
About the SAP BAPI eWay
eWay™ Adapter for SAP BAPI User’s Guide
9
Sun Microsystems, Inc.
The meta data for a BAPI/RFC in SAP R/3 is extracted by the BAPI wizard, which uses
it to build the BAPI/RFC OTD. This OTD is used in Java Collaborations and eInsight
Business Processes to invoke or receive the BAPI/RFC call.
1.2.2
The SAP BAPI eWay Data Flows
When the SAP BAPI eWay communicates with the SAP R/3 software, it uses the RFC
protocol. The list below shows the RFC types of communication used:
Outbound (Java CAPS to SAP R/3): non-transactional (regular) RFC and
transactional RFC (tRFC)
Inbound (SAP R/3 to Java CAPS): non-transactional and transactional RFC (tRFC)
Outbound Data Flow: Java CAPS to SAP R/3
Outbound communications occur when the eWay receives data from Java CAPS and
sends it to SAP R/3 by calling a specific BAPI or RFM. The figure below shows a non-
transactional outbound process.
Figure 3 Outbound Data Flow: Java CAPS to SAP R/3
The figure above shows the following steps for the outbound data flow:
1
The Collaboration or Business Process populates the appropriate BAPI or RFC
Import, Changing,
and Table parameter nodes on the BAPI/RFC OTD with data
from an inbound OTD.
2
The eWay logs onto the SAP R/3 application using preconfigured properties.
3
The eWay calls the BAPI OTD's execute() method. Any work performed is
immediately committed by SAP R/3 through autocommit.
4
The SAP R/3 applications returns successfully.
Inbound Data Flow: SAP R/3 to Java CAPS
For the inbound data flow, the SAP BAPI eWay can receive data from SAP R/3 via RFC
or tRFC. The sections below describe each protocol.
To enable the SAP BAPI eWay to receive data from SAP R/3, configure the
Environment properties with an RFC destination created within SAP R/3. For
information, refer to
“Creating the RFC Destination for the eWay” on page 48
.
Collaboration
Business Process
SAP R/3
System
BAPI
OTD
BAPI
eWay
execute()
execute()
Call RFM
Return
Time
Call RFM