Hi Rene,
What are you understanding by duplicity?, if your scenario is asynchronous you can set it with quality of service exactly once, EO.
If the sender sends two times the same message the PI cant know if the second message is the same because the message will be generated with different message ID,
The unique solution that i know if to do this control in the receiver system, or more complicatad to find an unique payload value between message, to stored it in a PI table (abap or java) and during to mapping to check this value in order to forward the message or to throw an exception.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.