SOAP to RFC message duplication

[Former Member]

Hi,

We are working on SOAP to RFC scenerio with Integrated Configuration.

It is synchronous scenerio.

But one of the fields in the RFC is getting posted twice in PI.

Can you please let me know the possible reasons for this?

Thanks and regards,

SDN User

[iaki_vila]

Hi,

Grzegorz has right in this issue. I only find two possible reasons for this problem:

1. The most usual is that your PI has receiving two time the message from the sender because the sender is sending two times the same information. Solution: To Speak with the sender system in order to avoid this issue. Another solution if to identify that message is duplicated in the RFC but in PI you have the message dupplicated.

2. You have a receiver determination with multiple conditions. You have the configured receivers in that way that the condition option send two times to the same RFC (Weird).

Regards

[Former Member]

Hi Inaki,

Thanks for the reply.

2. You have a receiver determination with multiple conditions. You have the configured receivers in that way that the condition option send two times to the same RFC (Weird).

There is only one receiver configured in the receiver determination and no condition is imposed in it,that is,it is the standard receiver determination.

Can you please help me?

Thanks and regards,

SDN User

[iaki_vila]

Hi,

Have you check the Test Option in the request mapping (operation mapping or message mapping)?. Copying+paste the payload from the payload monitorization (sxmb_moni transaction) and check if the problem is a mapping issue.

Sorry, you speak in you thread title about "message duplication" but later you speak about "field duplication". How is it really being duplicated?

Regards.

Message was edited by: Iñaki Vila

[Former Member]

Hi Inaki,

Thanks for the valuable help.

The message is posted twice in PI.

Can you please help?

Thanks and regards,

SDN User

[former_member184681]

Hi,

Is the message also duplicated in the sender communication channel monitor? If so, the message might have been sent twice from the sender system. As a result, you should analyze the sender system logic, not PI itself, to find the error.

Regards,

Greg