Skip to Content

SAP Hybris Commerce – Integration with SAP Solutions – A Compendium

This blog is discontinued since SAP Hybris Commerce 6.0, but can still serve you for general understanding about how to integrate SAP Hybris Commerce with SAP Solutions.

The most recent informatioin about the integration with SAP Solutions is available in the corresponding SAP Hybris Commerce docu parts (access only for registered Hybris Wiki users). Check each release seperately.


Dear community members,

This compendium gives an overview about the integration of the SAP Hybris Commerce Platform with SAP solutions, and provides helpful links and guides.

Please note:

Most of the hybris/SAP integration content described below is part of the hybris product portfolio. Therefore the online documentation, feature description, product details etc. are located in the Hybris WIKI (registration required, access might be restricted).

NEW However, as SAP customer you can download a comprehensive PDF presentation about the hybris/SAP integration from SAP Service Marketplace (as of Hybris Commerce 5.5).


    By release


The company hybris joined the SAP group in August 2013. In October 2013 SAP announced to discontinue its own SAP WebChannel Experience Management solution to solely focus on boosting hybris’ Commerce Suite. For hybris 5.1, just four months after the acquisition, SAP described the integration with SAP ERP in a RDS package documentation.

hybris 5.2

In July 2014, hybris 5.2 provided the integration with external procurement solutions.

The so-called hybris B2B PunchOut Service provides an easy configuration point for suppliers to integrate with third-party procurement systems and feed catalogs and product content to these systems on a request basis. This enables B2B buyers to access the full product catalog and shop within their preferred procurement system environment.

The hybris B2B PunchOut Accelerator offers a built-in access to the ARIBA network.

Check the hybris PunchOut Factsheet.

hybris 5.3

Back in Sept 2014, hybris 5.3 provided a deep integration between hybris Commerce Suite as a front end and SAP ERP as back end, introducing a new SAP extension. This integration makes it possible to reuse the master data available in SAP ERP, which are transferred as XML idocs via http using the hybris DataHub for the asynchronous transfer of master data, prices, stock information, as well as order documents and order status.

Here a list of standard idocs used (as of hybris Commerce 5.4)


hybris 5.3 contains a built-in Order Management integration with SAP ERP. Orders are either created in hybris (asynchronous and hybrid scenario), or directly in SAP ERP (synchronous scenario) using SAP’s Lean Order Management interface. Real-time connections to SAP ERP are performed synchronously via JCo-RFC connections calling SAP RFC Function Modules. The hybris Management Console (hMC) provides built-in settings to configure the preferred scenario, SAP ERP backend destination, RFC functional calls etc.


27-11-2015 13-39-42.png


Integrated in the hybris/ERP Order Management scenarios SAP Configure, Price, and Quote for Product Configuration provides a comprehensive solution to manage personalized and customizable products in and with hybris Commerce Suite. As a pillar of the SAP Configure, Price, and Quote (CPQ) solution, it allows you to expose capabilities of SAP ERP Variant and Product Configuration to your hybris online store customers. At the same time, it allows you to hide any complexity that is not relevant for the online store. Online store customers can configure these products interactively, and then order them.

No additional hardware is required in order to use SAP CPQ, as the configuration knowledge base with the configuration models is replicated from ERP database to the hybris database server as a second instance, which is independent from the hybris DB instance. So it sits there in parallel. The configuration engine is the “CPQ engine”, a JAVA based application that is installed on the hybris application server in parallel to the hybris application. hybris and CPQ engine communicate via JCO. During a product configuration by a user, the hybris application calls the CPQ engine via JCO, which provides the configuration options. The UI rendering however happens in hybris. So there is only one common UI for webshop and configuration part.

Please note that SAP CPQ requires an additional software license to make use of the product variant configuration, as well as an SAP ERP software solution package (SAP CPQ Product Config 2.x) which can be downloaded separately from the SAP Software Download Center.


20-11-2015 10-49-18.png


Important to all SAP customers to know, the hybris software shipment includes all SAP ERP integration capabilities, which is part of the hybris software. Unless you are not using SAP CPQ for product configuration, there is no additional package required in SAP ERP.

