Configuring the Receiver IDoc Adapter

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 adapter fills the IDoc control record with data.

More information: Control Record .

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.

You can automatically create a communication channel with a receiver IDoc adapter for business systems that are defined in the System Landscape Directory.

For more information, see the documentation Integration Directory → Defining Communication Channels → Creating Communication Channels Automatically.

1. The transport protocol is IDoc.
2. The message protocol is IDoc.
3. The Adapter Engine is the Integration Server.
4. Under RFC Destination, enter the RFC destination of the receiver system.
5. Under Segment Version, specify which segments of the IDoc type are to be sent to the receiver system.

   Enter a three-figure reference for the release.

   If you enter incorrect data, a runtime error occurs.

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

   Tip

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

6. Under 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 the interface versions are placed in the tRFC queue.

   More information: tRFC Queue

   • 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).

7. Enter 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.

8. Under SAP Release, specify the current release of the receiver system.

   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.

   More information: Loading, Displaying and Deleting Metadata

9. If function module IDOC_INBOUND_IN_QUEUE is to be used, choose Queue Processing.

   The function module is used for IDocs that are serialized by queues (quality of service is EOIO). This module is only available in 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.

10. To reassign the communication party to the IDoc partner, choose Apply Control Record Values from Payload.

    This is only possible for systems that are not logical systems.

    If you do not set the indicator, all combinations of communication parties and communication components are handled as communication components 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.

    More information: Fields in the IDoc Control Record

11. If you want to take the sender of the message from the payload and not from the configuration information in the Integration Directory, choose Take Sender from Payload.

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

12. If you want to take the receiver of the message from the payload and not from the configuration information in the Integration Directory, choose Take Receiver from Payload.

    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.

    Caution

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

13. If the original partner from the IDoc request message is to be used for acknowledgments, choose Restore Original Parties for Acknowledgments.

    This means you no longer have to maintain the alternative identifiers (for party conversion) in the Integration Directory.