SAP Hybris - HY600 - Col03 Latest

HY600 Collection: 03 M aterial N um ber: 50130044

Learning Objective

After completing this lesson, you will I i able to: Describethe various integration scenarios Explain the architecture of the SAP hybris integration List SAP Modules and important extensions Explain used technologies Explain how to activate SAP hybris integration List necessary configurations to be made in hybris management console

Agenda

1) Business considerations 2)

Overview

3} Architecture

- Asynchronous Integration Architecture - Synchronous Integration Architecture - Modules and Extensions C o n fig u ra tio n

A Client who already owns SAP products wants to implement an enterprise software solution for e-commerce based on the newly acquired hybris product and SAP Business Suite Products Client Requirements: Create a rich user-experience for the online e-commerce Application that has all the features offered by the hybris Commerce Suite platform (e-commerce, multi-channel commerce, master data management and order management, extendability, etc). Customers (users) must only interact with the hybris based ecommerce Application Still use the existing SAP Products (both Data and Functionality)

hybris-SAP Solution Integration

Refers to how hybris and the SAP Products need to be configured to work together based on various scenarios Components: e-commerce A pplication (existing or to-be created) based on hybris platform v5.3 or higher (latest recommended) SAP Products (including Master Data)

B e n e f it s

user experience when using hybris inform ation available fo r performing the integration (as Rapid Deployment Solution, planned fo r early 2015) configuration set-ups based on various SAP integrated business scenarios time to market by using out of the box ecommerce functionality from hybris SAP Master Data (Products, Customer, Prices, Stock level, etc) |

reduces

front-end com plexity by using hybris as entry-point for placing an order

A genda

B u s in e s s c o n s id e r a t i o n s

2)

O v e r v ie w

3)

A r c h it e c t u r e -

Asynchronous Integration Architecture

-

Synchronous Integration Architecture

-

M od ules and Extensions

C o n fig u r a tio n

Overview: Integration Scenarios

S y s t e m s O v e r v ie w : h y b r is in a n S A P la n d s c a p e

•optional In all scenarios, master data are transferred asynchronously through the hybris Data Hub. HTTP is used as general communication protocol. Messages transferred between the SAP backend and the Data Hub are of content type xmlIDoc. Messages transferred between the Data Hub and hybris are of content type ImpEx. In the synchronous and "hybrid” scenarios, also - RFC calls are used for communication with the SAP ERP back-end. - ODATA WebService calls are used with SAP CAR and SAP hybris Marketing.

A synchronous Order Management • Customer interaction through and within hybris. • Order capturing process runs completely in hybris Commerce Suite, including price calculation and order persistance. • hybris stays independent from SAP back-end • Transfer of master data for products, prices, inventory, customer (optional) and order status from SAP ERP to hybris via the hybris Data Hub. • When an order is created in hybris, it is replicated asynchronously through the hybris Data Hub to the SAP ERP back end; subsequently, order fulfillment is carried out in SAP ERP. • Integration through asynchronous communication (iDocs) using the hybris Data Hub. ° Integration method often preferred in B2C and simple B2B scenarios using price lists. This makes asynchronous order management a good choice for many B2C scenarios and lean B2B scenarios. • Orders can be canceled either from hybris Customer Service Cockpit or from SAP ERP, and the cancelations are replicated to the other system. The B2C scenario is supported through the B2C Accelerator. • The B2B scenario is supported through the B2B Accelerator.

Target custom ers: The ones who already have invested in SAP back-end infrastructure, but are working on old version of the product (mainly B2C customers, or the ones who have simple B2B scenarios, without complex price calculation)

Hybrid Scenario (Asynchronous O rder Management w ith synchronous parts) • In addition to the asynchronous scenario, there is the option to add synchronous calls into backend(s), e.g. • to determine customer specific B2B prices und discounts (from hybris 5.3 with EhP7) • ATP check (from hybris 5.5) • Credit Limit Check (from hybris 5.5) scale price determination (from hybris 5.5). • Calls on project basis, e.g. retrieve store inventory from CAR ...

• Customer interaction through and within hybris. • Order capturing process runs completely in hybris Commerce Suite, including price calculation and order persistance. • hybris stays independent from SAP back-end • Transfer of master data for products, prices, inventory, customer (optional) and order status from SAP ERP to hybris via the hybris Data Hub. • When an order is created in hybris, it is replicated asynchronously through the hybris Data Hub to the SAP ERP back end; subsequently, order fulfillment is carried out in SAP ERP.

Integration through asynchronous communication (iDocs) using the hybris Data Hub. Integration method often preferred in B2C and simple B2B scenarios using price lists. This makes asynchronous order management a good choice for many B2C scenarios and lean B2B scenarios. Orders can be canceled either from hybris Customer Service Cockpit or from SAP ERP, and the cancelations are replicated to the other system. The B2C scenario is supported through the B2C Accelerator. The B2B scenario is supported through the B2B Accelerator.

Target customers: The ones who already have invested in SAP back-end infrastructure, but are working on old version of the product (mainly B2C customers, or the ones who have simple B2B scenarios, without complex price calculation)

