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

Similar Messages

XI IDoc adapter problem. MESSAGE.DUPLICATE_DE

I have a problem with the IDoc. When sending the IDoc from the PI to ERP - system throws an error (ta SXMB_MONI):
<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="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3><SAP:Error><SAP:Category>XIProtocol</SAP:Category><SAP:Code>MESSAGE.DUPLICATE_DE</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation <SAP:Error><SAP:Category>XIProtocol</SAP:Category><SAP:Code>MESSAGE.DUPLICATE_DE</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What could be the problem?

The HTTP code 500 indicates internal error in your application.
Check on to the stacktrace in
<local drive>:\usr\sap\XXX\YYY\j2ee\cluster\server0\log
check note number 804124 at service.sap.com
You can also check:-
Ping the receiver host from XI server.
Have a look at the SMICM->Trace file
Test the connection of AI_RUNTIME_JCOSERVER
HTTP 500 can be any problem at receiver side. Are you sure, that the payload fits to the receiver requirements?
Also i looked up this message "MESSAGE.DUPLICATE_DE" this comes when duplication of message takes place.
Try chaning the input data.
Venkat.

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

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

Configuration Problem on IDOC Adapter

Hi,
I am trying to configure the IDOC Adapter and am badly stuck.
On the sender system: I have configured
-RFC destination, ports and partner profile.
- I have also configured the SLD as per documentation
On the Integration Server:
-RFC Destination, Port maintanence(IDX1.
- Imported Metadata (IDX2)
My IDOC is getting created and is being sent properly, I can see that in WE02
But I cannot see it in Integration Server using transaction IDX5.
Please help.
Regards
Ramesh

Ramesh,
Try to refresh the cache
in Xi using transaction SXI_CACHE > delta Cache refresh.
Then go to Integration Server and Environment Cache Notifications.
Status should be green once you refresh the cache.
This may look a bit silly, but it worked for us.
(We used to get errors with SXI_CACHE in XI3 Service pack 9. Then we followed the steps of Checking Instalaltion part 1 as in XI3 install guide. Once we repeated these steps . SXI_CACHE worked and everything was fine).
To find what exacly is happening, try to send the IDoc from one R/3 to anotehr thro Xi.
The other R/3 will tell you the errors even if it does not show up in SXMB_MONI.
Hope this helps.
Thanks,
BG
Message was edited by: Bhaskar Ghandikota

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:
<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

File to Idoc Mapping Problem

Hi all,
i'm getting an error from SXMB_MONI in a scenario File to Idoc.
I have done the mapping from source file and Idoc CREMAS03, when i try to test from Integration Repository it's all ok, but when the scenario is executed i find this error in Idoc Adapter :
<SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
The field BEGIN in idoc structure is filled with constant value 1, than i dont understand the error.
This is the xml source file :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Vendor xmlns:ns0="urn:tbit40:workshop:group01:legacy">
- <Address>
<Country>IT</Country>
<Zip>001</Zip>
<City>ROMA</City>
<Street>SATTA</Street>
</Address>
<Currency>USD</Currency>
<SearchTerm>TEST</SearchTerm>
<LastName>GUIDA</LastName>
<VendorNumber>44332</VendorNumber>
</ns0:Vendor>
Any help is really appreciated.
Thanks.

Hi all and thanks for your answer.
My problem is that for what i can see all Idoc attribute (like the attribute BEGIN) are mapped with constant value.
In taget source i can see : BEGIN = Constant([value=1])
What i dont understand is why when i execute the scenario it ends with this message :
<SAP:P1>MSGGUID EF7E2140A08811DDBE1202004C4F4F50: Tag #TEXT found instead of tag IDOC BEGIN=</SAP:P1>
It seem to me that the tag BEGIN is not filled with value, i also tried to copy the source xml file directly from SXMB_MONI (from payload) and test it in Integration Repository mapping section, but here is all ok and the test end succesfully.

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

Basic Idoc Adapter Error - XI 3.0

Hi,
I am new to XI so excuse me if this is a basic question.
The scenario we have is File -> XI -> IDOC
When the message is processed into the IDOC Adapter I am getting the following error :
Control record must start with tag EDI_DC40 not E1LFA1M
Don't really understand this one as in the message mapping this segment on the target IDOC is disabled. It was my understanding that this segment is automatically filled by the IDOC Adapter.
Is there something I need to change in the Idoc Adapter to get this to happen ?
Kind regards
colin.

It is not a basic question, but it seems to be a common problem.
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

IDOC adapter Retry interval

Hi
I am doing File-IDOC scenario.
For each 5 min there will be new file coming to the FTP folder..sender File adapter needs to pick the file and send as IDOC to R/3.
Each file consist of multiple lines..so i am using IDOC bundling..so for each file i am sending aroung 50 IDOCs at a time toR/3..
I am using BPM for this scenario...( i know we can do this without BPM also...but i have to use BPM..)
if R/3 system is down...then i am waiting for 2 min..and through deadline branch i am canceling the process...assuming that receiver system is down..and throughing alert to support team to intimate the same...
Each adapter is having default Retry interwal...if that adapter fails to send to the receiver...by default it will try for 3 time..with time interwal gap of 5min(i think) between each retry..
For each 5 min i will get a new file...so i have mentioned 2 min for deadline branch...
what happens if the IDOC adapter succeded in seconed attemt.(i mean after 5min) to send to receiver (here R/3)..?
--> i am sending alert to support team...but IDOC has sent succefully..which should not happen..so either we have to decrease the IDOC retry interwal or need to increase the deadline branch inerwal...
Questions:
What's the default retry interwal for IDOC adapter??
Can we decrease IDOC retry interwal time as normal file adapter in Visual admin..??
if i increase the Deadline branch time interwal...it will keep on trying to send first file..so waiting status..if sencond file comes after 5 min...it will also wait status..will there be any problem...??
Thanks
Murali

>>What's the default retry interwal for IDOC adapter??
Can we decrease IDOC retry interwal time as normal file adapter in Visual admin..??
No. Idoc adapter is not part of Java stack and hence you cant alter any idoc adapter settings in VA.
When the Idoc adapter fails, the message fails in SXMB_MONI unlike other adapters which pass through SXMB_MONI.
So, incase of Idoc adapter the restart depends on the reprocessing the error messages in SXMB_MONI.
Usually the report to restart errror messages in SXMB_MONI is scheduled as a background job.
You need to check for that. But in most cases, the interval is a few hours rather than minutes.
Jai

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.

Assignment IDX1 port to sender idoc adapter ...

Hi gurus,
I have a big problem and I don't have any idea how to solve it. Please, help me.
I have a non-SAP system, regular SAP ERP and SAP XI and I need to transfer IDocs between them.
There is no problem to send IDoc from ERP to XI and forward it to non-SAP system. Unfortunatelly communication in opposite direction doesn't work. XI is not able to receive IDoc sent from non-SAP system because appropriate metadata can not be found in IDX2 cache.
In configuration of communication channel for sending IDocs to non-SAP (receiver idoc adapter) I selected IDX1 port that is directed to the ERP and it's worknig fine. I can send IDoc from XI to non-SAP.
But in configuration of communication channel for receiving IDocs from non-SAP (sender idoc adapter) is not possibility to determine any port. Does exist a way how to force sender idoc adapter to use some specific IDX1 port?
Thank you in advance for every reply!
Regards,
Zbynek

The IDocs are sent from non-SAP system by means of tRFC. Connection type of the RFC destination is type T (TCP/IP) and activation type is Registered Server Program.
If we sent the IDoc directly into SAP ERP (where the IDoc Type is known) everything is fine
Edited by: Zbynek Kabrt on May 19, 2009 8:59 PM

IDOC Receiver problem with 7.11 and ECC6

Hello,
we have a IDOC_2_IDOC scenario on old XI system which worked fine.
We are moving now to PI7.11 and get the problem, that all IDOCs in the receiving ECC6 system
go to status 51 "No status record was passed to ALE by the application"
It seems to be a problem of processing of too many IDOCs at the same time,
because if there is enought ime between the IDOCs the the procsing in ECC6 works.
Only if too many IDOCs are sent from PI to ECC6 then I get this error.
I have checked aRFC and tRFC options in SM59 but there is no difference.
IDOC packing is not activated on sending system and on PI.
At the moment the scenario should work as is worked on 7.0......
Any ideas which setting is different or where to look?
best regards
Werner

Hello,
which ALE settings do you mean???
on PI or receiving ECC6
PI:
here we only use SM59, IDX1, IDX2.... for IDOC adapter
ECC6: only partner profile INBOUND PARAMETER
On the sending R/3 system I can not change something.....and there was no change.
best regards
Werner

XI 3.0 IDoc Adapter Problem

Similar Messages

Maybe you are looking for