hybris 5.3 also provides an integration with SAP Customer Activity Repository (= CAR), a solution for SAP’s retail customers, where all customer activities are tracked. When SAP Customer Activity Repository (SAP CAR) is part of your system landscape, you can provide B2C customers with a more complete view of their purchase history. When customers access their order history in the online store, they can view not only orders made in the online store and other hybris channels, but also see their point-of-sale (POS) transactions.

When SAP hybris Marketing (formerly SAP Customer Engagement Intelligence) is part of your system landscape, you can offer your customers personalized shopping experiences by integrating and leveraging the results of the advanced customer segmentation capabilities with the hybris WCMS. The data needed in SAP hybris Marketing Segmentation comes from hybris Commerce Suite via SAP ERP, for customer-related and order-related information created in hybris, but optionally also from other sources like CAR (including POS data), Loyalty Management and CRM solution(s), Social Media platforms, geo-based data sources (e.g. Nielsen), … The extensive information of customer data, transactions and (social) interactions in the HANA based SAP hybris Marketing provides an ultimate 360 degrees view of the customer allowing best-in-class personalized marketing addressing.

This in total makes hybris 5.3 the first major release for SAP customers to go for.

SAP release requirements are found in the hybris WIKI.

hybris 5.4 (RTC on Dec 4, 2014, see product page in hybris WIKI).

Among generic hybris features, hybris 5.4 provides new SAP integration capabilities like the integration of the personalized product recommendations based on SAP hybris Marketing Recommendation (formerly known as Product Recommendation Intelligence), as well as important round offs of the extensive SAP integration content shipped in the former release.

For SAP customers hybris 5.4 supports

  • Integration with SAP hybris Marketing for personalized product recommendations
  • Watch the video on hybris 5.4 Product Information page
  • Handling of pre-configured product variants
  • Ordering of configurable products
  • Customer Self-Service and customer data change
  • Material classification data seamlessly integrated with hybris
  • Cart handling between sessions and planned backend down times (synchronous scenario)
  • Support of group conditions
  • Maintain and display commerce-specific information for configurable products

The comprehensive description of hybris 5.4 based SAP integration features is found in the hybris-SAP Knowledge part of the hybris WIKI.

hybris 5.5 (RTC on March 11 2015, see product page in hybris WIKI)

On March 11, 2015, hybris 5.5 was shipped. As in the former release, it contains both new capabilities as well as important round-off content.

hybris 5.5 provides important generic SAP integration features, like

  • Transfer of taxation information
  • Conversion of Base UoM
  • Definition of an SAP base store
  • Live ATP check via synchronous RFC call
  • Pricing scales via synchronous RFC call
  • Significant hybris DataHub performance increase

hybris 5.5.1 (RTC in April  2015, see product page in hybris WIKI)

This realease provided genuine hybris improvements, but from an SAP integration perpective the changes are only documentation:Instructions for extending SAP Data Hub extensions are now available, see Data Hub – Extensibility Guide.

However, hybris 5.5.1 is the first release supporting Java 8, Spring 4.1 and other latest technical framework releases. Please note that Java 7 is no longer supported with 5.5.1!

hybris 5.6 (RTC on August 4, 2015, see product page in hybris WIKI)

Asynchronous B2C and Synchronous B2B scenario can run in parallel on a single hybris instance. This capability was further extended in 5.7, see below.

SAP IS-Retail Integration Package

SAP Retail specific integration is provided by the SAP hybris Commerce, integration package for SAP for Retail

The package contains important enhancements to integrate SAP ERP Retail and SAP CAR with SAP hybris Commerce Suite by providing the following integration:

hybris 5.7 (RTC on Oct 8, 2015, see product page in hybris WIKI)

There is plenty of interesting functionality in 5.7.

From an SAP integration perspective, combined B2C and B2B scenarios can run in parallel on a single hybris instance. This is a huge step forward for all industries who sell to both B2B business partners as well as B2C consumers.

Here an extreme example of shop combinations possible with 5.7 in one hybris instance:

B2C with asynchronous order management (AOM)

  • B2B with asynchronous order management (AOM), prices and ATP are determined by hybris
  • B2B with asynchronous order management, but synchronous connection to ERP for e.g. pricing, ATP, credit limit, …
  • B2B with synchronous order management in ECC via SAP’s Lean Sales Order API (LO-API)

