You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures.
An IDoc-based communication using the Integration Server works as follows:
· The IDoc control record contains information, for example, the logical system name (LS), port definitions, business partner information, partner role information, and more ALE-specific parameters. This IDoc control record information is used to build SOAP message header information for the Integration Server in the IDoc adapter. The configuration in the Integration Directory allows the creation of the message header from an IDoc control header on the Integration Server inbound side. It is also used on the Integration Server outbound side to create an IDoc control header.
· The original IDoc control record is available in the payload of the XI message, which means that it is not modified by the IDoc adapter.
· The tasks of the IDoc adapter are:
Ў To create an IDoc-XML message out of an RFC call on the inbound side.
The metadata of the IDoc structure is used for this purpose. This metadata is retrieved from the DDIC of the sender and receiver systems.
When you load metadata from a sender or receiver system, ensure that all required IDoc types and IDoc segments have been released (this can be checked with transaction IDoc Type Development (WE30) in the corresponding system).
Ў To create an RFC call out of an IDoc-XML message on the outbound side.
Ў To create message header information by mapping ALE logical system names to business system names stored in the Integration Directory and (optionally) defined in the System Landscape Directory.
Ў To create an IDoc control record out of an XI message on the outbound side.
Transaction SAP Adapter – Monitoring (IDX5) provides you with an overview of all messages sent to or from the Integration Server as IDocs. Double-clicking a message provides you with detailed information on this message in the Integration Server.
You can monitor the status of all XML messages by using transaction Integration Engine – Monitoring (SXMB_MONI).
You can use transaction SM58 to monitor native RFC communication on the Integration Server. This type of communication protocol is used in two places here:
· To send an IDoc from an SAP system to the Integration Server
· To send an IDoc from the Integration Server to an SAP system