Doubt about IDOC Adapter

Hi all,
i'm using idoc adapter for generating IDOCS from R/3, and my scenario is: IDOC->XI->File. this is working fine, in R/3 i've got partner profiles for diferent vendors(suppliers) and they are configured for create idoc message in R/3 and all this message are caught by XI from my scenario and generate the corresponding text file.
but now suppose that I need another scenario because i need to send purchase orders by mail instead file to some of my vendors in R/3. the scenario would be IDOC->XI->Mail.
for both cases i would use ORDERS05.
i can't undertand how XI knows wich scenario have to use, if there's nothing from R/3 that tells XI which scenario should be used.
thanks, Fabian.

Thanks for responses, I know what should i use to do what i wanted. but i've tried to make a condition in the receiver determination and it's giving me an error saying that 'No receiver could be determined'.
i've searched in other threads and i have seen that utilizes xpath to make conditions
what i have done is add a condition in Configured Receivers as '/p1:ZORDERS2/IDOC/EDI_DC40/RCVPRN = 0000010598'
because depending on the partner, i want to use either one or other adapter (file or mail)
do i have misedd something?

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

Doubt on Idoc adapter parameters

Hi ,
      I need one more clarification on Idoc adapter parameters :
1.while configuring for IDOC adapter in communication channel , we have an option
called "APPLY CONTROL RECORD VALUES FROM PAYLOAD" doubt arises here
what actually this mean,and if this check box is ticked what values will be taken from payload and where will be they applied?
                       Plz clarify answers will be definetely rewarded.
                                                                                Regards,
                                                                                Vinod.

Hi vinod reddy ,
If u want to add values to the control record , u have to select the APPLY CONTROL RECORD VALUES FROM PAYLOAD checkbox in the communication channel. When a new communication channel of type IDoc is created, the flag is set by default. If the flag is not set, the
settings comply with XI 2.0
This following websites clearly clarifies u'r doubt with detailed description with fields :
Fields of the IDoc Control Record
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Configuring the Receiver IDoc Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm
How to.......Sample IDoc XI Scenarios
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
cheers!
gyanaraj
****Pls reward points if u find this helpful

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

Doubt Regarding IDoc Adapter

Dear Gurus,
In IDoc to XML conversion scenarios, we never use Sender Communication Channel because the IDoc adapter sits on the ABAP stack and the conversion is done by the IDoc adaper in the Integration Server.
Then why in case of the reverse scenario , i.e. XML to IDoc conversion we use Receiver Communication channel and the IDoc adapeter explicitly? Why can't that IDoc Adpater that sits on the ABAP stack convert the xml file into IDoc format?

Hi Shweta,
the reason for this is:
The adapter at the inbound channel is located before the Integration Server pipeline and calls this pipeline. The adapter at the outbound channel, however, is called by the pipeline, and can therefore be regarded as part of the pipeline.
The connected systems transfer or receive IDocs through their IDoc RFC interface.
if you check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
and read the Integration section and try to understand the pipeline flow, as the names are not understandable(viz. receiver determintaion, mapping etc.) in the diagram.
you will get the clarity after reading this..
Sachin

Doubt on Idoc Adapter

Hi
I was going thru the help.sap for IDoc adapter.
Implementation Considerations
Only use the IDoc adapter to integrate SAP systems with the Integration Server if a scenario of this kind suits your requirements.
in
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
what does it really mean. I understand where the idoc adapter is placed and y no sender agreement is req. But this phrase in help.sap is confusing.
Can i take all ur help in understanding this?
thkx
Prabhu

Hi,
IDOC scenarios are used when you have to transfer business data TO or From SAP R/3 . Itz is still the most preferable solution. But if you want ackowledgements to be sent back for ex: a business data back can it be acheived through idoc >? No. That where rfc comes into picture. Itz only effective during assynchronous communication.
I suppose it was in this conext of application of a idoc adapter that was illistrated.
correct me if itz wrong
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Doubt about idoc meta data

