Showing results for 
Search instead for 
Did you mean: 

Question About IDOC ADAPTER

Former Member
0 Kudos

I test a scenario as file->xi->IDOC->R/3

and another scenario as R/3->IDOC->XI-file

i think, it should be two Communication channel

to R/3,one is Receiver another is Sender

But when i create the channel ,after select the adapter

tyep as IDOC, i can not select the Channel as a Sender

Can only set it as a Receiver


and when i test the first scenario , the flowing error

appers(my test idoc message is 'CREMAS03':

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter


- <SAP:Error xmlns:SAP="" xmlns:SOAP="" SOAP:mustUnderstand="">



<SAP:P1>I:IDOC_ADAPTER:209 66609E10320A11D9ABCB000F1F6BBAD1 E1LFA1M</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Fehler: I:IDOC_ADAPTER:209 66609E10320A11D9ABCB000F1F6BBAD1 E1LFA1M</SAP:Stack>



all of setting seems fine.

Accepted Solutions (1)

Accepted Solutions (1)

Active Contributor
0 Kudos

The IDOC adapter does not need a sender channel, as all information the XI needs are stored in the message itself. Sender channels are requested mostly for polling adapters like file of jdbc. HTTP-, RFC-, IDOC- and XI-adapter do not need a sender channel (see manual for further details).

The error message seem not to be translated in your system. Here is the message text:

"MSGGUID &1: Control record must start with tag EDI_DC40, not &2"

So in the payload there is no control record for the IDOC.

Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.



Former Member
0 Kudos

thanks for your reply

just as u say

i checked the checkbox uncarefully when i edit the

communication channel

Answers (0)