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.

Similar Messages

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

File adapter problem - message in RWB HOLDING msg status

Problem in XI File adapter recver comm channel.Getting msg in RWB Adapter Engine HOLDING status.
1. No explaination in RWB Details tab, of why status Holding.
2. File does not get created, because of Holding status.
3. Cannot Resend or Cancel in RWB the message.
Sometimes the msg goes through and other times does not and is stuck.
File Adapter Parms set as:
Connection Mode: Per File Transfer
Transfer Mode: Text
File Adapter setting Max concurrency = 1 would that have anything to do with it?
File Construction Mode:Create
Put Name: Direct
Empty msg-handling: Write Empty File
Type: Text
Any ideas Why holding? and Where to see more details. 

Hey
exact same issue has been discussed today on SDN.anyways have a look at the following blog
/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Thanx
Aamir

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

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

IDOC adapter message limitation Status 64

Hello,
we have implemented an IDOC R/3->XI->R3 scenario.
Sometimes it happens, that the sending system generates a hugh number of idocs.
In this case, the IDOCs are posted to the receiving R/3 system, but stay on status 64 which says,
"...to few dialog processes...."
So the receiving SAP system has to few processes to start the processing of the idocs.
But we can no enhance the amount of the processes.
Is it possible, to limit the calls of the IDOC adapter
or to schedule the idocs, or to make a package?
This should be done on XI!!!!
I have read the QUEUE option, but we are working on 4.6BASIS, so this did not solve the problem.
best regards
Werner

Werner-
This situation can be handled using some variations to your suggestion of handling it in XI.
1) In the Partner profile of the target R3 system, use the option 'trigger by background program' in the inbound parameters. This way, the IDOCs will be created in the database, syntax checked and will be set to status '64' but with a different message (mostly No filters....). At this point, we are not even trying to post the IDOC to the application, which takes the most processing time.
2) Then in your traget SAP system, schedule program RBDAPP01. There are various options available to restrict your selections. By scheduling this program to run in regular intervals, you can process IDOCs which are in status 64, there by re-processing them if some failed during the last run because of lack of processes.
Some additional information on performance improvment:
RBDAPP01 is an interesting program, because it allows you to parallel process the IDOCs plus process them in packets. That is, instead of processing IDOCs one by one, you can make the program to use all the available free processes to process the IDOCs in parallel. This will greatly reduce your processing time.
If you see, this program has a tab called 'Parallel Proc' (assuming you are logged on in English). You can activate the check box 'Parallel Proc. Active' and choose a 'Server Group'.
Now, before using this option, you need to understand that this program will occupy all free DIALOG processes. Which means no process will be available for users to log on (even admins) while the program is busy posting IDOCS. However, this limitation can be overcome by fixing a system parameter on the server group which will limit the number of processes to be used by this program. For e.g., in one of my implementations, we set up the profile parameter in such a way that out of 13 dialog processes available, the program will always leave 5 processes free thereby occupying only seven free processes max.
This setting was done by the basis team and probably you or your basis team already know about it. If not, let me know, I will try to find it out from our guys here.
Hope the above explaination help. For more information check note 399271 and other related notes for RBDAPP01 PARALLEL PROCESSING.
KK

XI 3.0 SP 20 - Problem with adapter-specific message attributes

Hi everyone,
I am using XI 3.0 SP 20, in SP 17 i read who SOAP adapter and mail adapter have additional adapter-specific message attributes in the message header
But in my XI SP20 dont have that function.
There arent problem in installation of SP20 (no show errors).
Can anybody tell me what is happening? Why dont have "adapter-specific message attributes" ?
Thanks

Hi,
you have to import the SAP XI content, SAP BASIS 6.40 have to be updated. Because the new attributes for adapters are saved in the Adapter Metadata located in the Integration Repository. If you have not update the content, you will not be able to find new options.
Start IR and navigate to the SAP BASIS 6.40, double click on this SWCV and click on the Details tab, you should be able see which Support Package the SAP BASIS has at moment. Update it to SP20 if it is still SP17. You will be able to see the required new attributes in Mail Adapter.
regards,
Hai

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

Message split on adapter engine for the java based IDoc adapter

Hi Guys,
Do you know if message split on adapter engine is available for the java based IDoc adapter on the single stack (PI 7.31)?
I'm getting such exception when I try to post 3 IDocs
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: Invalid XML 1.0 character encountered within IDocXML for type <ns0:Messages>:
state=EXPECTING_IMMEDIATE_TAG_END, charPosition=68, lineNumber=1, columnNumber=69, invalidChar=U+0078,
sourceSnippet=...UTF-8" standalone="no"?><ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><...
^
Mapping is one to many.
Each IDoc content has been compared manually against the xsd schema and it was fine.
I know that old way of modifying xsd is still possible.
Best regards,
Wojciech

Did you find a solution to this? Having a similar error right now.
Thanks and kind regards
Jens

How to get rid of messages in idx5 idoc adapter

We are having a lot of messages in idx5 (327828 for a particular date). When I go to sxmb_moni "Monitor for processed xml Messages" I do not find these messages there.
We are running the archiving/deletion reports and I expected theese to take care of the Idoc Adapter messages as well. Is this not the case? Are there separate archiving/deletion jobs for the idoc adapter? How do I get rid of the messages in the idx5 xml messages in the idoc adapter?
When running the report RSXMB_SHOW_STATUS this is today (after archiving/deleting all messages older then one day) showing good 30.000 messages in the database - and do not show the huge number of messages in the idoc adapter.

The baseball is probably the symbol assigned to you in Address Book - take a look and see. It appears on all your sent mail in Mail, but not on the messages as they appear to recipients, so don't worry about it too much. If you don't like it, you can remove or replace it through Address Book.

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

Messaging Bridge/Resource adapter problem on Solaris?

 Has anyone successfully used the supplied resource adapter and messaging bridge
 on Solaris? We seem to have problems getting the resource adapter to be bound
 properly. After creating a connector through the admin console (using any of the
 weblogic supplied jms-*-adp.rar files) the element shows up in the JNDI tree but
 has no object information associated with it - which I assume means it is not
 bound. The following error shows up in the weblogic log file:
 ####<Jan 24, 2003 6:28:03 PM CST> <Error> <Connector> <fssun02> <AdminServer>
 <ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <kernel identity>
 <> <190004> <ManagedConnectionFactory not found for jndiName eis/jms/WLSConnectionFactoryJNDINoTX.>
 We are using WL 7.0.1.0 and Solaris 2.8 (8). With the same configuration on Win
 2K everything works properly. Classpath's etc all seem to be correct. Any ideas?
 thanks,


I finally got my Messaging Bridge (Tibco to a WLS Cluster) to work. See my post 3 messages before yours - to which no-one responded... :-(
 So here goes with my suggestion based on what I have done.
 1. Create a Distributed Destination for the WLS queue and "auto deploy" it your cluster. (Read the manual on how to do that, it is quite straightforward).
 2. In the Local Bridge Destination, put :
 Connection URL - nothing
 Initial Context Factory - weblogic.jndi.WLInitialContextFactory
 Connection Factory JNDI Name - <your JMS conection factory name>
 Destination JNDI Name - <the JNDI name given to the Distributed Destination>.
 I hope that works.
 Andy

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
 I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

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

XI IDoc adapter problem. MESSAGE.DUPLICATE_DE

Similar Messages

Maybe you are looking for