AEX - IFlow / ICO with multiple sender systems

[Former Member]

Hi experts,

we have two ERP test systems in our system-landscape, which are both sending IDOCs and Proxy calls to our PI system.

In our current PI system, we can use a wildcard (*) in the "Communication Component" in the "Receiver Determination" to focus the calls to one set of configuration objects, as the interface should behave the same way no matter which test system is committing the call. This works perfectly fine.

We are now migrating to a PO system. With ICOs / IFlows, we encounter the problem, that if we want to receiver IDOCs / Proxy calls from both systems, we would need 2 ICOs / IFlows.

Is there a workaround, or something that we are missing?

Thanks!

[Former Member · Accepted solution]

Hi Elias,

You will need 2 ICOs as you have 2 different sender systems and as part of IFLOW PI will need a sender system to be unique..

Regards,

Sriram

[Former Member · Accepted solution]

Hi Elias

Unfortuntely we can not use * as communication component in ICO . Hence you have to create 2 separate ICO for two diffrent sender systems.

Thanks,

Indrajit

[Former Member]

Thanks for all your answers.

I hope this gets changed. At least if no wildcards are allowed anymore, being able to add more than one specific sender systems to the ICO / IFlow would help a lot.

If someone finds a workaround to solve the problem with one ICO / IFlow, please let me know.

[Former Member]

Hi Elias,

Receiver determination will have a sender system, sender interface and a namespace...so why for proxy the Receiver determination will be one and for IDOC it will have another receiver determination.

When you say that u have put a * in the Receiver component name it will take whatever is the config(Collabaration Agreement) available for that Sender System, Interface and namespace and proceed further.

However with ICO/Iflows u will need to have a receiver mentioned.

Regards,

Sriram

[Former Member]

Hi Sriram,

sorry if my description was confusing. We are not trying to mix IDOC and Proxy Calls.

What we are merging into one configuration is for example:

• TestSystem1 sends ORDERS05 IDOC to PI -> gets mapped -> gets put to file system
• TestSystem2 sends ORDERS05 IDOC to PI -> gets mapped -> gets put to file system

In above example, mapping, target folder in file system, etc. is exactly the same. Only the sender system differs.

So for the example above we need on PI:

• 1 Receiver Determination
• 1 Interface Determination
• 1 Receiver Agreement
• 1 Sender Agreement (Optional)

On PO it seems we need:

• 2 ICOs / IFlows

I would like to channel both calls into one ICO / IFlow though, as it is very redundant to copy everything just because we got different senders (even when using "referenced communication channels")

Thanks!

[Former Member]

Hi Elias,

Yes you need 2ICOs/iFLOWs as per above requirement.

Regards,