SAP Integration with Hybris primarily involves - asynchronous master data replication from SAP to Hybris, asynchronous order replication* from Hybris into SAP and the downstream flow of various order statuses from SAP to Hybris.
While Datahub can directly communicate with SAP ECC over HTTP/IDOC-XML for master data replication into Hybris, it is more important to see how the existing integration architecture is established via an ESB like PI and how Datahub with its data integration capabilities fits into the overall integration landscape. It so happens that master data replication from ECC into downstream applications, in majority of cases, is already happening via PI. Instead of creating multiple master data distribution models for various receivers, master data is sent out to PI from which it is routed to multiple downstream applications taking care of target transformations and target technical protocol conversions. In this case, Hybris or E commerce Platform can be added as one new receiver in existing master data IFLOWs with relevant routing conditions.
The same approach holds good for various order statuses from SAP to Hybris. Similar to master data, order confirmations, invoices etc. are happening via PI and Hybris or E commerce Platform can be added as one new receiver in existing IFLOWs with relevant routing conditions.
The reverse flow is applicable for asynchronous order replication from Hybris into ECC:
The apparent advantage with this is that we are not building point to point interfaces with Hybris but routed through enterprise-wide ESB and the new Hybris-SAP Integration fits right into existing integration or enterprise architecture and as per the established interface design patterns.
* (in case of Asynchronous Order Management - AOM Scenario)