Comparison between split Adapter in Seeburger and EDI Separator

Hello All,

Currently we are designing EDI interfaces using B2B Add-On.

I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.

In Seeburger Splitter configuration:

The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.

I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.

In B2B Add-On:

The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.

Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?

Your inputs highly appreciated.

Thanks.

Regards,

Sudharshan N A