Sun Microsystems eWay SAP BAPI - Manual (Page 10)

Chapter 1 Section 1.2
Introducing the SAP BAPI eWay About the SAP BAPI eWay
eWay™ Adapter for SAP BAPI User’s Guide 10 Sun Microsystems, Inc.
Inbound Data Flow via RFC
The sequence diagram uses a sample CostCenter OTD to describe the RFC inbound
sequence.
Figure 4 Inbound Data Flow via RFC
The figure above shows the following steps for the inbound data flow via RFC:
1 The Business Process is activated when an RFM call is received from SAP R/3.
2 Finding that data from an RFM is available, the Business Process accesses all
pertinent data nodes and sends the gathered information to other Java CAPS
components.
3 The eWay returns the results of the RFM execution back to SAP.
Inbound Data Flow via tRFC
Communication via tRFC is the similar to RFC, except that it adds transactional
verification steps prior to committing or rolling back. tRFC is preferred over RFC
because of the additional reliability. By using unique TIDs associated with a BAPI/
RFM call, SAP R/3 processes the data once, and only once. The figure below shows
inbound data flow via tRFC.
Business Process SAP R/3
System
BAPI
CostCenter
OTD
Call RFM
BAPI eWay
(JCo server)
GetListReceive
exception
Populate OTD
GetListReply
Call RFM
Return
Time