Comparison of IDoc Adapter (IE) and IDoc Adapter (AAE)
SAP NetWeaver Process Integration (SAP NetWeaver PI) provides different runtime engines to process XML messages and to provide connectivity between components, partners and systems that are based on different technical protocols and standards: the Integration Engine (based on AS ABAP) and the Advanced Adapter Engine (based on AS Java). Both engines provide a - slightly - different set of adapters for connectivity.
More information: Installation and Connectivity Options
Which runtime engine you can use depends on the chosen installation option. For example, when you have installed SAP NetWeaver PI as standard dual-stack version, you can use both the Integration Engine and the Advanced Adapter Engine.
Whereas, when you use the Advanced Adapter Engine Extended (AEX), you can only use the Advanced Adapter Engine as runtime engine.
Using AEX has many advantages compared to a standard dual-stack installation of SAP NetWeaver PI. However, the decision to use a particular installation option depends also on the set of adapters you need for connectivity. In order to promote the usage of the AEX, the widely used IDoc adapter, which in former releases only runs on the Integration Engine, has also been developed as part of the Advanced Adapter Engine. Therefore, also customers who install AEX can also use the IDoc adapter.
The IDoc adapter version that runs only on the Integration Engine (based on AS ABAP) is called IDoc adapter (IE) (technical adapter type in Integration Directory IDOC_IE).
More information: Configuring the IDoc Adapter (Integration Engine)
The IDoc adapter version that runs on the Advanced Adapter Engine (based on AS Java) is called IDoc adapter (AAE) (technical adapter type in Integration Directory IDOC_AAE).
More information: Configuring the IDoc Adapter (Advanced Adapter Engine)
Note that, however, IDoc adapter (AAE) has some limitations as compared to IDoc adapter (IE). The following table lists which features are supported in each case, and serves as a basis to decide on which adapter version to go for:
Availability and Tool Integration
|
Attribute/Feature |
IDoc Adapter (IE) |
IDoc Adapter (AAE) |
|
Available in SAP NetWeaver (PI) Release |
SAP NetWeaver XI 3.0 SAP NetWeaver 7.0 (including EHP) SAP NetWeaver PI 7.1 (including EHP) SAP NetWeaver 7.3 |
SAP NetWeaver 7.3 |
|
Supported IDoc segment versions |
As of 3.1x, IDoc metadata can be retrieved |
As of 3.1x, IDoc metadata can be retrieved |
|
Supported releases/versions of the integrated software |
SAP applications based on
Non-SAP applications with a certified IDoc interface, for example EDI systems (requires a reference SAP system to connect to for IDoc metadata) |
SAP applications based on releases including SAP Basis 4.0 and higher |
|
Tool integration |
Available transactions in back-end systems:
|
|
|
Automatic generation of adapter (Integration Directory) |
Supported |
Not supported |
Communication, Connectivity, Security Settings
|
Attribute/Feature |
IDoc Adapter (IE) |
IDoc Adapter (AAE) |
|
Supported data transfer languages (code pages of connected systems, Unicode, etc.) |
Supports the exchange of IDocs with SAP applications running in any single code page, or in Unicode mode. |
|
|
Quality of service |
EO, EOIO with qRFC For more information in EOIO behavior and serialization concept for IDoc adapter (IE), see Serializing IDocs . |
EO, EOIO Not supported: Best Effort, qRFC and function module IDOC_INBOUND_IN_QUEUE |
|
Communication with systems with multiple code pages (Multi Display/Multi Processing - MDMP) systems |
Supported for IDoc inbound processing (sender adapter) |
Not supported |
|
Communication with JCO-based IDoc senders and receivers |
Supported |
Not supported |
|
Connection setting modes |
Connection configuration via RFC destination (transaction SM59) |
Connection configuration via RFC destination in SAP NetWeaver Administrator and via destination (transaction SM59; connection type = T) |
|
Security |
Basic authentication Transport level security |
Basic authentication Not supported: Security on transport level, principal propagation |
|
Partner conversion |
Supported |
Supported |
|
IDoc Packaging See figure below |
Supported (as of EHP 1 for SAP NetWeaver PI 7.1) |
Supported (but not at outbound side) |
|
Segment data change/reduction |
Not supported |
Not supported |
|
Automatic segment data reduction |
Supported (not relevant segments that were added in later releases are filtered out automatically) |
Supported (not relevant segments that were added in later releases are filtered out automatically) |
|
Enhancement by adapter modules |
Not supported |
Supported |
Auditing, Monitoring ,and Tracing Functions
|
Attribute/Feature |
IDoc Adapter (IE) |
IDoc Adapter (AAE) |
|
ALE Audit |
Supported Acknowledgment handling (XI message to ALEAUD and vice versa) is supported. |
|
|
IDoc tracing |
Supported (transaction IDX5) IDoc tracing for IDoc inbound processing is supported by a tracing API on the Integration Server. IDoc tracing for IDoc outbound processing is supported by transaction IDX5 on the Integration Server (in conjunction with tracing API on in receiver system). |
Not supported |
|
IDoc monitoring |
Transaction IDX5 |
Integration with channel monitor and message monitor (as part of Advanced Adapter Engine monitor) |
|
Status tracking -SYSTAT (analysis and further processing of messages that have not been processed) |
Not supported |
|
|
RFC monitoring |
Supported |
Not supported |
|
Message persistence in the IDoc adapter |
Supported Message correlation information can be stored in IDoc adapter. |
Not supported. Message is persisted in messaging system with correlation data persisted in adapter. |
IDoc Packaging
The IDoc adapters support IDoc packaging as illustrated in the following figures.
