Sun Microsystems eWay SAP BAPI - Manual (Page 11)

Chapter 1 Section 1.3
Introducing the SAP BAPI eWay What’s New in This Release
eWay™ Adapter for SAP BAPI User’s Guide 11 Sun Microsystems, Inc.
Figure 5 Inbound Data Flow via tRFC
The figure above shows the following steps for the inbound data flow via tRFC:
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 R/3.
4 If the RFM call returned successfully without exceptions, SAP R/3 informs the
eWay that the data can be committed by calling onCommitTID().
5 The eWay updates the TID in the file database as being Committed, commits the
data, and sends an onCommitTID() return to SAP R/3.
6 If the RFM call did not return successfully for any reason, SAP R/3 informs the
eWay that the data must be rolled back by calling onRollbackTID().
7 The eWay sends an onRollbackTID() return to SAP R/3, confirming that the TID
was not committed.
1.3
What’s New in This Release
The SAP BAPI eWay includes the following new features:
What’s New in Version 5.1.3
ƒ Added support: Supports automatic deployment of EAR files to WebLogic
Application Server (version 9.1).
Business
Process
SAP R/3
System
BAPI
CostCenter
OTD
Call RFM
BAPI
eWay
(JCo server)
GetListReceive
onCommitTID()
exception
Populate OTD
GetListReply
Call RFM
Return
onCommitTID()
Return
onRollbackTID()
onRollbackTID()
Return
Rollback
Sequence
Commit
Sequence
OR
Time