Configuration Of Receiver Idoc Adapter

Hi Experts,
for an interface,I need to desighn a receiver idoc adapter.Plese guide Me
regarding following matters:
1. how to configure receiver idoc adapter ?
2. how to get the control record for the receiving idoc?
3. what are the configuration we have to make?
4. receiving idoc's data i want to update in my SAP database,How to achieve that?(Any program I have to write?what i need to mention in there?)
Eagerly looking for valuable suggestions.
Regards,
Rasmiraj
Edited by: rasmiraj tripathy on Aug 29, 2011 1:32 PM

Hi RashmiRaj,
Configuration Scenario
1. Create the RFC Destination in SM59.
2.Create Port in IDX1.
3.Create Logical System in BD54
4.Create A Scenario
5. Select a Business System in Service with out Party
6.Create a Receiver Communication Channel.
7. Create a new Business Service
8. Create a new Communication Channel
9. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.
10. create sender agreement
11. Create Receiver Determination
12. Create Interface Determination
13. Create Receiver Agreement
Also check the link [File to IDOC|http://www.****************/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm]
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?quicklink=index&overridelayout=true
Thanks and Regards,
Naveen
Edited by: chichilin on Aug 29, 2011 5:40 PM

Similar Messages

Configurations for Receiver IDoc adapter??

Hi,
I have a File-to-Idoc scenario. In the Reciever Idoc adapter configuraiton, we have to provide: 1) RFC destination and 2)Port. Where do we define the RFC destination and Port? Do we have to do any any configuration in R/3 in we20 and we21?
Any help is greatly appreciated.
Thanks,
Karma

1) RFC destination and 2)Port. Where do we define the RFC destination and Port?
>>These are defined on XI server in IDX1 tcode.
>>Port is SAP<XXX>, <XXX> = SID of R/3 receiver system
>>RFC destination is the one u mention in this port definition.
>>First define the RFC destination in SM59 of XI Server.
>>U need not do anything in IDX2.
Do we have to do any any configuration in R/3 in we20 and we21?
Yes.
In WE20 of R/3, u have define the partner profile for XI server with the IDoc as inbound parameter.
In WE21 port for connecting to XI server. Here also u have to mention the RFC destination, which has to be defined in SM59.
Good luck.
-Naveen.

Can we go with ALE configuration instead of receiver idoc adapter at target

Hi Experts,
Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI to Target system instead of configuring receiver IDOC adapter at target side.

Hi Raj
Point 1:
When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
Point 2:
When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
Regards,
Raj

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

Problem with an Receiver Idoc adapter

Hi.
We have just went from XI 3.0 to PI.7.10.
The Receiver idoc adapter is set up in the same way as it was in XI.
The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
The idocs are different messagetypes.
In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
Any idea whats wrong ?
/Per-Arne

Thanks.
Checked sxmb_moni as you said.
In the OutboundBinding-node I can see the right idocadapter is used
where 'Apply Control Record Values from Payload' is enabled.
<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>001</SAP:MANDT>
<SAP:DOCREL>710</SAP:DOCREL>
<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>OILLDD</SAP:MESTYP>
<SAP:MESCOD>EXT</SAP:MESCOD>
Too be more specific about the interface.:
I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
two different idocs-adapters.
I think you are right about that the configuration may be mixed up.
Any idea of what I can do?
It may be an PI 7.10 bug ?
Shall I delete all config objects and so set config up from scrach again ?
/Per-Arne

Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

Hi All,
We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

Hi,
Both the sender and receiver IDoc transmission is done by the RFC communication channel.
In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
Hope this helps...!!!!
~SaNv...

Idoc packaging for Receiver Idoc adapter in 7.11

We are using PI 7.11. And, I have a File to Idoc scenario. I am trying to find an Idoc packaging option for Receiver Idoc adapter. Any suggestions on how to do configure thi scenario?
Thanks
abhinaya4321
Edited by: abhinaya4321 on Dec 3, 2011 12:15 PM

hi,
We are using PI 7.11. And, I have a File to Idoc scenario. I am trying to find an Idoc packaging option for Receiver Idoc adapter. Any suggestions on how to do configure ?
that is possible with message packaging concept it is suitable for you requirement
go through below links:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c?QuickLink=index&overridelayout=true
thanks,