Please note that a hybris instance can only be connected with a single SAP ECC client, so all these scenarios have to run against the same ECC client.

Check the details in the hybris 5.7 SAP Integration docu.

A Rapid deployment Solution is available which provides a scenario and implementation guide to integrate Hybris Commerce 5.7 with ERP including special Retail Industry master data, see this blog: RDS – Hybris Commerce 5.7 integration with ERP incl. IS Retail and the corresponding RDS page.



Hybris Commerce 6.0 (RTC on April 13, 2016, see product page in Hybris WIKI)

Release Documentation

– massive enhancement on the Hybris Commerce platform, responsive UIs, Customer Experience, etc.

– SAP CRM Order Management Integration

– Integration of Hybris OMS with ERP logistics

Integration Technology and Architecture

There are different technologies used for the hybris Commerce/SAP Integration, see figure below:

20-11-2015 10-46-37.png

hybris Commerce/ERP integration methods

1) Asynchronous integration via Hybris Data Hub
used for the asynchronous transfer of master data and order documents between ECC and hybris Commerce Suite by using the hybris Data Hub. ERP data is replicated through SAP’s ALE layer as XML based IDocs (http transfer) to the hybris Data Hub, which identifies and converts the data packages into a hybris IMPEX format and forwards it to the hybris Commerce server.

In the same way hybris documents, e.g. orders, are sent from the hybris Commerce server to the hybris Data Hub, which converts the data into XML based idocs and forwards it to the ALE interface. This technology is applied for master data (materials, customers, price conditions, bonus buy conditions, stock inventory, order documents) and order documents. Standard iDoc types are used.

In B2C, usually you need no customer specific pricing, no true ATP check, no credit limit check (only a credit check for your payment card), … Therefore B2C is destined to run via AOM.


In B2B, you usually have customer specific prices, maybe even sales/volume contracts, credit limit, ATP check, customer/plant assignments, etc.

In B2B you have the option between

    • Asynchronous Order Management (AOM = order creation in hybris Commerce) with synchronous RFC calls into ERP for retrieving real-time information
    • Synchronous Order Management (SOM = order creation in ERP SD) via the Lean Order API (LORD, LO-API) for the (almost) complete SD Sales order context accessible from within hybris Commerce with a single RFC call. In case the ERP is not available a fail-safe mechanism is available to save the basket within hybris.

2015-08-18 hybris-SAP Integration in Detail_CUSTOMER.png

2a) Synchronous integration via JCo-RFC connection
The synchronous access from hybris Commerce Suite to an ECC is used to retrieve information at runtime, e.g. customer specific prices, ATP check, credit limit check, or when called the Lean Sales Order API to directly create standard SD orders from hybris Commerce Suite.

In B2B, you usually have customer specific prices, maybe even sales/volume contracts, credit limit, ATP check, customer/plant assignments, etc. Here a synchronous order creation in ERP is useful, with access via the Lean Order API (LORD, LO-API) for the true ERP Sales Order specifics.


2015-08-18 hybris-SAP Integration in Detail_CUSTOMER.png

2b) Synchronous integration via OData Web Services Odata

web services are used to synchronously integrate

    • SAP Customer Activity repository (from hybris Commerce 5.4)
    • SAP hybris Marketing (Recommendation, Segmentation) from 5.4

Master Data

(all transferred asynchronously via hybris Data Hub)

  • Transfer of standard materials and IS-Retail single articles to hybris (hybris 5.3)
  • Transfer of variants of IS-Retail generic articles (w/o header) from ERP to hybris (hybris 5.4)
  • NEW Transfer of IS Retail Generic articles, merch hierarchy to hybris (hybris 5.6 with SAP Retail Industry Addon 1.0 for hybris Commerce 5.6)
  • Transfer of plant ID from ERP to hybris (hybris 5.5)
  • Transfer of hybris customer records to ERP (5.3) to become ERP debitor master
    • including customer data changes (5.4)

Prices / Discounts / Bonus Buy:

(all transferred asynchronously via hybris Data Hub)

  • Transfer of Prices, discounts from standard ERP to hybris (hybris 5.3)
  • Transfer of IS-Retail Bonus Buy conditions to hybris (hybris 5.4)
  • Transfer of Tax indicator to hybris (hybris 5.5)

