Is iflow a must to set up a B2B interface?

[Former Member]

We are making the switch from seeburger to B2B add-on. We have a scenario where a trading partner sends us a 850 to our SAP system.

With the new B2B add-on, looks like this is a two step process:

1. AS2 Sender to EDI-Separator Receiver (we can also send a 997 in this step by checking the box).

2. EDI-Separator Sender to IDOC.

Since this scenario would always be two steps, we cannot implement this without iflow?

[Former Member]

The receiver and sender EDI separators know each other using some of the header identifiers. Figured this from one of the other blogs here. Thank you very much.

So IFlows can be avoided for most B2B scenarios. Many blogs referencing iflows while explaining B2B concepts is misleading but I am sure that was not their intention.

[Dimitri]

Hi,

iFlows are a graphical representation of an Integrated Configuration object (ICO). There is no need to have an iFlow in any case.

You can create B2B processes without having iFows in place.

Kind regards,

Dimitri