Message already exist in called system

[Former Member]

Hi.

I have the following scenario

Picki´ng up a file with the file adapter and makes an ABAP mapping. Sending the message to the target system with Proxy usding the XI adapter.

I get the following message in the SXMB_MONI at the target system.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!-- 
 Call Integration Server 
--> 
- <SAP:ErrorHeader xmlns AP="_http://sap.com/exchange/MessageFormat"> 
<SAP:Context></SAP:Context> 
<SAP:Code p1="F5C16E2C70A24D800FC3D7B3E9899F39" p2="CENTRAL" p3="" p4="">PROTOCOL.MSGID_EXISTING_INBOUND</SAP:Code> 
<SAP:Text language="EN">Message ID F5C16E2C70A24D800FC3D7B3E9899F39 already exists in called system (pipeline CENTRAL)</SAP:Text> 
</SAP:ErrorHeader>

Can anybody expalin to me why I get this message?

The message do not get proccessed in the target system.

BR

Kalle

[Former Member · Accepted solution]

Hi,

Please refer to the below given thread. May be this will help:

[;

Regards,

Anshul

[Former Member · Accepted solution]

Already read that thread.

Did not help.

//Kalle

[Former Member · Accepted solution]

Had a simular problem.

We had it working in our DEV enviroment and not in our QA enviroment.

After checking our configurations we found out that we had deffrences in our HTTP destination in SM59.

DEV had the following querystring

/sap/xi/engine?type=receiver

QA had the following querystring.

/sap/xi/engine?type=entry

Changed it to

/sap/xi/engine?type=receiver

and it worked.

Not sure if that's your problem but you can always check.

//Andreas

[Former Member · Accepted solution]

That solved it.

Thanks.

BR

Kalle

[Former Member]

Did you find any resolution for your issue? I am also having a similar scenario and facing the same problem.