Order Management:

  • Asynchronous Order Management (order creation in hybris Commerce Suite)
    • Asynchronous transfer of hybris orders to ERP via iDoc (hybris 5.3)
    • Transfer of SD order status from ERP to hybris via iDoc (hybris 5.3)
    • Change header, delete complete orders in hybris or ERP (hybris 5.4)
  • Hybrid/Mixed/Pick&Choose Scenario = Asynchronous scenario with synchronous JCo-RFC calls from hybris to ERP, e.g. to retrieve
  • Synchronous ERP order integration via LORD API (order creation directly in SAP ERP as standard SD Order via LORD API)
    • focus on B2B scenarios
    • Direct (synchronous) creation of an ERP SD order while bypassing the hybris order management capabilities.
    • LORD order creation limitations (compared to ERP Sales Order in va01) apply.

Integration with EWM and TM?

In the asynchromous scenario, Hybris Commerce creates the order, and sends it to ERP. From there it is fulfilled in whatever fulfillment system, SD, EWM, TM, …
In case the fulfillment happens outside ERP, the SD order management is to be informed about the order fulfillment status, to posts the order status via idoc to Hybris Commerce. 
So there is no direct integration between hybris Commerce and EWM, TM etc. required (nor available).

hybris Commerce Integraton with SAP Cloud for Customer (C4C) – outdated chapter

The C4C integration provided by SAP (for service ticket and customer master replication) relies on the hybris Data Hub.

In contrast to the ERP integration, the C4C integration uses SOAP service calls (C4C communication arrangements) instead of IDocs. For the quick access to the hybris Assisted Service Module from within C4C, a URL mashup is used. Again, have a look at the corresponding section in the hybris wiki for more information. To my knowledge, there are no standard iFlows (HCI or PI content) available that would realise integrations between C4C and hybris Commerce.

Authentification and Identy Management

For general authentification, please refer to (OAuth 2.0).

A few use case for our integration with C4C use SAP Cloud Identity Service. Please refer to for details.


hybris Commerce – Product Information and Support

Training and Learning

  • hybris-SAP Learning Map for technical and application consultants for Customers and Partners
    • hybris-SAP Integration 3-day Classroom Training (HY600) (public)
      >> training is outdated and is to be revised
    • hybris Essentials Online Training for Customer and Partners
    • Learning Room for hybris-SAP Integration (customer/partner)
      • Starting mid of April 2015, the Learning Room is offered with the option to subscribe to new on-demand access to SAP training systems, preconfigured with the data you’ll need to carry out the exercises, plus additional live info sessions.Please note that access to this content in SAP Learning Hub requires a commercial subscription to SAP Learning Hub. Find more information here:
        • Log on to SAP Learning Hub
        • To search for the Learning Room, from the Main Navigation Node (in upper left corner, next to SAP Learning Hub), select Learning Content.
        • In the Find Courses screen area, enter the Learning Room title hybris-SAP Solution Integration Learning Room (EKT), and click Go to receive the link to your learning room.
        • To narrow your search results, select Learning Room in the Delivery Method screen area. Choose the link to your Learning Room to open it.


Most content of this blog is from early 2016 and has not been updated since. But I hope you find it stilluseful, as the general integration is still working as described.




Dr. Ingo Woesner

Global Director, Product Management Retail Omnichannel



Follow me on SAP Community Network and LinkedIn

