IDOC ADAPTER

Hi,
idoc sender adpter lies on integration engine,,:thats y it dnt need an sender agreement and sender comm' chanell"then
1> why does a "receiver adapter needs comm channel and rec agrrement".
2>does it lie on integraton engine or not?
please let me know
Regards,
Swati

Hi swati,
When the IDOC is your sender then you do a ALE config from Sender R3 to XI system,i.e you create RFC connection,partner profies,ports,Function module for idoc generation etc. so when you are going to execute the IDOC2FIle scenario you just execute that function module in senderR3 and the idoc will be posted to XI.
But if idoc is in your receiver side then also you make an ALE connection from XI to receiver in this case you specify these ALE config parameters in receiver idoc comm channel so it will be fetched at runtime and the idoc will be triggered from Xi to Receiver.
Hope its clear to you now.
**Reward points if helpful
--Sankar Choudhury

Similar Messages

XI FILE(FTP) - XI- CRM(Idoc adapter) scenario - restart message

Hello All,
I have scenario as below.
FTP->XI->CRM
The sender adatper is File Adapter, FTP.
Recv. adapter : IDOC adapter.
In CRM, there were middleware settings for idoc processing.
For an interface, in XI, i had a problem in getting a file of 10 Mb in size, so the file is split and i have made the XI sender adapter 'Z_PRICE_NEW20061004*.txt', so it picks all files within 5 mins and i have almost 104 XML messages.
Now the problem is a quite no. of message are ended up with error status in outbouond process in XI.
How can i reporcess the message? As the file is deleted from FTP? i ahve to do anything with the failed message.
A quick help is highly appreciated.
Thanks in advance.
Best Regards,
Jilan Bhasha

Hi ,
This weblog will help you....
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
sekhar

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

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

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

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

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 Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Generated ADRMAS IDOC is
 <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
 <IDOC BEGIN="1">
 
 <EDI_DC40 SEGMENT="1"/>
 <xsl:apply-templates select="."/>
 </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

Time Zones problem in IDoc Adapter

Hello,
we have a problem regarding time zones. We send an IDoc from an external system to the XI IDoc adapter. the external system has only one time zone which is set to CET. Our SAP XI system as well as the op system is also set to CET and the same also goes for all user properties.
We need the value of "TIME_SENT" from the xml message header to achieve our mapping. This works out pretty good but unfortunately we find the wrong time in the xml message header, which is UTC in this case.
Does anyone know where in the J2EE engine or in the IDoc adapter this UTC date comes from and where to configure the time zone?
Thanks in advance
/Michael

hi once more:)
maybe check you j2ee too:
log on to
http://server:port/sap/monitoring/SystemInfo
then choose system properties for your server
inside you'll find user.timezone
check if this value is ok
Regards,
michal

Connecting of an external system by IDOC adapter

Hello everybody,
we want to connect an external (storage) system to XI by IDOC-Adapter.
In a scenario without XI the R/3 backend triggers the external system by RFC-Call (TCPIP-conncetion) and an program on the external system is called. This program executes an RFC-call on the R/3 to get the IDOC-informations.
IN the new scenario (with XI) the R/3 Backend sends the IDOC information to XI. The XI routes this to external system. An TCPIP-Connection is needed which calls the program from the external system.
But how should this work? The program can not (or should not) call the R/3 Backend directly but the XI.
What has to be done now? Has the program of the external system changed so that it can understand IDOC-structure directly?
Or do I have to implement a business process scenario to guarantee that the external system reads the IDOC data in XI (similar to "old" scenario?
Thanks a lot!

HI everybody,
thank you very much for your help. Now it es possible to send an IDOC from R/3 Backend and IDOC-Adapter via XI to an external system using the IDOC-Adapter.
But now the external system wants to send IDOCs back. So the communication is realised by using the IDOC-Adapter again. In this case we do not get the messages in XI. The conncection is ok (we see this in the Gateway), but the system gets an error in IDOC adapter (sys-log):
Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )LFS = external system (AS400).
In the RFC-Trace we find following information:
 **** Tra
