IDOC adapter question

I am trying to set up a simple file to IDOC transaction ( as a poc ), and I think that I havent configured my IDOC reciever channel properly. I used IDX1 to get the port, and RFC destination information. When I used the wizard, it said that the channel configuration was not complete, so I tried creating it manually. I am able to create and activate it without getting any errors. However, when I send my Idoc message, I get the following error in my message:
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
I am guessing that my channel is what is screwed up. Any ideas or tips ? I noticed that in the adapter monitor of Runtime workbench, there is no entry for an IDOC adapter monitoring. Where else can I look to find specific errors ?
Thanks
Osman

Thanks Chris,
I got into bd54, and the LS are already configured. So I tried to set up the Business system with the "Adapter-Specific Identifier". But the Logical system box is greyed out, so I cant enter anything. The only box that is editable is the Marketplace Adapter entry.
Any idea what Im doing wrong...
Thanks
Osman

Similar Messages

Question to IDoc-Adapter

Hi,
we want to operate 3 software components (1. development status, 2.presentation, 3.productive) and all software components use the same IDoc-adapter.
My question is:
If we send a message from the R3/System ( one client) to XI. how can I configure the IDoc-Adapter that the message is going to the software-component development for example?
Or do we need 3 client to solve this problem?
Thanks in advance.
Regards.
Stefan

Hi,
>>>>we want to operate 3 software components (1. development status, 2.presentation, 3.productive) and all software components use the same IDoc-adapter.
1. this is HIGHLY not advisable to
use PRD with DEV on the same XI server!
if you do that you can expect many
problems on DEv that will have negative effects on PRD
don't do that never - it's like having
DEV and PRD R3 on different clients.. on one server
>>>>If we send a message from the R3/System ( one client) to XI. how can I configure the IDoc-Adapter that the message is going to the
2. there is no sender IDOC adapter but
I'm not telling you how to do it
because of point 1
Regards,
michal

Question About IDOC ADAPTER

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
why?
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" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<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>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
all of setting seems fine.

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.
Regards
Stefan

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

Basic Idoc Adapter Error - XI 3.0

Hi,
I am new to XI so excuse me if this is a basic question.
The scenario we have is File -> XI -> IDOC
When the message is processed into the IDOC Adapter I am getting the following error :
Control record must start with tag EDI_DC40 not E1LFA1M
Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
Is there something I need to change in the Idoc Adapter to get this to happen ?
Kind regards
colin.

It is not a basic question, but it seems to be a common problem.
Check in your IDOC receiver channel, if the checkbox "Apply Control Record Values from Payload" is marked. If so, uncheck it. That should help.
Regards
Stefan

IDOC adapter Retry interval

Hi
I am doing File-IDOC scenario.
For each 5 min there will be new file coming to the FTP folder..sender File adapter needs to pick the file and send as IDOC to R/3.
Each file consist of multiple lines..so i am using IDOC bundling..so for each file i am sending aroung 50 IDOCs at a time toR/3..
I am using BPM for this scenario...( i know we can do this without BPM also...but i have to use BPM..)
if R/3 system is down...then i am waiting for 2 min..and through deadline branch i am canceling the process...assuming that receiver system is down..and throughing alert to support team to intimate the same...
Each adapter is having default Retry interwal...if that adapter fails to send to the receiver...by default it will try for 3 time..with time interwal gap of 5min(i think) between each retry..
For each 5 min i will get a new file...so i have mentioned 2 min for deadline branch...
what happens if the IDOC adapter succeded in seconed attemt.(i mean after 5min) to send to receiver (here R/3)..?
--> i am sending alert to support team...but IDOC has sent succefully..which should not happen..so either we have to decrease the IDOC retry interwal or need to increase the deadline branch inerwal...
Questions:
What's the default retry interwal for IDOC adapter??
Can we decrease IDOC retry interwal time as normal file adapter in Visual admin..??
if i increase the Deadline branch time interwal...it will keep on trying to send first file..so waiting status..if sencond file comes after 5 min...it will also wait status..will there be any problem...??
Thanks
Murali

>>What's the default retry interwal for IDOC adapter??
Can we decrease IDOC retry interwal time as normal file adapter in Visual admin..??
No. Idoc adapter is not part of Java stack and hence you cant alter any idoc adapter settings in VA.
When the Idoc adapter fails, the message fails in SXMB_MONI unlike other adapters which pass through SXMB_MONI.
So, incase of Idoc adapter the restart depends on the reprocessing the error messages in SXMB_MONI.
Usually the report to restart errror messages in SXMB_MONI is scheduled as a background job.
You need to check for that. But in most cases, the interval is a few hours rather than minutes.
Jai

RE:SENDER IDOC ADAPTER

