Virtual Receiver with multiple Identifiers in IDoc_AAE --> PI --> 3rd Party Scenario

[JaySchwendemann]

Dear all,

we are currently fiddling with property "ResolveVirtualReceiver" as mentioned in https://launchpad.support.sap.com/#/notes/1941832

I have a scenario where a GTS sender system sends custom declarations through /SAPSLL/CUS_EXP IDocs to our PI system which then routes that to the German Customs server. The IDoc are generated with partner type "GB" and multiple possible partner values representing customs offices like DE005864 and DE005866. However, the resulting data should only ever being routed to a single receiver system. (I know that it might then be better to configure GTS to create the IDocs with partner type = "LS" but since I don't know if that is even possible and I am a curious guy I want to concentrate on the current situation and a solution on PI for this issue)

Now my first, simple hearted course of action was to try setting up a party in PI as follows:

• Party Name = Customs
• Party Identifiers Agency[1] = GTS_DEV
• Party Identifiers Schema[1] = ALE#GP
• Party Identifiers Name[1] = DE005864
• Party Identifiers Agency[2] = GTS_DEV
• Party Identifiers Schema[2] = ALE#GP
• Party Identifiers Name[2] = DE005866

To my surprise, this resulted in an error "ConsistencyException:Agency/scheme pair GTS_DEV | ALE#GP must only be used once in the current party"

I then looked a little around and stumbled accros this helpful blog https://www.integration-excellence.com/virtual-receiver-with-idoc_aae-for-sap-pi/ bringing me to the idea to create two parties, namely "Customs_Office_A" (DE005864) and "Customs_Office_B" (DE005866) and assigning them the respective Identifiers.

I also made the following changes to the iFlow:

• Virtual Receiver Party = *
• Virtual Receiver Communication Component = [empty]
• 

The iFlows Receiver is currently set to "Customs_Office_A" with communication component "CustomsProcessing". Only there i configured the receiver adapter (FTAM Adapter by 3rd party vendor).

This setup works but I don't think it's ideal

My questions

1. Is there a way to overcome the limitation of not specifying multiple agency / schema / value triplets per party? I read about https://launchpad.support.sap.com/#/notes/1707103 but that seems dates (Visual Administrator anybody) and only valid for RNIF anyways.
2. Is there a better way to support such "multiple non LS party type senders --> to --> one technical receiver" than the one I came up with? I particularly find it irretating that I have a "dangling" party (here "Customs_Office_B") that I obviously don't use in any iFlow, which however is needed nevertheless to have PI even acceppt the IDoc from GTS
3. I also know about https://launchpad.support.sap.com/#/notes/2178769 but I think this is also coming short in terms of scalability. I don't want to have all "Non LS" IDoc traffic routed through Customs. But maybe I overlooked something here?

Many(!) thanks and kind regards

Jens

[kavitha_rambabu]

Hi Jens,

Though this is a little older post, I have the same situation where I want to maintain multiple Business components for a party and I am not able to configure it with the same combination of Agency and Schema. How did you manage to achieve this? One way is to create One Party for each BC but I am looking at using One party for multiple entities of a partner.

Your response is appreciated.

Thanks,

Kavitha