How SAP HANA Cloud is transforming Business Application Development at Danone

Transcription

1 How SAP HANA Cloud is transforming Business Application Development at Danone

2 Presentation agenda The story of SAP HANA Danone Application development with HANA Cloud Portal Future directions Page 2

3 The story of SAP HANA Danone Context HANA Cloud Portal Saas HANA Cloud PaaS SAP On-premise Portal ABAP Webdynpro Page 3

4 Security The story of SAP HANA Danone Latest software No upgrades Reliability EVOLUTION OPEX vs CAPEX Flexibility SLA Easy site creation CONTEXT: how Danone evolved from ABAP/ECC6 => Great SAP HANA UX CLOUD (monolitic apps)=> SAP HANA Widgets Cloud Portal (wigitized app) Low TCO Evolution of skill set Scalability Evolution of development way of working Business Continuity Lower initial cost Page 4

5 The story of SAP HANA Danone REACH PRODUCTIVITY RAPID EVOLUTION Page 5

6 The story of SAP HANA Danone Reach Potential SAP business application users B2C Enterprise B2E B2E Traditional SAP Users B2B ECC6 ERP SAPGUI Page 6

7 The story of SAP HANA Danone Reach Potential SAP business application users B2C HCP Enterprise Traditional SAP Users B2E HCP B2E B2B HCP ECC6 ERP SAPGUI Page 7

8 Why SAP HANA Cloud Portal? Productivity VA01 HCP CRM Complex, Static, single function screen Simple, yet Dynamic, multifunction screen Page 8

9 The story of SAP HANA Danone Evolution RFC Webshop RFC CRM RFC Product catalogue Stable Rapid Evolution Page 9

10 Application Development with HANA Cloud Portal Page 10

11 Why SAP HANA Cloud Portal? Key points for HCP adoption Page 11

12 The story of SAP HANA Danone Front-end solution for easy site creation and consumption, it brings applications, report and unstructured content together. Flexible and easy branding and customization HTML5 and SAP UI5 based user interface Scalable solution Easy integration of SAP and non-sap sources Sites can easily be duplicated, exported and imported across environments Out-of-the-box mobile consumption and social experience Based on standards (HTML5, LESS, SAML2, CMIS, OpenSocial, SAP UI5) Light CMS capabilities Page 12

13 Monolithic vs Portal based applications Monolithic applications built on top of SAP HANA Cloud Platform (SAP HCP) Application s logic is self-contained Applications run entirely on SAP HCP Portal based applications Composed of widgets Widgets run on SAP HCP Application s logic is driven by widgets and inter-widget communication Portal layer Monolithic applications offer the same UI experience as Portal based ones Page 13

14 Monolithic vs Portal: Deciding criteria How to decide which technology suits best? Is the application eligible for multiple roll-outs? Is it to render according to different branding or theming requirements? Will the functionality and the User Experience differ across deployment units? Will the functionality be reused across sites? Is the functionality based on roles (RBA)? Is the number of screen/pages significant? Page 14

15 Web CRM for DWC B2E scenario - Danone Waters China Web CRM Page 15

16 Web CRM for DWC B2E scenario - Danone Waters China Web CRM Order Management Order Reporting Inquiry Management Credit Check Cockpit Order History Page 16

17 Web CRM DWC Process Flow Is order and delivery progress communicated via workflow/sms??? Page 17

18 Web CRM for DWC Objective: Build an E-Collaborative CRM Platform to be used by Customers, Sales Branch Operators and Customer Service Team, delivering zero-footprint, external facing web front-end to SAP ECC GT Customer Sales Branch CS Team eorder Page 18 Page 18

19 Web CRM DWC Functionality Web CRM DWC accessed by internal users (Danone employees) as well as external users (e.g. sales agents) who do not exist in SAP ECC. Functionality: Business Party Search (Sold-to and Ship-to Party Search) Customer Credit Usage Order Taking (Order Check, Incompletion Log, Validation Workflow) List of orders related to materials Order History Open Invoices Open Reports Order Display and Change Document Flow Page 19

20 From Web CRM DSA to Web CRM DWC In 2013 we built Web CRM for Danone Southern Africa (DSA): monolithic SAP UI5 application interfacing to SAP ECC by means of SAP NetWeaver Gateway (odata). We broke it into reusable components and re-assembled it into the new Web CRM DWC. Back-end functionality (RFCs) reused with little rework. SAP HANA Cloud Portal was the solution chosen for composing the final application Page 20

