This Blog will provide the Basic configuration guide for receiver IDOC adapter in SAP PI.
We use IDOC adapter to convert IDOC XML to native IDOC format and to forward the IDOCs to an SAP system or subsystem by using the standard tRFC IDOC interface.
Below are the configuration steps for SAP to ECC we will not go in details but listed out all steps which need to be completed for IDOC communication.
In SAP PI
- Create a RFC to ECC in SM59
- Create a IDOC port in idx2
- Create a IDOC Metadata in idx1
In SAP ECC
- Create RFC to PI in SM59
- Create a Port in we21
- Create a Partner profile in we20
How to do IDOC Adapter configuration?
Usage of Indicator: Apply Control Record Values from Payload
If you have set the above indicator in the receiver IDOC adapter, below fields are filled from the IDOC XML payload:
- MESCOD
- MESCFT
- TEST
- EXPRSS
- STD
- STDVRS
- STDMES
- SNDSAD
- SNDLAD
- RCVSAD
- RCVLAD
- REFINT
- REFGRP
- REFMES
- STATUS
- DIRECT
- OUTMOD
- CREDAT
- CRETIM
Usage of Indicator: Take Sender/Receiver from Payload
Below fields gets value at runtime by the configuration in the Integration Directory.
- SNDPRN: From the sender communication component, configuration in Integration Directory, System Landscape Directory
- RCVPRN: From the receiver communication component, configuration in Integration Directory, System Landscape Directory
To set the above fields at mapping level we need to select this option.
If we don’t set this option and value are taken from Communication component but sometime we get the error as below
Unable to convert the sender service XXX to an ALE logical system
This happen if Sender Component is has incorrect/blank adapter specific attribute as shown below
To overcome these errors we can to header mapping in Receiver Agreement
Communication component used in header mapping will have the correct adapter specific attribute.
You may also like other adapter series blog