Using unique message ID to avoid duplicate messages

[#1]

Hi Experts,

we have ascenario SOAP to IDoc (to receive ORDERS), The requirementy is to avoid the duplicate meesages in PI sent by the SOAP client multiple times due to the network issues.

I have found some expaination in SDN

Ensuring Exactly Once Processing 
The SOAP message provided by the SOAP client must contain a unique GUID. This can be provided in a valid XI message header in the SOAP message header or specified in a corresponding query string in the URL.
If the SOAP client then receives an empty SOAP message in HTTP 200 as a response, this means that the message has been successfully persisted and will be processed exactly once.
If the SOAP client receives a SOAP fault or any response not in HTTP 200, it must resend the message until it receives an empty SOAP message in HTTP 200.
 
If the GUID is set by the SOAP client, you must set the Use Encoded Headers and Use Query String indicators.

But can you please explain what config we need to do in PI, where can SOAP client have the GUID and how the process will work.

Thanks in Advance,

MK

[Former Member]

In the SOAP sender communicatiob channel specify Processing Parameters

Under Quality of Service, specify how the message is to be processed by the Integration Engine

Exactly Once (asynchronous processing)

*If the client sends a GUID, execution is guaranteed exactly once. See also: Ensuring Exactly Once Processing

[http://help.sap.com/saphelp_nw70/helpdata/en/5e/164442c1a1c353e10000000a1550b0/frameset.htm]