Prerequisite Setup 

Although you send or receive XML documents when using the IDoc Connector for XML component, you are actually sending or receiving IDocs to or from an R/3 system.

Therefore both the R/3 system and the external system using the IDoc Connector for XML component must be set up to send or receive IDocs.

ALE/IDoc Setup on the R/3 System

To allow the R/3 system to either send or receive IDocs, your administrator must set up the R/3 system with the appropriate ALE infrastructure and IDoc settings.

This ALE/IDoc setup involves many tasks, including (but not limited to) setting up an RFC destination, setting up a port for communication, and defining partner profiles. Port number and partner information, for example, are included in the header of the IDocs that you either send or receive.

The complete list of ALE/IDoc setup tasks and their details are outside the scope of this document. For More details, see the following documentation:

ALE/IDoc Setup for the IDoc Connector for XML Component

Note the following selections your administrator should make when setting up the ALE/IDoc infrastructure to work with the IDoc Connector for XML component:

Defining a Port (Inbound and Outbound IDocs)

When defining a Port (Transaction WE21) for communicating with the IDoc Connector for XML component, your administrator should define it as a Transactional RFC (tRFC) port type.

Defining an RFC Destination for Outbound IDocs

When using outbound IDocs, the IDoc Connector for XML acts as the server for RFC Function calls from the R/3 system.

Therefore, for using outbound IDocs with the component your administrator should define an RFC Destination (Transaction SM59) to point to the IDoc Connector for XML component.

This RFC Destination should use Connection type TTCP/IP connection.

External System Setup for Outbound IDocs

The other side of preparing the IDoc Connector for XML to act as an RFC server is to set up the following on the system on which the IDoc Connector for XML component is installed:

The TYPE field should be R.

The GWHOST and GWSERV fields should point to the sending R/3 system.

The DEST field should be the name of the RFC Destination as it was defined in Transaction SM59 on the R/3 system.

The PROGID field should be the Program ID entered in Transaction SM59 on the R/3 system.