Idoc adapter- communiccation channel

Hi
When we do an Idoc to file scenario sender communication channel is not required. Because Idoc is the sender adapter. but while doing a File to Idoc case why do we neeed a receiver communication channel. Here also we use Idoc so why use a communication channel ?

Hi,
You do not need A Sender IDOC Adapter. IDoc's are sent directly to XI's Integration Engine and so no need of Sender IDOC adapter and therby Sender Agreement as well.
Yes, the port will be a TRFC port and you will use the RFC destination created in SM59 in this port.
Idoc Metadata gets loaded automatically when your scenario is run. You can also do it manually, by going to IDX2 and probiing the Port and the Basic Type of the idoc whose metadata you want to load.
but when we go for a fileto IDOC the file does not contain a standard structure
for that reason we need to create the receiver IDOC adapter .
pls chk this links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
if found worth pls do the req
Thanx
Sampath

Similar Messages

Issue about IDoc Adapter Receiver Channel's Performance

Hi Everyone,
Currently, I am working on a scenario of File -Integration Process - IDoc in XI 3.0 with patch level 16. The scenario works fine when it process one/two/three files in parallel, and the IDocs arrive R/3 system quite fast. But when I try four files in parallel, the whole XI server blocks, I can not do anything even logon Integration Builder, and the IDocs arrive R/3 brokenly, sometime with the invterval to 10 minutes. When the XI comes back, I found all the four integration processes finish successfully and each transaction works fine and fast. What's more, after I change the IDoc Adapter receiver channel to a File Adapter receiver channel, it works fine for even 20 files in parallel. So I think it is some issue about IDoc Adapter receiver channel. Does anyone have the same experience as me? Any comments will be appreciate.
Regards,
Nick

Hi Nick,
Can you check this Blog-
/people/sreekanth.babu2/blog/2005/01/05/delayed-xi-message-processing
May be useful.
How are you picking the files .. You can try with EOIO options while picking the file.
But if you use BPM, it is not applicable. It will act as a EO only.
Check this SAP Note- 833740
Thanks,
Moorthy

IDoc adapter inbound channel: Error Fehler beim Le

Hello,
I have a BIG problem. I want to use IDOC - XI - IDOC. I have configured the connections. But when I send the Idoc to the XI. it returns a code in the SM58 "IDoc adapter inbound channel: Error Fehler beim Le" The Message comes cut, it doesn't return all the message. In the XI doesn't give me any error, nothing. The IDOC says thta it has been sent correctly (Code 3). How can I trace the IDOC from de sender to the XI?
I wanted to use the IDOC HRMD_A06 but now i'm trying with SYIDOC to see if it passes.
Can Someone help me?
Caller Function module Target system Date Time Status text
SRGEN13 IDOC_INBOUND_ASYNCHRONOUS RHXCLNT013 07.04.2006 10:06:46 IDoc adapter inbound channel: Error Fehler beim Le
Thank you
PM

I want to know if the Connections have to have SNC?
I have read this in the note http://help.sap.com/saphelp_nw04/helpdata/en/ca/fafaf6dbc8b240b1cf4a88c40379b2/frameset.htm
Inbound and outbound connections should be secured by Secure Network Communication (SNC).
Is that correct? maybe that's why it says the that error
PM

IDoc adapter inbound channel: Error Error when reading Exchange Profile

Hello Experts,
Currently i am working on an IDOC to file scenario, in which Data will be sent from ECC server (IDOC) to an FTP server via SAP PI, but when i try to send IDOC to PI, i am getting the following error
in Transaction SM58:-
'IDoc adapter inbound channel: Error Error when reading Exchange Profile for system XID and
client 401 occurred in the IS pipeline' .
Can anyone please help me on this.
Thanks & Regards,
Amit Naik

Hello Experts,
Let me explain to you the whole scenario, We have two servers of PI, 7.1 & 7.0. Now the Java Stack of 7.0 is not working & Cache update of 7.1 is not happening.
Thats why we have linked ABAP stack of 7.0 with Java stack of 7.1. Now we can see the objects created under Java 7.1 in ABAP stack of 7.0 (SXI_CACHE).
Now we have done all the settings to create an IDOC to file scenario. All the RFCs are working fine, but when we send an IDOC from the ECC system to ABAP 7.0, we are getting the following error 'Error while reading exchange profile for system NW' in SM58 .
Now can anyone tell me what exact settings i have to change in the Exchange profile (Java stack of 7.1), so that the Java 7.1 & ABAP 7.0 connection is setup or do i need to change anything else.
Thanks & Regards,
Amit Naik