S ynchronous Order Management • For complex B2B scenarios as well as with customers who heavily invested in SAP back-ends (e.g. customer speicific pricing, ATP check, sourcing, credit limit check, ...) • Transfer of master data for products, prices, inventory and customer asynchronously from SAP ERP to hybris using the hybris Data Hub. • Orders and shopping baskets are directly created in ERP, bypassing the hybris order management. ° Order Management Integration through synchronous communication via JCo/RFC. ° Customer interaction in hybris (catalog, search, navigation, ...). Order creation dirtectly in SAP ERP backend . The order processes and data reside in the SAP ERP back end. ■ This option is designed for use in B2B scenarios, safeguarding heavy investments made for an SAP ERP back end, such as implementation of complex pricing, availability information, and credit limit checks that are not meant to be replicated to hybris Commerce Suite. The B2B accelerator is extended by the synchronous order management scenario. Products, as well as customers and contacts, must be replicated asynchronously from the SAP ERP back end to hybris Commerce Suite.

• Target customers: 1) The ones who already have invested in SAP back-end infrastructure, but are working on old version of the product (mainly B2C customers, or the ones who have simple B2B scenarios, without complex price calculation) 2) The ones who are looking for the holistic solution to cover all aspects of their business activities.

S A P In t e g r a t i o n w it h i n h y b r is C o m m e r c e S u it e

SAP Back-end integration is part of the hybris commerce suite Fully comply w ith hybris architecture •

Integration is done by using extensions

• Configuration within hmc •

Uses S P RING a s program m ing model

• hybris Data Hub for asynchronous scenarios Different scenarios are activated by installing extensions and configuration in hmc

Required Applications and Releases hybris Commerce Suite hybris Commerce Suite 5.3 or higher (latest recommended), including the hybris Data Hub SAP ERP Asynchronous or synchronous order management and product configuration SAP ERP 6.0 EHP5 SP09 or a higher SP SAP ERP 6.0 EHP6 SP05 or a higher SP Any higher EHP Synchronous pricing using the SD Price Inquiry API SAP ERP 6.0 EHP7 SP04 or a higher SP SAP CPQ C onfiguration Runtime (SSC) - optional SAP Solution Sales Configuration 1.5 Plug-In for hybris SAP hybris Marketing applications: Segmentation (ex ADT) and Recommendation (ex PRI) - optional Segmentation: SAP CE11.1 SP04+, hybris 5.3 or higher (latest recommended) Recommendation: SAP CE11.1 SP05+, hybris 5.4 or higher (latest recommended) SAP CAR - optional SAP CAR 1.0 SP1 or higher, hybris 5.3 or higher (latest recommended)

Procedure: To Perform hybris-SAP Solution Integration Install hybris Commerce Suite platform

hybris platform Installed

Install and Configure hybris Data Hub

hybris Data Hub Installed

Set up System Connections for hybris-SAP Solution Integration

System Connections configured

Configure Basic Settings on SAP ERP for Asynchronous Data Replication to Data Hub

Basic Settings on SAP for Asynchr. Order Mgmt. configured

Synchronize Common Data between SAP ERP and

Common Data synchronized between SAP and hybris

Configure Common Settings in hybris Management Console

Common Settings configured in

Procedure: To Perform hybris-SAP Solution Integration

J

l Replicate Customer Master Data from SAP to hybris

4

r t ------------------------—

( [

V ,_,

Customer Master Data is available in hybris

-----------------------------------

Replicate Product Master Data & Stock Level from SAP to hybris

Product Master Data & Stock Level are available in hybris

Replicate Prices and Discounts Data Exchange

Prices and Discount Data is available in hybris

Perform an Asynchronous Order in hybris

Order is done in hybris and sent asynchronously to SAP

A genda

B u s in e s s c o n s id e r a t i o n s

2)

O v e r v ie w

3)

A r c h it e c t u r e -

Asynchronous Integration Architecture

-

Synchronous Integration Architecture

-

Modules and Extensions

C o n fig u r a tio n

Data Hub Overview

The hybris Data Hub enables end users to easily feed data from external systems into any hybris system. The complexity of the hybris data structure is hidden from the users that are designing the integration. The Data Hub also acts as a staging area where external data can be analyzed for errors and corrected before being fed into hybris

SAP ERP

A s y n c h r o n o u s A r c h it e c t u r e Outbound: hybris -> SAP ERP Process engine is used for decoupling Data Hub adapter transfers data to Data Hub Data Hub extensions define the raw data formats, the transformation to canonical data format and the target system format • SAP IDOC outbound adapter reads target system definition, creates IDOCs and sends via SpringIntegration to SAP ERP

Inbound: SAP ERP -> hybris • IDOCs are received by SAP IDOC inbound adapter, which creates Spring-Integration messages Messages are routed to mapping services provided by the SAP extensions Mapping services are creating raw data fragments and route them to Data Hub raw inbound Data Hub transforms raw items to canonical items and then to target items, which are published to hybris - During impex data processing, hybris services, interceptors, translators and events are used

Asynchronous Architecture Spring-Integration Inbound

REST web service idocInboundService receives IDocs from ERP, creates a message and sends it to the idocXmllnboundChannel A router routes the messages according the IDOCTVPE to specific channels, e.g. ORDERS05, MATMAS The specific channels are read by service activators. The service activators are calling mapping services, provided by the different hybris Data Hub extensions for SAP ERP, e.g. saporder, sapcustomer, sapproduct, sappricing The mapping services are returning messages in the Data Hub raw fragment format, which are routed to the Data Hub rawFragmentDatalnputChannel

Asynchronous Architecture Spring-Integration O utbound

SAP IDOC outbound adapter creates a message with Java object for IDoc and sends it to the sapIDocOutboundChannel A Marshaller transforms the Java object to a xml object and puts it into the sapXmlOutboundChannel A further transformer creates a String message out of it and puts the message to the sapHttpOutboundChannel The sapHttpOutboundAdapter finally sends it as IDOC/xml via http to the ERP system. This adapter also handles the security and authorization requirements

Data Hub