Configuring the Receiver IDoc Adapter 

Use

You need to configure the receiver IDoc adapter to convert Integration Server contents from IDoc XML to native IDoc format and to forward the IDocs to an SAP system or subsystem by using the standard tRFC IDoc interface. The IDoc control record is completed by the IDoc adapter.

If a sender system expects acknowledgment messages from an IDoc adapter, you also need to define a corresponding receiver agreement and a receiver IDoc adapter for this system. 

Integration

You configure the adapter on the Parameters tab page during the definition of a communication channel.

A communication channel with a receiver IDoc adapter can be created automatically for business systems that are defined in the System Landscape Directory. See also: Creating Communication Channels Automatically

Prerequisites

       1.      You have created a new communication channel or have opened an existing one.

       2.      On the Parameters tab page you have selected the adapter type IDoc.

Activities

To configure the adapter, specify the following:

Transport Protocol

IDoc is already specified.

Message Protocol

IDoc is already specified.

Adapter Engine

The Integration Server is already specified.

RFC Destination

Enter the RFC destination of the receiver system.

Segment Version

Specify which segments of the IDoc types are to be sent to the receiver system. Enter a three-figure reference for the release. Any incorrect entries here will result in a runtime error.

If you leave this field empty, the last version will always be used.

The metadata for Release 6.40 is available. The receiver system must only contain the segments for Release 3.0A. Enter 30A.

Interface Version

Specify which function module must be called in the receiver system to transfer the data in the relevant format. Function module calls for both interface versions are placed in the tRFC queue.

You can choose from the following versions of the technical IDoc interface:

●     SAP Release 3.0/3.1

INBOUND_IDOC_PROCESS

This function module is used for IDoc types with short names (for example, eight characters).

●     SAP Release 4.0 or Higher

IDOC_INBOUND_ASYNCHRONOUS

This function module is used for IDoc types with long names (for example, 30 characters).

Port

Specify the port that the IDoc adapter uses to receive the IDoc metadata. The port definition uses an RFC destination to receive the IDoc structure by RFC.

SAP Release

To convert the data from IDoc XML to IDoc format, the receiver IDoc adapter requires the IDoc metadata. If the IDoc metadata is not available, it will be loaded from the receiver system.

Specify the current release of the receiver system.

Queue Processing

If the function module IDOC_INBOUND_IN_QUEUE is to be used, set the relevant indicator. It is used for IDocs that are serialized by queues (quality of service is EOIO). This module is only available in SAP Web AS 6.40 and higher. If it is not available, the function module IDOC_INBOUND_ASYNCHRONOUS is called. The indicator only takes effect in SAP systems Releases 4.0 and higher. Calls for the queue processing function module are placed in the qRFC queue.

Apply Control Record Values from Payload

If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.

If you do not set the indicator, all combinations of communication parties and services are handled as services without party.

If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values. See also: Fields of the IDoc Control Record

Take Sender from Payload

If you want to take the sender of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.

If you do not set the indicator, the information is taken from the configuration in the Integration Directory.

Take Receiver from Payload

If you want to take the receiver of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.

If you do not set the indicator, the information is taken from the configuration in the Integration Directory.

If you set both of the above indicators, you do not require a heading mapping and do not need to set the alternative identifiers.

However, you must ensure that the SNDPRN, SNDPRT, RCVPRN, and RCVPRT fields are set in the IDoc control record.

Setting the senders and receivers of a message from the payload simplifies configuration and speeds up processing.

If the sender and receiver are not set correctly in the payload, the resulting error is only visible in the receiving system.

Restore Original Partners for Acknowledgments

If you set this indicator, the original parties from the IDoc request message are used for acknowledgments. This means you no longer have to maintain the alternative identifiers (for party conversion) in the Integration Directory.