21 Web CRM DWC: perfect fit for widgetization Web CRM DWC was the perfect candidate for SAP HANA Cloud Portal because: It s a core solution, to build centrally and deploy to multiple Country Business Units (CBUs) CBUs have different branding and theme requirements. A flexible and easy way to address this was needed Functionality (e.g. order report) could be reused by other sites (not necessarily belonging to the same core template) Different user profiles exist and access to functionality is driven by their roles DWC delivers a rich set of functionality (it displays various screens), but more capabilities will be added further down the line (extension should be as easy as possible) Page 21

22 Widgetizing Web CRM DSA into Web CRM DWC Web CRM DSA has been widgetized as follows: Credit Check Order Taking Order History Monolithic Open Reports Business Party Search Open Invoices Business Party Search redeveloped from scratch and embedded in a page template (to enhance performance and unify the look-and-feel). Functionality is mapped to Open Social Portal Widgets and communication employs a broker implementing Pub/Sub pattern. Page 22

23 SAP HANA Cloud Portal Organizational Roles Roles defined in HCP, at subscription level Groups defined in HCP at account level or at subscription level or defined using a dynamic assertion group rule using regular expression of SAML attributes from the IdP Roles are assigned to Groups, Users are assigned to Roles or Groups Roles defined in the platform becomes Organizational Roles in the portal and will have to be added to the site to make them available at page level Based on the groups the user is assigned to, the list of roles is determined and navigation hierarchy is subsequently built Navigation Root Content Page Contentless page Crate Orders Change Orders Display Invoices Page 23

24 User Authentication Internal Users (Danone Employees): Authenticated by Symantec O3 SSO Server SSO Server picks up Windows User IDs, creates SAML2 Token and forwards it to SAP HANA Cloud Portal which, in turn, feeds the token to the widgets in the page Groups are defined in HCP and users are assigned to them Artificial groups (corresponding to SAP PFCG roles) are created on HCP and forwarded, by a Proxy Servlet, to ECC for authorization checks External Users (e.g. Sales Agents): Authenticated by SAP IdP Users created manually on SAP IdP by means of a custom cockpit SAP IDs mapped manually by Administrator upon User Creation No SSO Authentication UI tailored to fit DWC s requirements Page 24

25 The story of SAP HANA Danone B2B scenario - Nutricia Metabolics Web Shop Page 25

26 Nutricia Web Shop User Management Order Management (Shopping Basket) Content Management Cockpit Product Catalog Page 26

27 Nutricia Web Shop: Portal Architecture Nutricia (monolithic) was decomposed into widgets according to functionality: Registration Form Header Footer Product Catagories Product Catalogue Basket Container PDFViewer Shopping Button Some widgets were added to the portal page template whilst others were added to the individual portal pages. Page 27

28 Page 28 Nutricia Web Shop: User Registration

29 Page 29 Nutricia Web Shop: Summary Screen

30 Page 30 Nutricia Web Shop: Order Creation

31 Overall Impressions SAP HANA Cloud Portal is mature and stable platform to build sophisticated user experience, it s reliable and offers an intuitive way to extend existing applications or build new ones on top of SAP HCP. Pros Intuitive Mobile consumption Branding & Theming Navigation & RBA Heterogeneous mash-ups Quick roll-outs Reduced time to market Cons Performance Out-of-the-box widgets Authoring environment capabilities Page 31

32 Future directions Page 32

33 Future directions LATENCY Page 33

34 Future directions BUSINESS Drivers Main reasons for going to cloud: Picture of clouds with OPEX RELIABILITY UX etc, superimposed Page 34

35 Application performance Caching Application deployed on multiple DCs: EU, AP, US. Best response times was to AP. USA Europe Sydney SAP UI5 Shindig HCP Compression Resources from CDN CacheControlFilter (maxage) to cache proxy requests LRU Cache implemented in Proxy Servlet which intercepts all requests. Cache size 500, eviction policy: eldest entry Minification Page 35

36 Future directions smart-routing for direct Rfc calls Cloud infrastructure adaptation user and role management cockpit optimize resources consumption Page 36

37 Future Directions Purchasing Outbound Logicstics HR (Success Factors) Complaint Management CRM DSA B2B rollouts (Russia, DACH) Mobilization Page 38

38 Final thoughts Innovative Spirit Developer skills Collaborate with SAP Page 39

39 Final thoughts Innovative Spirit Developer skills Collaborate with SAP Page 40

40 Page 41 Questions?