Show TOC

Procedure documentationConfiguring the Sender IDoc Adapter Locate this document in the navigation structure

 

You configure the sender IDoc Adapter to be able to process IDoc packages that come into the inbound channel of the Integration Server further using the Integration Engine. You can specify segement release so that IDocs are forwarded correctly.

Prerequisites

  • You have made the settings in the sender system.

  • If you want to specify segment release in the adapter and have already loaded metadata, delete all metadata for the sender port and loads the metadata again.

    More information: Loading, Displaying, and Deleting Metadata

  • If you want to use IDoc packaging, activate the syntax check in the Integration Engine configuration (parameter SYNTAX_CHECK).

Procedure

  1. The transport protocol is IDoc.

  2. The message protocol is IDoc.

  3. The Adapter Engine is the Integration Server.

  4. To be sure that only those fields that relate to the release are transferred from each segement, enter the release under segment version.

    Enter for example 640 for release 6.40.

    If the inbound IDocs have a higher release than specified here, then the segments are taken from the higher release.

    If you do not make any entries it is possible that more fields are transferred from the inbound IDoc than actually relate to the release.

  5. If you also want to forward IDoc packages using the IDoc Adapter, choose IDoc Packaging.

    IDocs of the same message type/IDoc type/CIM type are compiled into one IDoc XML. An IDoc package remains in message processing until an acknowledgment has been returned for each of the IDocs that it contains. An ALE Audit is created for each package in which the combined IDocs are noted.

    You have selected IDoc packaging and it is not possible to transport IDocs as a table.

    ALE Audits are not combined into packages.

  6. Under IDoc Package Size specify the maximum for how many IDocs can be put into an IDoc XML.