1:N multi mapping for message splits going to wrong receiver interface

[Former Member]

Hi,

We are in the process of upgrading to PI7.11. Our scenario is 1:N multi-mapping for message splits.

We have one Receiver Determination and Interface determination with multiple receiver agreements.

The message is sent to PI from an R/3 system using the ABAP proxy. The source message produces X number of messages depending on the data to the same receiver. For some reason, when certain messages are produced from the mapping, it always defaults to the same receiver interface.

Has anyone experienced similar issues?

Any help is greatly appreciated.

Thanks and regards,

Duke

[srikanth_srinivasan3 · Accepted solution]

If my understanding of your scenario is right, your interface determination must contain the conditions for splitting.

You may have to revisit this as this could be due to conditions satisfied for more than one intended receiver.

-

Srikanth Srinivasan

[RaghuVamseedhar]

Hi Duke,

Please pay attention to this point, When different Service Interfaces are used to send files to different target locations, we have to create different Receiver Agreements. Accordingly, each Receiver Agreement will refer to a different Service Interface and also to a different communication channel. Please have look at Parge 8 [Link1|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?quicklink=index&overridelayout=true] .

Regards,

Raghu_Vamsee

[Former Member]

Thanks for the replies.

What we discovered was that when you do a 1:N mapping and one of the target messages is disabled, this causes an issue in the routing of the receiver interface for the subsequent messages.

For example, if my 1:N mapping has 10 target messages and message 8 is disabled in the mapping, message 9 and 10 does not get routed correctly. In PI 7.0 this was not an issue.

Thanks again,

Duke

[srikanth_srinivasan3]

Good that you posted the root cause.

Thanks.

Srikanth Srinivasan