Chapter 1 | Section 1.2 |
Introducing the SAP BAPI eWay | About the SAP BAPI eWay |
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
Business Process |
| BAPI |
| BAPI eWay |
|
| CostCenter |
| (JCo server) |
|
| OTD |
|
|
SAP R/3 System
Time
Populate OTD
GetListReceive
GetListReply
Call RFM
Call RFM
Return
exception
The figure above shows the following steps for the inbound data flow via RFC:
1The Business Process is activated when an RFM call is received from SAP R/3.
2Finding 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.
3The 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.
eWay™ Adapter for SAP BAPI User’s Guide | 10 | Sun Microsystems, Inc. |