You must be Logged on to comment or reply to a post.
  • Thanks a lot for sharing overview Ingo. Good to hear that we can make a synchronous communication with SAP ECC and make use of LORD api.  ISA also has similar API and I hope Hybris is incorporated with the Backend layer which is used in ISA. In that case, its a good thing for the ISA developers for an easy migration to Hybris. 


    Kiran Kumar Vemula.

  • Hello Ingo,

    You indicate for Hybris 5.7 - Synchronous ERP order integration (SOM) that the focus is on B2B scenarios. 

    However on the Hybris Wiki I also read that from 5.7 we can also have the "Full" integration scenario:

    • Full: AOM and SOM for B2C and B2B

    Could you share some more details on SOM  in combination with B2C scenarios? (new possibilities / limitations of previous versions no longer valid?)

    Thanks in advance and regards,

    Wouter Dingjan

    • Hello Wouter,

      this means you can run a AOM+SOM combined on the very same hybris instance.

      Technically it doesn't matter which one you use for B2B and B2C, or both for B2B or both B2C (regardsless of whether this makes sense from a business perspective or not).

      Typically a B2C scenario is realized via AOM, to keep the high-volume B2C requests away from the ERP backend. In B2C, usually you need no customer specific pricing, no true ATP check, no credit limit check (only a credit check for your payment card), ... Therefore B2C is destined to run via AOM.

      In B2B, you usually have customer specific prices, maybe even sales/volume contracts, credit limit, ATP check, customer/plant assignments, etc. Here a synchronous order creation in ERP is useful, with access via the Lean Order API (LORD, LO-API) for the true ERP Sales Order specifics.

      Best regards,


      • Hello Ingo,

        Thanks for your reply.

        So can I conclude the following?

        • In 5.6 It was made posible to Run AOM+SOM on the same Hybris instance. Where AOM can be used for both B2B and B2C and SOM only for B2B.
        • In 5.7 same as above for 5.6 but additionally SOM can be used for B2C as well. However in reality the combination SOM / B2C is still unlikely due to load on ERP back end and no need for customer specific pricing / true atp / credit check / etc..

        Thx and regards,

        Wouter Dingjan

        • Hi Wouter,

          my understanding ist that in 5.6 basic capabilities were introduced to run two separate scenarios on one hybris instance.

          Now in 5.7 a COMBINED B2B/B2C scenario is possible. They can be AOM/AOM, AOM/SOM, OR SOM/SOM.

          B2C as SOM is certainly the exception. B2C typically runs as AOM, while in B2B you need real-time information hybris Commerce has to retrieve at runtime, e.g. customer specific prices, ATP, credit limit, etc.

          Best regards,


  • Hello Ingo,

    In 5.7, I would like to use AOM for my B2B store along with synchronous pricing.

    1) When I checkout, what price components can be retrieved from ERP? Each product price, shipping charges, taxes, discounts?

    2) Is the final cart price (after considering all pricing components) also retrieved from ERP, or does it have to be calculated in hybris?

    3) Can I use hybris Vouchers and Promotions in this scenario? Will it lead to discrepancies in the Sync pricing?

    Thanks in advance


    • Hi Sudhanshu,

      AOM with synchronous parts is a typical scenario for B2B businesses, where orders should be created in hybris Commerce to avoid unpredictable load and dependency from ERP (as in the synchronous order management SOM).

      Therefore a new SD Price Inquiry RFC function module in ERP EhP7 SP3/4 and higher was introducted to provide the customer specific prices and scales ON ITEM LEVEL and without an order context.   It is optimized for the price calculation for multiple items (material numbers) at once. You can download a detailed documentation here from SAP Service Marketplace

      However, as it has no order context, it cannot calculate the header conditions incl shipping/freigth costs.

      Here I see  3 options:

      1. add header conditions in the hybris pricing engine, maybe transferred as conditions from ERP. I am no expert here, but you have to enable the hybris pricing engine somehow to calculate the header conditions and shipping based on the customer specific prices the SD Pricing RFC has provided..
      2. "Simulate an ERP order" by calling the ERP LORD API during the checkout, and transfer the provided prices into the hybris order creation process. But this procedure would raise the question why you wouldn't create the order directly in ERP when you have the order already there and just need to commit and save...
      3. Switch to SOM. Then you have almost the full SD order context at hand with just one RFC call. No need to worry if ERP is down. There is a fallback mechanism available since 5.4 to save the basket content for later.

      Bst regards,


      • Thanks Ingo.

        We are looking at AOM with sync pricing for both B2B and B2C. SOM is not an option due to some other business/technical considerations, so #3 is ruled out.

        #2, as you rightly said, why not just create the order itself.

        Which leaves us with #1 as the only feasible option.

        I went through some documentation on the hybris wiki around sync pricing which seemed to suggest that you do get shipping and transaction costs from SAP ERP. I quote "After customers apply their shipping and payment selections to orders, the system displays shipping and transaction costs from SAP ERP". That made me thinking if you could actually get those costs without having created an order in SAP. And if you could, maybe SAP could give you the total order price as well !

        So we clearly need some bit of customization to achieve this.

        Thanks again!


  • Hi Ingo

    Wonderful compilation and historical overview.

    I've got a question regarding SOM with ERP. Since it is based on JCo and RFC calls (similar to the way ISA and WCEM connected with their backend systems), can this scenario actually be supported in a landscape where hybris is hosted in the cloud/external data centre, while the ERP backend runs as an on-premise installation?

    For SAP's SAAS solutions such as Cloud for Customer, the HCI or PI iFlows-based integration works because all communication is via HTTP (web services, XML IDocs), so the cloud solution can be integrated via the web and a reverse proxy (e..g, SAP Web Dispatcher) sitting in a DMZ on the outside of the internal network. However, there is no standard iFlow integration for hybris (which makes sense as it's not really part of SAP's SAAS portfolio).

    For custom developments on the HANA Cloud Platform, the HANA Cloud Connector allows the use of JCo calls from a Java app running in the cloud to the SAP backend. However, to my knowledge, there is no standard support for running hybris on a customer's HCP instance, so the cloud connector wouldn't be available.

    Any thoughts on this would be greatly appreciated.

    Thanks and best regards


    • Hi Matt,

      I am tempted to say yes, as I know at least one customer with a hosted hybris Commerce (hosted via hybris Managed Services) and an on premise ERP, hosted somewhere else.

      This project was recently presented by the customer on the DSAG (German SAP user group) meeting where I presented the SAP Retail Omni-Channel Commerce reference architecture

      Let me reach out to some infratructure colleagues, to compile you a more comprehensive answer.

      Best regards,


      • HI Ingo

        Thanks for the reply and internal follow-up. Much appreciated.

        I think for a B2C scenario with AOM via the hybris DataHub, this should definitely work. Since all communication with the ECC backend happens via HTTP and XML IDocs, a reverse proxy or application-level load balancer as well as a suitable network architecture would control the transfer of data from the internet/cloud to the customer internal network with the business systems. This is basically the same as for SAP's other SAAS applications like Cloud for Customer and integration via PI/HCI. I'm still wondering how to achieve this for synchronous communication via JCo, though.

        Thanks again and best regards


        • Hi Matt,

          I got the reply from the infrastructure colleagues.

          You can runa hybris Commerce in a managed cloud / hosted envoronment, separated from the ERP, and have the RFC communication via VPN tunneled RFC requests.

          There is no difference between a VPN type of synchromous integration, and the "normal" one. Datahub would run close to the hybris instance in the hosted environment as well.

          We have a few customers who already realized such a set up.

          Best regards,


          • Hi Ingo,

            SAP provides pre-packaged content for integration with SAP's SaaS offerings (C4C, Success factors etc) that can be deployed in PI / HCI? YaaS being SaaS offering, are there plans to provide PI/HCI content?

            What is SAP's strategic direction on use of Datahub or PI/HCI for SAP ERP - Hybris integration?

            Having Datahub would have yet another integration tool in the IT estate. Can the integration be met using just SAP PI, if both ERP and Hybris are hosted systems, without use of Datahub?



          • Hello Harpreet,

            standard-wise, HCI/PI is NOT used for the integration of SAP solutions with hybris Commerce. Instead, the hybris datahub is used for the asynchronous integration between ERP and hybris Commerce, see my SCN blog "hybris/SAP Integration - A Compendium.

            However, there are customers integrating ERP with hybris Commerce via PI, on project basis of course. Typically these are customers who already had a PI in their SAP landscape, and wouldn't want to implement/monitor a second integration tool.

            SAP has chosen the hybris Datahub over the SAP PI, to not force SAP customers to implement a PI just for a webshop integration, as the PI requires an additional license and additional integration effort. The Datahub is a generic tool for ASYNCHRONOUSLY integrating any backend solution with hybris, not only SAP solutions.

            But in case a PI is already in place, customers always ask the question you are asking. From what I was told the asynchronous integration via PI is not overly difficult. Just converting idocs into an XML-like hybris "impex" format and vice versa.

            C4C is integrated asynchronously via the datahub as well (from hybris 5.7), plus access to hybris Commerce via UI mash up.

            As for YaaS I am not informed how the integration works here. I will ask a colleague to reply.

            Hope this helps.

            Best regards,


          • Thanks Ingo for the information. This helps.

            Did you get a response / more info on YaaS integration?

            Couple of more questions:

            1. IS-Retail Integration package - This package needs to be deployed on IS-Retail. What gets deployed on Datahub? Does this work out of the box with some config or development effort is required?

            2. SAP provides integration content (deployable on HCI or PI) for C4C-ERP integration. To integrate Hybris with C4C, is Datahub recommended or HCI (PI) is the recommended technology?



          • Hello Harpreet

            I'm answering to your earlier question to avoid getting too much indent in this conversation stack.

            YaaS Integration

            This question cannot be directly answered because YaaS is not so much an individual product but a set of microservices built according to a defined architecture, common design principles, and development guidelines. The default storefront template "integrates" with YaaS via simple REST web service calls. For a greenfield commerce-as-a-service project, you wouldn't really need an integration with hybris on Premise because YaaS already provides the relevant services.

            However, the set of YaaS services is constantly expanding and some will indeed integrate with SAP's other CEC solutions. A good example is hybris Loyalty, which has just become GA in the US. This solution can optionally be integrated with hybris on Premise and this happens again via the hybris Data Hub. More information can be found in the corresponding section of the hybris wiki.

            C4C Integration

            As Ingo pointed out, the C4C integration provided by SAP (for service ticket and customer master replication) relies on the hybris Data Hub. In contrast to the ERP integration, the C4C integration uses SOAP service calls (C4C communication arrangements) instead of IDocs. For the quick access to the hybris Assisted Service Module from within C4C, a URL mashup is used. Again, have a look at the corresponding section in the hybris wiki for more information. To my knowledge, there are no standard iFlows (HCI or PI content) available that would realise integrations between C4C and hybris Commerce.

            Best regards

  • Hello again Ingo,

    In the beginning of your post you make the statement:

    Hybris 6.0 - SAP CRM order management integration; multiple SAP backends, further C4C integration - stay tuned

    So for the "multiple SAP backends' part that means the following:

    In the  AOM scenario you can have Hybrs sales orders for one store replicated to SAP ECC system A and sales orders for another store replicated to SAP ECC system B.

    Is this statement correct?

    If yes how to configure that on the Hybris side.

    In the backoffice under SAP integration you can set an HTTP destination. Here you would define the SAP ECC system to which the sales order messages should be sent. But how to link different HTTP destinations to different (SAP) Base stores?

    Thanks in advance and regards,

    Wouter Dingjan

    • Hello again, Wouter!

      I am no longer involved in the most recent (industry generic) Hybris Commerce-SAP integration.

      Myself I concentrate on SAP Retail Omnichannel Commerce now, where I of course cover the very interesting integration with Hybris Commerce and SAP Retail solutions like the SAP Customer Activity Repository (CAR), see my SAP Retail Omnichannel Customer WIKI here in SCN.

      However, I still own this blog, so I try to help you as always 🙂 I have asked a colleague to answer your question about multi backend support and hope he replies soon.

      In the meantime I would like to refer you to the application help section of Hybris Commerce 6.0, which should be accessible for parties who register to the platform.

      Best wishes,


      • Thanks Ingo,

        Could not find the answer to my specific question on the wiki. So looking forward to the answer by your colleague.

        Kind regards,


  • Hello Ingo,

    When the synchronous scenario (with SD LORD functinality) is used, the connection between Hybris and ERP is kept stateful, right? I mean that stanrting with the first RFC call, the connection, SAP session and a user context are kept in the memory on the ERP side, until it's explicitely or implicitely closed by RFC_CONNECTION_CLOSE. Am i right?

    Is it possible to use standard synchronous scenarion (with LORD) via SAP PO 7.5 ? Both should be having JCo, but are they compartible ?

    Thanks, Dima


  • Hi Ingo,


    Thanks for the post which gives a good overview. You mentioned about integrate multiple SAP backend with SAP hybris commerce. Can one SAP Hybris instance (containing multiple b2b storefront) integrate with multiple SAP PI/PO for synchronous data transfer? Since there will be no datahub, will the integration be entirely be customized on the SAP Hybris side? Or hybris offers another solution? Any recommendation or best practice for such a scenario?




  • Hi Andrea,

    For a few years now I am no longer involved in the topic.

    Please check the Hybris help docu to check what's possible here.


    Sorry and best regards,