Hi ,
why don't we crate a communication channel for idoc on sender side,but when we go for receiver side we create communication channel .
please let me know how an idoc converted in to idoc-xml while transfer to integartion engine from sender side.( with out idoc adapter on sender side)

hi prateek,
The communication at sender also passes through the Idoc adapter.
with our configuring idoc adapter on sender side, how can an idoc passes through idoc adapter, is this because idoc adapter resides in abap stack.
can u briefly describe how can an idoc convert in to idoc-xml before comming to integration engine.
if idoc adapter is on abap stack then
in case of file to idoc
why we go for idoc adapter . (con't the process same as reciver side) .
please give brief explain to each of my questions.

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Receiver Idoc adapter - issue

Hi,
I need to send an IDoc (CRMXIF_ORDER_SAVE_M01) to SAP CRM. The trouble occur when having/wanting to use/send only the segments that apply to release 620.
In order to do that I have in my receiver IDoc adapter specified the value '620' in the Segment Version part.
As soon as having done this my IDocs fail in the adapter giving me the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The segment specified in the above corresponds to the very fist sub-segment to the main segment (BUSTRANS). So if removing that segment the error jumps to the next segment (which would then be the first sub-segment).
Should be noted that I have no trouble sending IDocs if I've either not specified a Segment version (meaning latest version is automatically used) or if I explicitly request the latest by entering the latest segment release (700 in my case).
<Trace level="1" type="T">Convert one IDoc</Trace>
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_BUSTRANS</Trace>
<Trace level="2" type="T">Ignore unknown Segment E101CRMXIF_BUSTRANS</Trace>
<Trace level="2" type="T">Ignore segment field: APPL_SNAME</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_TASK</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_GUID</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_ID</Trace>
<Trace level="2" type="T">Ignore segment field: PROCESS_TYPE</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_TYPE</Trace>
<Trace level="2" type="T">Ignore segment field: POSTING_DATE</Trace>
<Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE</Trace>
<Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE_ISO</Trace>
<Trace level="2" type="T">Ignore segment field: LOGICAL_SYSTEM</Trace>
<Trace level="2" type="T">Ignore segment field: CRM_RELEASE</Trace>
<Trace level="2" type="T">Ignore segment field: CLIENT</Trace>
<Trace level="2" type="T">Ignore segment field: CREATED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CREATED_BY</Trace>
<Trace level="2" type="T">Ignore segment field: CHANGED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CHANGED_BY</Trace>
<Trace level="2" type="T">Ignore segment field: LOCAL_TIMEZONE</Trace>
<Trace level="2" type="T">Ignore segment field: OBJECT_ID_OK</Trace>
<Trace level="2" type="T">Ignore segment field: HIGHEST_ITEM_NO</Trace>
<Trace level="2" type="T">Ignore segment field: CRM_CHANGED_AT</Trace>
<Trace level="2" type="T">Ignore segment field: CALC_SCHEMA</Trace>
<Trace level="2" type="T">Ignore segment field: SCENARIO</Trace>
<Trace level="2" type="T">Ignore segment field: VALID_FROM_EXT</Trace>
<Trace level="2" type="T">Ignore segment field: VERIFY_DATE</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY_X</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E103CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E107CRMXIF_ADDRESS</Trace>
<Trace level="2" type="T">Ignore unknown Segment E107CRMXIF_ADDRESS</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS_F</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON</Trace>
<Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON_F</Trace>
Hope someone can help me so that I can succesfully limit the segment version used when sending Idocs.
Best regards,
Daniel

Hi,
Thanks for your quick reply.
The funny thing is that even if a try to post the exact same idoc (except for the EDI part) that I have received from CRM it still fails in XI with the before mentioned error.
But to answer your questions:
1. I'm not using java mapping but traditional message mapping (meta-data are up-to-date and structure is newly loaded).
2. No blank segments are being created
3. All segments have value 1 or blank (using blank works fine for me, that is when not trying to limit Segment version. But using 1 makes no difference)
Best Regards,
Daniel

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

>so i cant use apply control rec values from payload.........
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

Sender agreement & communication channel not needed in case of IDOC adapter

Hello everyone ,
I am new to xi , as far as i know a communication channel cannot be created in ID when using IDOC adapter , the answer for this question is like , the idoc adapter resides on the integration server & not part of j2ee AF .
Can some one explain me in the terms of a laymen , its not clear to me.
Thanks & Regards,
Reena.

Hi ! Reena
IDOC adapter resides on Integration server, so Integration engine takes care of the conversion format from IDOC to XML, hence there is no need for sender Adapter .Also since its residing on Integration server you can directly post the message in the Integration engine.
well lemme explain a little bit,the main reason for sender agreement is to associate namespace with the sender adapter,now when we shoot IDOC from R/3 it already contains its standard SAP namespace so no need of sender agreement.
now comes the sender CC,main use of sender CC is to identify the sending system and the adapter.the IDOC header contains details of all the this,so again there is no need for sender CC
loook at this thread discuss the same
Re: Why we r not Creating Sender Agreement For HTTP & IDOc Adapter at Sende
Re: why HTTP & IDOC adapter do not require sender communication channel?
Thanks!!
Questions are welcome here!!
Also mark helpful answers by rewarding points
Regards
Abhishek Agrahari

Adapter Questions

hi.....what kind of questions will ask on Adapters in XI certification

Hi Venkatesh,
some more question on adapters:
1. I have a problem with sending RFC from R/3 to XI
2. How do I use 'Apply Control Record Values from Payload' parameter with the IDOC adapter?
3. I can't see my adapters in the adater monitoring after the import of a new SP
4. Where can I find J2SE plain Adapter
5. How can I access filename from File/FTP Sender Adapter
6. Where can I find FAQ on adapters?
7. Where can I find examples on Adapter module development?
8. Where can I find http adapter test tool?
9. How can I access adapter monitor?
10. I'd like to develop my own adapter - how can I test the sample adapter?
11. How can I dynamically set some parameters in the adapter configuration?
12. Which value should I fill in the RFC sender adapter for Program ID parameter?
13. What is the SOAP action value in the SOAP receiver adapter?
14. Where can I find JAR files for creating java proxies?
15. How can I debug my abap proxy?
16. Adapter Engine returns HTTP 401 under high load what can I do?
17. How can I work with profile other then LS with IDOC Adapter?
Amaresh

Idoc packaging questions

Hi
I am aware that in Idoc packaging how Sender Idoc adapter packaging is done and also know that it is available from PI7.11
I have 2 questions...
1. Suppose there is a data issue with a single idoc ,,because of that entire package will fail...then it would call for finding the erroneous idoc ...correct the data and resend all the Idocs again..
This problem can occur again and again...and because of this the entire package will be stopped..
So is it a good option to not do packaging and send a single Idoc and insert it as a record in target database.
2. In case i am doing idoc packaging the occurence of IDOC in mapping will still be 1..1.
How do i manage my mapping such that each Idoc in the package should insert a separate record in the database table
Hema

>
> 2. In case i am doing idoc packaging the occurence of IDOC in mapping will still be 1..1.
>
> How do i manage my mapping such that each Idoc in the package should insert a separate record in the database table
>
Map IDoc to access tag, in this case one record for each IDoc will get inserted.

IDOC Adapter error while load balancing

Folks,
I am facing an issue when I am switching on Load balancing button in RFC destination while sending IDOC in sender system . The sender system shows this error in SM58
IDoc adapter inbound channel: Error Error when rea
Thanks,
Manish

Hi Manish...
This is from F1 on Traget host field in SM59..Check part in bold..
Name of target host
 Name of the target host as displayed by the UNIX command 'hostname'.
 If you are using load balancing, the target host must be the host name
 of the message server of the SAP System. This is defined in the profile
 parameter 'rdisp/mshost' of the target system. If you have any further
 questions, consult your system administrator. 
 You can specify host names as
 - Normal host names
 - Host names in DNS format (if DNS available)
 - IP addresses
 - SAProuter names (in the form /H/.../S/.../H/.../S/... )
Notes
 If you enter the host name (for example, hs0311) as the target host in
 an RFC destination, its IP address is stored internally in the database
 table RFCDES (destination administration). This speeds up the RFC
 connection initiation, since the host name does not need to be converted
 into its IP address.
 However, problems occur if the IP address of the target host changes.
 For this reason, you must adjust the RFC destinations if the IP address
 of the target host changes.
 If you specify the host name as a SAProuter name (/H/hs0311 instead of
 hs0311), it is not converted into its correspondidng IP address.
 Instead, it is stored in its SAProuter form in table RFCDES.

Why Sender side IDOC adapter doesnt have SenderAgreement and Sender CC

Why Sender side IDOC adapter doesnt have SenderAgreement and Sender CC . But in receiver side it is having.
what i know is
1) Idoc adapter is in ABAP Stack.
2)XI having Idoc Metadata.
3)Once Communication Idoc generated , no control on it.
4)SAP using TRFC to identify XI , XI cant.
Pls explain , in comparition with receiverside. Dont post links.

Hi vijayreddy.veluri
these questions are very general.
Please refer to the
[rules of engagement|/thread/117188 [original link is broken];
before creating threads.
Sender agreements are not required as there is no requirement to bind sender information to a sender communication channel.
[IDoc Processing with the IDoc Adapter|http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm]
Thanks and Regards
Kenny Scott
SDN XI/PI Moderator

IDOC adapter question

Similar Messages

Maybe you are looking for