IDoc Adapter (SAP Library - SAP Exchange Infrastructure (BC-XI))

IDoc Adapter

Definition

The IDoc adapter enables you to process IDocs (Intermediate Documents) using the Integration Engine. IDocs are supported from SAP systems Release 3.1x or higher.

The IDoc adapter is used by SAP components to connect to a centrally configured Integration Engine using IDocs. A system that has an Integration Engine of this type is referred to as the Integration Server. External systems can also use the IDoc adapter to connect to an Integration Server.

Use

You require the IDoc adapter to connect SAP components (or external systems) to the Integration Server using IDoc communication.

You need the IDoc adapter if you want to use the Integration Server to process IDocs. The IDoc adapter converts the IDocs to IDoc XML format so that they can be processed by the Integration server pipeline.

It is also possible to transfer XML received by the Integration Server in IDoc format to connected systems. The Integration Server must convert the received XML to IDoc XML, and then transfer this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the receiver system identified in technical routing using the standard IDoc interface. The IDoc adapter can also call external subsystems.

Structure

Essentially, the IDoc adapter comprises two parts, namely an inbound adapter at the Integration Server inbound channel, and an outbound adapter at the Integration Server outbound channel. The meta data for the IDoc types involved is shared.

The inbound adapter converts an IDoc to IDoc XML, starts the Integration Server and then transfers the IDoc XML message.

The outbound adapter converts IDoc XML to IDoc format and transfers the IDoc to an SAP component or an external system (subsystem).

Note

If none of the pipeline services require the IDoc XML, then you can set a corresponding configuration parameter so that IDocs are not converted to IDoc XML, but are transported as tables instead. This only makes sense if IDocs are to be received on the Integration Server without changes to the data records and sent again as IDocs. By avoiding unnecessary conversions from and to XML can lead to improvements in system performance.

You also have transactions to do the following:

Maintain ports in the IDoc adapter (IDX1)

Load, display and delete meta data (IDX2)

Display IDoc XML messages (IDX5)

The authorizations for the individual transactions are all based on the authorization object S_XMB_AUTH or S_XMB_DSP. Individual authorizations for transactions must be granted as follows using the corresponding roles:

IDX1 (role SAP_XI_ADMINISTRATOR) and IDX2 (role SAP_XI_CONFIGURATOR)

Activity

01 (create)
02 (change)
03 (display)
06 (delete)

Operation

Not defined

IDX5 (role SAP_XI_MONITOR)

Activity

03 (display)

Operation

Not defined

You cannot execute transactions in the menu that have the locked symbol (), because you do not have the required authorization.

Integration

The IDoc adapter is part of an Integration Server. The inbound IDoc adapter is located before the Integration Server pipeline and calls this pipeline. Whereas the outbound IDoc adapter is called by the pipeline; it can be regarded as a pipeline service and is therefore part of the pipeline itself.

The connected systems transfer IDocs to standard IDoc tRFC outbound processing or receive IDocs from standard IDoc tRFC inbound processing.

This graphic is explained in the accompanying text

Only use the IDoc adapter to integrate SAP components with the Integration Server, if a scenario of this kind suits your requirements. For example, if you want to make IDoc data in the form of XML messages available to additional receivers, or if you want to integrate different components or business processes, which were previously not integrated. Only stop using existing functioning IDoc scenarios after serious consideration.