The IDoc Gateway is designed for asynchronous document exchange. From a technical view, SAG's RPC and SAP's RFC protocol stacks are reused. Therefore, the IDLs of Rpc2Rfc and Rfc2Rpc have several additional functions.
Note:
The IDLs of version 2.2.1 already contain these functions.
| Function | Used in |
|---|---|
| IDOC_INBOUND_ASYNCHRONOUS | Rpc2Rfc uses this function to create an inbound IDoc in SAP R/3 |
| IDOC_INBOUND_ASYNCHRONOUS | The Rfc2Rpc receives outbound IDocs delivered from SAP R/3. |
| IDOCTYPE_READ_COMPLETE | The function Rpc2Rfc returns type information about the structure of an IDoc |
The IDoc XML Gateway provides functionality for sending and receiving IDocs asynchronously and for making the type information available to your business application. Your business application receives an interface for IDocs, which is generated from the type information.
The IDoc XML Gateway uses XML to represent the IDoc. Therefore, several XSL(T) transformations are available. The IDoc XML Gateway concatenates the transformation steps to a pipeline concept.
For the technical transformation of IDocs the webMethods EntireX Broker's Concept of Persistent Messaging is used. The basic concept is
use of Units Of Work (UOW) for each IDoc and
guarantee delivery in a transactional way.
The pipeline concept offers business views and hides the underlaying technical system.