IDoc adapter inbound channel: Error Error while read

Dear All
I am sending idoc from SAP 4.6C to PI. But on SM58 I am getting an error
IDoc adapter inbound channel: Error Error when reading
Which is not complete because field length is 50 characters , double clicking on this message is asking for message class. How can i see the complete message.
Can any one send me configuration detail of receiving IDOC at PI end , I don't want send to it forward from PI.

Please clear these points.
In PI system:
1. Create RFC destination of type 3 pointing to R/3 system.
2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.
3. Using IDX2 import the IDOC meta data in to your PI system.
RFC destination to which direction , towards sender of IDOC ?
Port of which system sender system or receiver system?
What about configuration in Integration Directory , is there any configuration required on integration repository and on integration directory.
What will be the procedure of seeing complete message on SM58.
-->In PI system while ur creating the RFC destination of type 3 give the hostname and system number of ur R/3 system ie SAP 4.6 c.
-->In PI create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system and in that RFC destination option, maintaine the destinatination name which we created using sm59.
-->coming to IR you need to create the:
                    1. Receiver data type.
                    2. receiver message type
                    3. receiver message interface. No need to create the above 3 for sender.
                   4.while mapping source is your Idoc and target is your receiver message type.
                   5. while interface mapping source is Idoc and target is receiver interface.
-->Coming to ID no need to create sender communication channel and no need to create sender agreement.
-->create receiver communication channel and receiver agreement.
--->create Interface determination.
-->create receiver determination.
-->If message got stuck in SM58, unlock it by using double click or activate the selected message.
Thanks

IDoc adapter inbound channel: Error Connection err

Hi,
We are trying to push an IDoc from R3, it's status is green in WE02. However, the IDoc is not reaching PI.
In tcode SM58 in R3 we are getting an error "IDoc adapter inbound channel: Error Connection err". I have gone through the SAP note 940313 but was not able to figure out the exact cause of error.
Any help would be appreciated.
Regards
Pravesh

Hi,
Please check the steps for Idoc posting to SAP PI system from R/3. Probably you are missing some configuration.
Few Checks -
1. did you created Logical System using BD54?
2. Create RFC destination Type 3 for PI
3. create partner profile using we20
In Pi
Check following
1. Create RFC destination of type 3 pointing to R/3 system.
2 . create Port using the IDX1
3. Using IDX2 import the IDOC meta data
Regards
Aashish Sinha

IDOC adapter and number of tRFC records

We have idoc inbound scenario file -> XI -> idoc -> R/3.
For each file record an IDOC is created.
Can somebody explain, why only one tRFC record is created containing all IDOCs? Can you influence with interface config how many tRFC records are created? Does settings ' exactly once ' / ' exactly once in order ' have something to do with how many tRFC entries are created?
We faced a situation with our interface scenario that file unexpectedly contained huge number of records causing huge number of idocs generated in XI. However only one tRFC entry was created that contained all idocs. As consequence the receiving system had performance problems and the tRFC call had to be cancelled.
As workaround we splitted the source file in file adapter to interval of 1000recs, thus causing multiple tRFC records created and performance was ok in background system.
Is XI trying to keep IDOCs created out of each incoming message in one "LUW" and send them alltogether in one tRFC call to R/3? Or is there a config parameter that each created IDOC could be sent independent of other idocs still to be created?
br: Kimmo

Kimmo,
There will be one TRFC call per message from XI.
The whole input file is treated as a XI message.
The Receiver IDOC Adapter call the SAP system via ONE TRFC call and posts the message.
By mentioning Exactly Once in the Receiver Idoc Adapter Communication Channel, XI guarantees the delivery of that message.
One way is to split the file into multiple Messages.
You can do this via BPM. But this is not advisable for large files.
We had the same problem for very large files.
We used XI to just pass through the file from Source system and post as file in the Application Server of SAP.
We defined a LSMW project for Periodic Processing, which would take this file and post as Idocs in the SAP System.
Our Scenario
File -> XI -> File.
In the Receiver File Adapter, use the Execute Operating System Command to trigger event sapevt in the SAP system.
You can define events for Background jobs.
So when XI posts the file in the Application server of SAP, XI will trigger the background event defined in the Communication Channel.
The LSMW project which has been scheduled to listen to this background event will kick off.
Hope this helps.

