You use the IDoc adapter to have IDocs (intermediate documents) processed by the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported. You can also use the IDoc adapter to connect non-SAP systems to the Integration Engine.
The IDoc adapter converts the IDocs to IDoc XML format so that they can be processed by the Integration Server pipeline.
You can also transfer XML in IDoc format received from the Integration Server to connected systems. The Integration Server pipeline 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 identified receiver system using the standard IDoc interface.
More information: IDoc Processing with the IDoc Adapter
General Prerequisites
You should only stop using existing functioning IDoc scenarios after serious consideration.
For more information, see the documentation on the Integration Directory → Defining Communication Channels → Creating Communication Channels Automatically.
This only makes sense if IDocs are to be received by the Integration Server and sent again as IDocs without changes to the data records. Avoiding unnecessary conversions from and to XML can lead to improvements in system performance.
More information: Pipeline Service, Display/Change Configuration Data
The authorizations for the individual transactions are based on the respective requirements; they are assigned as derived from the following roles. They are all based on the authorization object S_XMB_AUTH or S_XMB_DSP.
Authorizations and Roles
Transaction | Authorization Object | Role |
---|---|---|
IDX1 |
S_IDOCMETA |
SAP_XI_ADMINISTRATOR |
IDX2 |
S_IDOCMETA |
SAP_XI_CONFIGURATOR |
IDX5 |
S_XMB_DSP |
SAP_XI_MONITOR |
Prerequisites for the Integration Server
More information: Configuring the Integration Engine
You can only include IDoc types in this table that are already defined in the system. These IDoc types are not processed using the Integration Engine.
To delete IDocs from the IDXIDOCINB exception table, use the report IDX_DELETE_IDOCTYP_WITHOUT_IS.
An IDoc must be syntactically correct to be able to convert it to IDoc XML. We recommend that you activate the syntax check.
This parameter defines whether the IDoc is transported as a table in the IDoc adapter and not converted to IDoc XML. This only makes sense if IDocs are to be received on the Integration Server and sent again as IDocs. If none of the services in the Integration Engine use the IDoc XML then you can optimize performance by avoiding the unnecessary conversion of IDocs to IDoc XML and the other way around.
More information: Displaying/Changing Configuration Data
More information: Loading IDoc Metadata, Port Maintenance in the IDoc Adapter
More information: Comparing Metadata with the Reference System
Prerequisites for Application Components
You do not need to change existing applications.
Sender System
In the sender system you need to change the target address of the RFC destination of a tRFC port for the Integration Server.
Choose the corresponding RFC destination by double-clicking it.
More information: Displaying, Maintaining, and Testing Destinations
More information: Displaying, Maintaining, and Testing Destinations
More information: Managing Ports for IDoc Metadata
More information: Creating an Outbound Partner Profile
Receiver System
You must change the partner profiles in the receiver system.
To do this, call the transaction Partner Profiles (WE20) and create an inbound partner profile for the sender party.
Specify the inbound message type and the basis type for the inbound parameters.
In addition to this there is no configuration for the sender adapter in the Integration Directory. The configuration only takes place in the sending system.
More information: Configuring the Sender IDoc Adapter
More information: Configuring the Receiver IDoc Adapter in the Integration Directory
More information: Serializing IDocs
This enables you to improve performance.
To create message packages, use event-driven message processing.
More information: Event-Driven Message Processing
More information: Configuring Acknowledgment Requests
More information: Sending Acknowledgment IDocs as XI Request Messages
More information: Displaying XML Messages