Decoupling IDocs and iFlows

[HarshC]

We are on PO 7.5.

When we get IDocs from SAP, a generic IDoc like ORDERS05 can have several potential receivers(in the RD condition).

Eg: A purchase order IDoc(ORDERS05) coming out of SAP, might be routed to one of the following:

1) One of many vendor via a direct connection

2) One of many vendors via a VAN

3) A different SAP instance for intra company transactions

This causes the ORDERS05 iFlow to have many receivers in the RD condition. Such iFlows become difficult to support due to increased complexity.

Is there a way to avoid a common iFlow for an outbound IDoc type?

Can we do something with parties and partner profiles to create partner specific iFlows?

Thanks,

Harsh

[adam_kiwon3 · Accepted solution]

Easy: https://www.integration-excellence.com/virtual-receiver-with-idoc_aae-for-sap-pi/

[HarshC · Accepted solution]

Thank you. Will check this out.