Professional Documents
Culture Documents
See Also
Setting up System Connections for hybris-SAP Solution Integration
Defining an SAP Base Store and Global Configuration
Setting RFC Destinations and HTTP Destinations
Types of Communication
Synchronous communication with SAP ERP: Examples: Synchronous order management and synchronous pricing. RFC calls are
used to communicate with the back end.
Asynchronous communication with SAP ERP: Examples: Asynchronous order management and master data replication.
Communication with the back end occurs through hybris Data Hub using HTTP as the communication protocol. Messages transferred
between the SAP back end and hybris Data Hub are of content type IDoc, and messages transferred between the hybris Data Hub and
hybris are of content type ImpEx.
Synchronous communication with SAP CAR or SAP hybris Marketing (SAP hMA): The communication protocol used is HTTP.
Messages transferred between hybris and SAP CAR or SAP hybris Marketing are of content type OData.
The SAP IDoc inbound adapter receives the IDocs and creates Spring integration messages.
The messages are routed to the mapping services provided by the SAP extensions.
The mapping services create raw data fragments and route them to hybris Data Hub.
hybris Data Hub transforms the raw items to canonical items and on to target items, and publishes the target items to hybris Commerce
Suite.
5. With the processing of the ImpEx data, hybris services, interceptors, translators, and events are used.
In keeping with the hybris AddOn extension concept, the hybris-SAP solution integration extends or exchanges existing views, data
transfer objects (DTOs), and facades of the hybris Commerce Accelerator.
The SAP facade layer communicates with the SAP business objects (BO) via SAP services. The BO layer is used for interaction and
presentation. It provides business functionality via well-defined interfaces in a back-end independent manner.
The SAP BO layer communicates with the corresponding SAP back-end (BE) objects through the BE layer. The implementation of the BE
layer is back end-dependent, that is, the integration can handle communication with different back-end systems. Currently, only SAP ERP
is supported as a back-end system.
The SAP BE layer communicates with the SAP back end via RFC by using the Java connector.
Synchronous and asynchronous order management scenarios require common configuration data. This configuration data is maintained
in hMC/Backoffice, and is stored in the hybris core database.
When an administrator saves the configuration in hMC/Backoffice, this triggers the Data Hub adapter, which in turn transfers the changed
configuration data to hybris Data Hub. A data feed receives the stream and puts the data into the SAP configuration pool.
The configuration data can be accessed in hybris Data Hub by using Java API or Spring Expression Language (SpEL).