1

2

3

pricing) 4 .In general.g.g. Flexible scenario: mainly asynchronous communication  With option to choose synchronous communication for certain functionality (e. Tightly coupled: synchronous communication  Integration method often preferred in B2B scenarios as well as with customers who heavily invested in SAP back-ends (e. configuration) 3. complex pricing. these scenarios exist:  Loosely coupled: asynchronous communication  Integration method often preferred in B2C scenarios 2.

Receives and sends data via hybris data hub asychronously (IDoc)  Can access SAP ERP or other backends such as SAP CAR and SAP CEI synchronously (RFC and OData)  Integration to above systems is enabled via SAP extensions. integration via direct calls and provides data model extensions to hybris hybris Data Hub  Receives and sends data to SAP Systems or hybris (data replication in both directions)  Can be used to also connect hybris to non-SAP Systems 5 . delivered with hybris commerce platform  SAP extensions enable data replication.Examples for synchronous communication:  Synchronous order management  Synchronous pricing Examples for asynchronous communication:  Asynchronous order management  Replication of product master data  Replication of customer master data hybris commerce platform .

Discovery and Targeting. target groups can be created Target group holds different types of members (either ERP accounts. CRM business partners or CEI Interaction contacts Initiative defines follow-up actions for a Target Group (Multiple Initiatives per Target Group are possible) 6 .SAP Customer Activity Repository (optional):  Provide access read POS (Point of Sale) Data  Show shopping data (POS transactions) from physical stores in addition to the shopping data from hybris SAP Customer Engagement Intelligence (optional)  Web Shop personalization by customer segments  Inside CEI    Out of Audience.

7 .

8 .

9 .

10 .

Data Hub Overview  Process fragmented data and consolidates before sending to a target system  Ease composition of data from external systems into any hybris core system and vice-versa from hybris core to any external system. like SAP ERP backend  Executes three major steps:    Data Import (raw format) Composition (canonical format) Publication (target format)  Technically bases on hybris Core+ platform with REST-based APIs  Includes Spring Integration in Data Import processing Examples:  Send Product Master Data from SAP ERP to hybris  Send Orders from hybris to SAP ERP 11 .

Events/Translators In inbound processing the data returned by the Data Hub is done via Impex. DataHubOrderCreationTranslator) raises an business event and notifies a waiting business process 12 . the usage of the translator concept allows to execute custom coding.g. a specific translator (e. In additon to the sole posting of data to the database. Example: An order is replicated from ERP to hybris.

xml files  Graphical Tools 13 .How does the data actually get into the database: Inbound process continued  Data Hub transforms raw items to canonical items and then to target items. file. E-Mail. which are published to hybris  During impex data processing. interceptors. ftp. Web Services. hybris services. translators and events are used Spring-Integration is based on the Enterprise Application Integration Patterns EAI – Enterprise Application Integration Patterns Architectural principles to integrate a set of enterprise computer applications (Wikipedia)  Message with Header and Payload  Channels with different formats and behaviors  Message end points       http.… Transformers Filters Splitters Service Activators Channel Adapters  Configurable in –spring.

g. SendOrderToDataHubAction) is triggered  Process engine action calls a SendToDataHubHelper (e. DefaultSendOrderToDataHubHelper)  SendToDataHubHelper calls and RawItemBuilder (e. DefaultRawHybrisOrderBuilder) to construct RawItems  SendToDataHubHelper calls DataHubOutboundService 14 .g.g.How does the data get to the outbound channel  Process engine action (e.

this is return to ERP ALE and the IDoc gets status failed in IDoc outbound in ERP. 15 .When an error occurs at any place in the processing chain.

16 .

17 .

18 .

19 .

DTOs and facades of the commerce accelerator. It provides business functionality via well-defined interfaces in a back-end independent manner. The implementation of the BE is back-end-dependent.  The Business Objects communicates with their corresponding Backend Objects (BE). The Business object layer is used for interaction and presentation.  The BE communicates with the SAP Back-End via RFC by using the Java Connector.  The SAP facades communicates with SAP services  The SAP Services communicates with Business Objects (BO). - 20 . Thus the SAP Integration can handle communication with different Back-End Systems. With the hybris AddOn Extension concept the SAP Back-end integration extends or exchanges existing views. Currently only ERP is implemented.

21 .

sap. SAP Master Data Module The SAP Master Data Module provides the integration of the SAP ERP master data (customers/contact persons/consumers.g. The module id is defined as property in the project. products and stock. localization keys in property files or configuration fields in SAP Configuration) or for enriching tracing information (e. authority traces). 22 .Module The module id represents a (business-) functional unit (named 'module' in the hybris world) which can be split across several extensions It is used for building unique names (e. prices/discounts/bonus buys) into hybris Commerce Suite.g. SAP Core Module The SAP Core Module provides the basis for developing and enhancing of SAP integration extensions.moduleId=<moduleId> Example: sapordermgmtbol. It offers core functionality which is needed to connect to an SAP system.moduleId=sapordermgmt There can be multiple extensions be assigned to the same module id.sap.properties file of the extension in the following format: <extensionName>.

carts and orders do not have a representation in the hybris persistence. SAP Synchronous Order Management Module The SAP Synchronous Order Management Module provides SAP ERP order management integrated into hybris Commerce Suite. with regard to data persistency and business processes. Orders are created and stored in hybris Commerce Suite before they are replicated to SAP ERP for order fulfillment. SAP Point-of-Sale Information Module When SAP Customer Activity Repository is part of your system landscape. hybris Commerce Suite stays completely independent of SAP ERP. the checkout.SAP Product Configuration Module The SAP Product Configuration module provides a comprehensive solution to manage personalized and customizable products in and with hybris Commerce Suite. POS transactions are purchases made in-store. or the order history are directly routed to SAP ERP. Customer interaction happens exclusively through and within hybris Commerce Suite. SAP Audience Discovery and Targeting Module The SAP Audience Discovery and Targeting (ADT) extension provides the capability to offer their customers personalized interactions / shopping in the hybris Commerce Platform by integrating and leveraging the results of the advanced segmentation capabilities of ADT. Calls to the cart. SAP Asynchronous Order Management Module In asynchronous order management. you can provide B2C customers with a more complete view of their purchase history by configuring the display of point-of-sale (POS) transactions in the online store. SAP Synchronous Pricing Module The SAP Synchronous Pricing Module enables you to read pricing information directly from SAP ERP. 23 .

24 .

25 .

26 .

27 .

28 .

 There is a dummy implementation of the SAPConfigurationService returning empty configuration data  Once the sapcoreconfiguration extension is active it replaces the dummy implementation with access to configuration data persisted via the hybris HMC UI 29 .

30 .

31 .

32 .

33 .

34 .