Sender Information in control record of IDOC adapter

Hello All,
I am sending data from JMS to R/3 (IDOC). I need to populate the SNDPRT with LI and SNDPRN with 42980.
I have mapped SNDPRT with LI and SNDPRN with 42980 in the control record. I have checked the Apply Control recrod values from check box in the IDOC adapter communication channel.
Also checked the Sender Party in the Receiver aggrement. I have selected the context object as the SNDPRN of IDOC control record
But it is failing. I am getting an error Unable to convert sender XI party ........to an IDOC party
I need to resolve thsi problem
Please help me.

Hi Abinash,
In addition to the document Mike suggested, SAP has many How-to Guides at the following link
http://service.sap.com/nw-howtoguides
https://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
Mike: Thanks a lot for spending your valuable time helping the forum even on Weekends. SAP really appreciates your help on this.
Regards,
Sam Raju

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.

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

IDOC adapter is not shown in communication channel

hi gurus,
at present i am using PI and in the communication channel list (adapters types) no idoc adapter is displayed ,can anyone help me to solve this problem.
and also when i create any scenario related to idoc those messages where not displayed in communication channel.

Hi Allen,
U r checking for an IDoc channels in Communication channel monitoring.IDoc adapter is reside in ABAP stack.So that u cant see the Idoc communication channels from monitoring of CC's. If Idoc messages is at sender side no need of CC.
If you want to view the source and target messages of Idoc's u can see those from SXMB_MONI.Choose u r processed message,Dbl click,For Idoc as sender u can view the message from payloads of Inbound message,For Idos as Receiver u can view the message from Payloads of Request message Mapping.
Hope it will helps..
Cheers
Veera
>>>Reward points,if it is needful

Do we communication channels in idoc adapter

do we create communication channels in idoc adapter
Edited by: katru vijay on Jul 24, 2010 10:54 AM

Hi Ashwin,
I stop and start the channel but it is still in red. The communication channel is working fine.
Resarting the box will clear this but we cannot restart each time this isuue occurs.
Ca you suggest any parameter with which we can limit the number of days to 1.
Thanks.

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

IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Hello,
I'm trying to establish IDoc communication. Here is the scenario that I need:
<XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System
I have the following components set up:
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
2. Sender Agreement
3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous
4. Receiver Determination
5. Interface Determination
6. Receiver Agreement
7. Receiver IDoc Communication Channel
8. Business Service for all this
No Integration Scenario.
If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.
Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:
RFC Destination: NX7CLNT800
Port: A000000022
SAP Release: 3 - this is I put myself
But when I run the whole system again, I'm getting the error:
IDOC_ADAPTER ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"
This is very confusing because both my message interfaces are Asynchronous.
Can anyone tell me what I'm doing wrong and why I'm getting this error.
Thanks.

8. Business Service for all this
Should it not be Business System for IDOC.....for SOAP it will be Business Service
1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

XI 3.0 IDoc Adapter Problem

Hello,
I have a problem to establish an Idoc communication between SAP R/3 4.70 and SAP XI 3.0.
Following systems I have defined in XI SLD:
Sending R/3: HS3CLNT100
Receiving XI: X30CLNT100
In the Idoc (type orders) the sending port is "SAPHS3".
I have configured the XI 3.0 IDoc Adapter as follows.
- IDoc Port "SAPHS3"
- I have loaded the IDoc Metadata
- ALE Distribution model in sending R/3 is defined
- In the Integration Directory I have defined a "service"
This was done by upload an existing business system
"HS3CLNT100" including the automatic generation of
communication channels.
This should "normally" be all, what I have to define.
PROBLEM
========
When SAP R/3 tries to send an IDoc into SAP XI it will fail. In SAP R/3 transaction SM58 I can see following message:
"No service for system SAPHS3 client 100 in Integration Directory"
I don't think, it's normal to configure XI business systems with the same name as the IDoc port!?
Thanks in advance
Klaus

Hi James,
yes in the IB (Configuration) I have generated a service under "services without partner". Service name is "HS3CLNT100" and he includes the generated receiver channels. Or do you mean something different?
Klaus

Idoc adapter- communiccation channel

Similar Messages

Maybe you are looking for