The document discusses the integration of SAP Hybris architecture with various SAP solutions, outlining the reference architecture model and its application in business processes. It emphasizes the need for architecture to cater to specific business requirements and the importance of making informed architecture decisions for project success. Additionally, it presents real-world examples of integration challenges and solutions between SAP Hybris commerce, marketing, and ERP systems.

1. PUBLIC
Brendan Dobbs,Head of Architecture Practice
SAP Hybris Center of Expert Practice
Integrating with the SAP Hybris
Architecture:
From Reference to Real World

2. 2PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
What is a reference
architecture model?
A baseline/
template
Architecture
recommended
practices
Supports end-to-end
business processes for a
given industry, domain,
scenario
Does not account for
all customer
requirements Does not always
need to be adopted

3. 3PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Reference SAP Hybris solution architecture
SAP S/4HANA Enterprise Management*
SAP Hybris Marketing Cloud
Recommendation
model
Know your
customers
Customer profile and interactions
Target groups and campaigns
Offer
model
Segment
model
Products
Customer
Consumer
Product
catalog
Prices
Business
partner
Product,
prices
SAP Hybris Sales Cloud /
SAP Hybris ServiceCloud
Customer
Oppor-
tunity
Ticket Product
Quote /
order
System of
engagement
Personalized
recommendation
Personalized
offers
Personalized
storefront
“Click-
stream”
Cart /
quote
SAP
CRM
(if existing)
SAP Hybris Commerce
Personalized shopping experience
Business
partner
Product
ASM module
Core enterprise platform Order
Lead
Activity

4. 4PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Integration solutions from SAP
PI/PO = SAP Process Integration / SAP Process Orchestration
CPI = SAP Cloud Platform Integration
SAP Hybris Data Hub CPI PI/PO
Deployment options On Premise Cloud On Premise
Data replication (batch) Yes Yes Yes
Synchronous business
processes
No Yes Yes
Content for SAP Hybris
solutions
Yes, but only used for SAP
Hybris Commerce integration
Yes, SAP Hybris
Cloud for Customer,
SAP Hybris Marketing
and others. Not SAP
Hybris Commerce yet.
No
Recommended usage SAP Hybris Commerce to any
other SAP solution (where
content exists)
Cloud to Cloud
Cloud to On
Premise
On Premise to On Premise

5. 5PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Hybris Commerce <—> SAP Hybris Marketing
SAP Hybris
Commerce
SAP Hybris
Marketing
Data hub
Customers
Orders
Saved carts
Reviews
Abandoned carts
Products
REST (CSV) REST (OData)
Interactions
Product
recommendations
Segments
Offers
REST (OData)
REST (OData)Clickstream
interactions
Asynchronous/batch
Synchronous

6. 6PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Hybris Commerce <—> SAP Hybris Cloud for Customer
SAP Hybris
Commerce
SAP Hybris Cloud
for Customer
Data hub
Customers
REST (CSV) SOAP
Individual customers
ASM HTTP redirect
Tickets REST (OData)
Asynchronous/batch
Synchronous

7. 7PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Hybris Marketing <—> SAP Hybris Cloud for Customer
SAP Hybris Cloud
for Customer
SAP Hybris
Marketing
SAP Cloud Platform
Integration
SOAP
Leads
Appointments
Phone calls
Tasks
Campaigns
SOAP
REST (OData) Campaign interactions
REST (OData) SOAP
Customers
Contacts
Consumers
Leads and
opportunities
Appointments,
visits, and phone
calls

8. 8PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
SAP Hybris Commerce <—> ERP
REST (CSV) HTTP (IDoc)
Order
Customer
Sales Order
Consumer
DataHub
HTTP (IDoc)
Material
Classification
Condition
Inventory
Products
Classification
PriceRow
Stock
HTTP (ImpEx)
HTTP (IDoc)
Returns/refunds
Shipping conf
Invoice
HTTP (ImpEx)
Returns/refunds
Consignment
SapB2BDocument
RFC (JCo)Price
Credit check
ATP
Cart
Order
SAP Hybris
Commerce
ERP
(SAP S/4HANA,
SAP ERP)

9. Real-world examples

10. 10PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
§ Real-time pricing from the ERP can introduce latency
§ Fast, responsive performance was a key concern for the business
§ NoSQL storage offers fast storage and retrieval that SAP Hybris Commerce can’t support
§ Large number or complex rules/conditions could be problematic with this approach
Alternative example 1: Near real-time pricing for SAP Hybris Commerce
Price publication (NRT)
PriceRow
SAP Hybris
Commerce
ERP
(SAP S/4HANA /
SAP ERP)
NoSQL
Native driver
Native
import/CSV

11. 11PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
§ SAP Process Integration and SAP Process Orchestration comprise the business’s strategic middleware
solution, in which it has already invested heavily
§ Business did not want to introduce another middleware solution (cost of maintenance/operation)
§ High up-front effort required to create transformation and transportation logic is acceptable
Alternative example 2: SAP Process Integration / SAP Process Orchestration
integration with SAP Hybris Commerce
ERP
(SAP S/4HANA /
SAP ERP)
RFC (IDoc)
PI/PO
REST (JSON)
REST (JSON)
RFC (IDoc)
SAP Hybris
Commerce

12. 12PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
§ Business did not like the complexity of the out-of-the-box solution (Apache ActiveMQ, and event stream
processor
§ SAP Hybris Commerce sends interactions directly to SAP Hybris Marketing but in a batch (performance) and
using background processes
§ Similar solution is now in the product
Alternative example 3: SAP Hybris Commerce → SAP Hybris Marketing
clickstream
ActiveMQ
SAP Hybris
Marketing
BusinessEvent
Native driver
BusinessEvent
Native driver
REST (OData) Interaction (batch)
SAP Hybris
Commerce

13. 13PUBLIC© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Takeaways…..
Architecture needs
to support the
specific requirements
Architecture needs
to fit into the
business’ policies
and strategy
Reference
architecture is at
least an excellent
starting point to build
on
1. 2. 3. 4.
Making sound
architecture
decisions gives the
project the best
chance of success

14. Thank you.