Chapter 6

Section 6.7

Reviewing the Sample Projects

Additional Sample Project Scenarios

ƒUnmarshal - To unmarshal IDOC data to this OTD

ƒIDOC_INBOUND_ASYNCRONOUSExecute - To send IDOC to SAP

ƒIDOC_INBOUND_ASYNCRONOUSReceive - To receive IDOc from SAP

The IDOC_INBOUND_ASYNCRONOUS OTD is NOT a message-able OTD, and the unmarshal web service is specifically provided to unmarshal IDOC data to this OTD.

You should always use this unmarshal operation in conjunction with

IDOC_INBOUND_ASYNCRONOUSExecute operation. You can cannot use the unmarshal operation alone in an eInsight Business Processes.

Client Mode - sending IDOCs to SAP R/3 via

IDOC_INBOUND_ASYNCRONOUS

The following screen illustrates and example Business Process to send IDocs to SAP R/ 3.

Figure 89 Business Process

The example seen in Figure 89 shows that we receive IDoc data from a File, unmarshal it to the RFC OTD, and call the Execute web service.

Figure 90 displays the business rule between FileCleint.receive and

RFC_IDOC_INBOUND_ASYNRONOUS.unmarshal. To create this business rule:

1From the Business Rules Designer, drag a String > text to bytes to the canvas, then connect the text field under FileClient.receive.Output to text in the text to bytes conversion box, and return bytes in the text to bytes conversion box to the bytesToUnmarshal field under RFC_IDOC_INBOUND_ASYNCHRONOUS.unmrshal.input.

eWay™ Adapter for SAP BAPI User’s Guide

117

Sun Microsystems, Inc.

Page 117
Image 117
Sun Microsystems SAP BAPI manual Client Mode sending IDOCs to SAP R/3 via, Idocinboundasyncronous