Transaktions-Abbruch IDOC_ADAPTER 151 ( LFS 910 )ce file opened at 20060223 111414 W. Europe Stand, SAP-REL 640,0,109 RFC
======> Der Funktionsbaustein "EDI_FILL_SYIDOC01_FOR_RFC" ist nicht vorhanden
ABAP Programm: SAPLIDX1 (Transaction: )
Called function module: EDI_FILL_SYIDOC01_FOR_RFC
User: RFC_USER (Client: 910)
Destination: C01 (handle: 3, , {C322581B-EB47-43E7-87D7-4607C2873828})
SERVER> RFC Server Session (handle: 1, 95896538, {43FD899F-8993-0202-E100-00000A
SERVER> Caller host: LHMAS40A.INTRANET.SYS
SERVER> Caller transaction code: (Caller Program: SAPCPIC)
SERVER> Called function module: ARFC_DEST_SHIP
Can anybody help us?
Thanks a lot!
Florian

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

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

ABAP Proxy or IDOC Adapter?

Hi all,
In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
1. Oracle ->PI ->SAP R/3
Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
2.VAN->PI->SAP R/3
VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
3.SAP->PI->VAN
Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
Please suggest me which one is better in all the scenarios.
How to decide which is better for the above scenarios?
Thanks In advance
Venkatesh

>
venkatesh bs wrote:
> Hi all,
>
> In my project, we are using 3 system(SAP R/3(ECC 6.0), Oracle and VAN). Data has to synchronize between these systems.
>
> 1. Oracle ->PI ->SAP R/3
> Oracle system is sending Material master data to SAP R/3 ECC 6.0. At sender side I am using JDBC Adapter but at receiver side shall i go for IDOC Adpter or ABAP proxy? If I go for ABAP server proxy I need to create message type for material master in IR and then I have to write code in abap to insert MM data into tables in R/3. Please suggest which one will be better IDOC adpter or ABAP Proxy?
>
> 2.VAN->PI->SAP R/3
>
> VAN is sending Invoice data to SAP R/3. At sender side I am using Seeburger Adapter. At receiver shall i go for IDOC Adpter or ABAP proxy?
>
> 3.SAP->PI->VAN
> Sap is sending PO data to VAN. At sender side Shall i go for IDoc Adapter or ABAP proxy?
> Please suggest me which one is better in all the scenarios.
> How to decide which is better for the above scenarios?
>
> Thanks In advance
>
> Venkatesh
Material Master - MATMAS
Invoice - INVOIC01
PO - ORDERS
wouldnt the above IDoc suit you?

PI 7.1 Ehp1 IDOC adapter message packaging - package options on sender side

Hi guys,
I am trying to use the new IDOC adapter PI7.1 Ehp1 functionality for packaging the IDOCs in single PI message, instead of using Collect pattern in BPM. I have configured IDOC sender comm. channel with Sender Agreement as well. So far, so good, but I am wondering if the packaging done on PI side should be the same as the packaging parameters on sender side...
What I mean? Do I have to set the Pack. Size (we20) to be the same as the one on PI, and do I have to use "Collect IDocs" as
Output mode (also found in we20) .. I guess "Yes".. Actually what I got also is that I have to schedule RSEOUT00 if I am using the option to Collect IDOCs, right ? Can execution of RSEOUT00 be "plugged" somehow to be executed after bd21(Creation of IDocs from change pointers) execution ..?
If you have any personal experience on this - please share it with me
Thanks & Best Regards,
Lalo

I am wondering if the packaging done on PI side should be the same as the packaging parameters on sender side
Do not have to be same.
Think of this way: there are two containers carrying water: A for ECC and B for PI (specified in communication channel), you are defining the size of the containers.
If Size of A > B, then, One full A will need more than one B to handle, means multiple PI messages will be created.
if Size of A < B, One PI message is enough to handle incoming package.
For sure in partner profile of ECC, you will need to enable IDOC packaging and specify the size (container A).
Regards
Liang
Edited by: Liang Ji on Jun 8, 2010 3:30 PM

Sender option grayed out in IDOC Adapter PI 7.1

Hi All,
I have heard of IDOC packaging in the PI 7.1 for which we need to create a sender channel in XI and sender agreement.
but the idoc adapter has the sender selection grayed out. Is there any other configuration which needs to be done.
Rgds
Aditya

Hi,
yes you have missed something - exactly what i am not able to guess.........just check whether the SAP BASIS 7.10 component was correctly deployed in your PI 7.1 system because without EHP1 also, at least you should be able to configure sender IDOC adapter............
maybe you need to do the readiness check of your PI 7.1 system again.........try restarting your PI server completely and then check if there is any error in the startup logs.........if there is no error, then again try to configure sender IDOC comm channel in ID.
Regards,
Rajeev Gupta

IDOC ADAPTER

Similar Messages

Maybe you are looking for