hi this is seshagiri. i have one doubt while in sending idoc to xi server in the idoc to file scenario, can we do with out configuring metadata in idx2.
if can we do means wat is the procedure.
please clarify me
thans & regards
giri

Hi Sesha giri,
    If you are dealing with Idoc to File Scenario...you need to create
1) RFC Destination in R/3 pointing to XI.
2) Ports in R/3.
3) PartnerProfiles
   we need to send idoc from R/3...so we have to do ALE configuration.
   Please see the below link for more details.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Hope I am clear.
Please let me know if you have any queries...!
Thanks and Regards,
Chandu

Doubt About Soap Adapter

Hi Experts,
I have one doubt Here iam Implementing SOAP To RFC Scsnario Using EP(WebDynpro).
Here Should I Generate WSDL File in Integration Directory of XI.
Or Can we generate In WebDynpro Appln.
Please let me know
Regards
Khanna

Hi,
Look into this article, It describes exactly what you want,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5f3ee9d7-0901-0010-1096-f5b548ac1555
Create the WSDL for your message interface in the integration directory and then create a Webservice Model in WebDynpro and finally deploy this on your portal.
Regards
Bhavesh

Process flow of IDoc adapter in SAP PI

Hi Experts,
can any one pls send me about IDoc adapter in SAP PI/XI, which covers a complete info of IDoc adapter.
i mean complete in and out about IDoc adapter.
with rgds,
MF

Hi
If you do a search, you will get lots of material.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
IDOC Adapter
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/idoc%252badapter
These links should help you out
Thanks
Saiyog

IDoc Adapter configuration for very high volumes

Hi PI Expert,
I'd like to have some tips about Idoc Adapter configuration in case of very very hudge volumes in "file to Idoc scenario" (adressing ECC) : How to optimize Idoc transmission time PI -> ECC ?
=> parallelization PI -> ECC by using differents comm channel IDocs with differents RFC destinations ?.
=> some other technical parameters in adapter IDoc
=> ...
Thanks a lot
Best regard.
Etienne

Hi,
for sure idoc bundling will greatly increase performance: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken]
If you are in 7.1 you can also leverage message packaging: http://help.sap.com/saphelp_nwpi71/helpdata/en/46/79e8e13872275ae10000000a11466f/frameset.htm
Regards,
Sergio

Doubt in Sender IDoc Adapter

Hi Gurus
I have doubts regarding the sender IDoc adapter.The sender IDoc adapter is present by default and we do not create manually. the qos of this is EO by default.
How can we change the QOS of the sender IDoc adapter? do we have to maitain any settings on the R/3 side, please explain??
thanking you

Dear Abhinav,
Check my comments in this forum thread:
[IDOC Serialization|Re: IDOC Serialization in PI]
Regards
Praveen K

Doubt about RFC Destination in FILE to IDOC Async scenario

hi
In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
Any specific reason.
Thanks in advance.

First you need to have a clear understading of how the idoc adapters works.
In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
Hope this answers your ques.
cheers
*Raj*
*POINTS IF SATISFIED WITH ANSWER.

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:
<i>CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only</i>
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

** Port is missing from the IDoc control record (Receiver IDoc adapter)

We are using a File to IDoc scenario and in the idoc sap sender port is not coming due to this IDoc posting is failing. Could any one tell us why idoc adapter is not able to get SAP port.
The following is the error message in SAP side.
Status : 56
IDoc: 0000000006188579 Status: IDoc with errors added
EDI: Partner profile inbound not available
Kindly help me friends.
Thanks,
Jagathees P.

hi,
>EDI: Partner profile inbound not available
this error message means that there is not partner profile
configuration for this IDOC (you configure it in WE20 of ERP/R/3 )
or your XI system is configured to post to a wrong partner profile
(if you fill your partner data in a mapping for example)
so it's one of the other for sure - check it/change it and it will work
for more info about IDOCs and XI you can check my book:
www.sap-press.com/product.cfm?account=&product=H1935
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Doubt about IDOC Adapter

Similar Messages

Maybe you are looking for