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>

Similar Messages

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

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.

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.

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.

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

SAP-Xi --configuration: purpose is to receive Idoc in XI from SAPR3

Hi all,
Please provide information how to configure SAPR3 and XI systems to post an Idoc and receive and Idoc.
sender: Receiver
SAPR/3--->posts Idoc -
> XI receives Idoc
Please provide the configuration steps in detail. As i am new to Xi, Please help me to configure the same.
Thanx A Ton In Advance.
Bye all....

Hi Ajay,
Requirements in R3 system:
1. Create RFC destination pointing to XI in SM59
2. Create port for XI using we21
3. create Outbound Entry in partner Profile for XI in we20.
Requirements in XI system:
1. Create Technical System pointing to the R3 system.
2. create Business System pointing to the R3 system.
If you want to send IIDOC out of XI,
1. SM59 - Create RFC destination
2. IDX1 - Create port
3. IDX2 - Import Metadata.
Note:u dont need a IDOC sender adapter or a Sender Agreement to sent a IDOC to XI.
Check dis link for more info:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Cheers,
Prasanthi.

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

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

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

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

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,

Declare rfc destination to receive idoc

i am trying an example to declare rfc destination to receive idoc. the directions say to create a new destination of type "L" with the name INTERNAL and desination NONE. When i try to create a new rfc desination with destination NONE is says there is already one there but it is of type "I". It will not let me change this to type "L" and I cannot delete it.
Any idea how to do this???
Also when I create it says give a name of INTERNAL but i see no field which says "name".

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

Ale settings when receiving idoc from xi

Hi friends,
I wan o confirm that the settings I had done in my R/3 system for receiving idoc from Xi are correct.
Third party is goin to send message to my Xi system, from there I have to send that message to my R/3 system.
In R/3 I had created 2 logical system,one for r/3 itself and other for my XI system.
I assigned client to this systems.
I created RFC and port for XI.
Then created distribution model, with sender as xi logical name ,receiver as R/3 logical name.
Is this configuration correct?or I need to create the thirdparty logical system also in my R/3 system?

Hi,
Your steps looks fine to me. I think distribution model is not required for inbound case.
just check the below configuration once again.
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Also look at the step by step process.
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
chirag
Edited by: Chirag Gohil on Nov 24, 2008 1:23 PM

Configurations to receive IDocs in XI

Similar Messages

Maybe you are looking for