Is Dynamic Configuration possible with IDOC adapter.

Hi,
I have SOAP to IDOC scenario. I have many SAP receivers and are determined at runtime in a Java map.
Can i use Dynamic Configuration for IDOC adapter?
Thanks
Shakthi

Hi Sivasakthi,
Why do you need Dynamic Configuration in receiver IDOC?
Regards,
Sanjeev.

Configuration Of Receiver Idoc AdapterRe

Hi Experts,
for a interface,I need to desighn a receiver idoc adapter.Plese guide Me.
1. how top configure receiver idoc adapter ?
2. how to get the control record for the receiving idoc?
3. what are the configuration we have to make?
4. receiving idoc's data i want to update in my SAP database,How to achieve that?(Any program I have to write??)
Eagerly looking for valuable suggestions.
Regards,
Rasmiraj

Hi,
please go through this blog, i hope you will get all answers
http://www.****************/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm
regards,
ganesh.

Adapter Module for receiver IDOC adapter?

Hi,
I have a scenario where i need to do some custom logging in the receiver adapters. For all receiver file adapters, i have written an adapter module which fulfills this custom requirement but how will i do this in the receiver IDOC adapter as its on the ABAP stack? I cannot write a java adapter module for this.
Is there anyway by which i can write a ABAP adapter mosule and deploy it in the IDOC adapter? Or any other way to achive it. the scenario is such that i need to do the logging before the idoc is posted into R/3 system by the idoc adapter.
Please advice.
Regards,
Yash

Hi Chirag,
Yes i have seen that the module tab is disabled for idoc adapter. I have a fin interface where i need to split a incoming file into an idoc and a file. For this purpose i need to log how many records are received by each adapter and the sum of the line items for audit perspose.
any othr way to do it apart from doing it in message mapping. The req is to do in the adapter engine.

Receiver IDOC adapter - RFC_NO_Authority

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
Went thru receiver determination, Interface determination, message split, request message mapping, Technical routing and then got stuck at call Adapter stage. Below is the error:
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Runtime error RFC_NO_AUTHORITY has occurred</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Runtime error RFC_NO_AUTHORITY has occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Is there any step that I may have missed after I created the receiver IDOC Channel?
Could you please shed some light here?

Please, search SDN before posting....
check these link: Runtime error RFC_NO_AUTHORITY has occurred in SM58
What its error?

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

Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

Scenario:
EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
I'm getting an error (below) at the Call Adapter stage:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
I::000
and thus the IDOC can't get recreated.
Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
Can someone please shed some light?

Hi,
Addition to the above
Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
it should be only SAPSID..(SID is your system name..)
HTH
Rajesh

Configurations to receive IDocs in XI

Hi experts,
I'm using PI7.0 SPS10.
I have a scenario IDOC -> XI -> File.
From what I've read in the numerous threads posted before me, the configurations required on XI for such scenario is:
1. SM59
2. IDX1
3. IDX2
For the above scenario, my understanding is I do not need an iDoc Sender adapter, because the IDOC resides on the ABAP stack.
I am able to import the IDOC structure into IR, and create message mappings for the message types.
I have created 2 business systems
BS_NHGDDBS01 : The business system for the corresponding R/3 sender system. This has a TS of type WebAS ABAP - NHGDDBS01.
BS_DEV1_NAUTICUS_OOTS: The business system I created, simply to house the various projects/mappings that I will need. The mappings are housed in a SWCV which i defined.
I created my mappings for IDOC->File, under BS_DEV1_NAUTICUS_OOTS.
I activated the mapping in Integration Directory.
My questions:
1. Am I doing this correctly? I'm puzzled because I did not use the business system BS_NHGDDBS01 at all.
2. With this current setup, can XI receive IDoc from NHGDDBS01? I do not see a configuration mapping the IDoc to the message Interface which I want.
Please help to clear my doubt.
Thanks.
Ron

Hi,
>>>>I created my mappings for IDOC->File, under BS_DEV1_NAUTICUS_OOTS.
you cannot do that- you create it under software component not busines system
>>>>I activated the mapping in Integration Directory.
you activate them in repository not directory
for all scenarios with IDOCs and XI:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Configuration Of Receiver Idoc Adapter

Similar Messages

Maybe you are looking for