7 additional sample project scenarios, 1 about sending idocs to sap r/3 using trfcs, The rfc otd used to send/receive idocs – Sun Microsystems eWay SAP BAPI User Manual
Page 116: Additional sample project scenarios, About sending idocs to sap r/3 using trfcs
Chapter 6
Section 6.7
Reviewing the Sample Projects
Additional Sample Project Scenarios
eWay™ Adapter for SAP BAPI User’s Guide
116
Sun Microsystems, Inc.
6.7
Additional Sample Project Scenarios
The following section describes an additional scenario involving Transactional Remote
Function Calls (tRFCs)
6.7.1
About Sending IDocs to SAP R/3 Using tRFCs
This section describes the procedure to send IDocs to SAP R/3 using the
IDOC_INBOUND_ASYNCHRONOUS RFC OTD and the BAPI eWay.
The RFC OTD used to send/receive IDOCs
The figure below shows the RFC OTD, IDOC_INBOUND_ASYNCRONOUS created
via the SAP BAPI OTD Wizard.
Figure 88 RFC OTD
In the OTD Editor you can see that this OTD has marshal, unmarshal methods, as well
as an executeAsyncronous method which takes a string EID (event ID) as a parameter.
Sending or receiving IDOCs to or from SAP is an asynchronous operation. This OTD
uses the executeAsyncronous method to send IDOCs in a Java Collaboration.
In the Project explorer, as seen in Figure 88, you see the following web service methods
on the OTD:
Web Service Methods
OTD Methods