SAP Big Data Forum 2013 A1 Dietmar Gasch - Bayer


Published on

Published in: Travel, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SAP Big Data Forum 2013 A1 Dietmar Gasch - Bayer

  1. 1. Thoughts and experiences about a path to SAP Business Suite powered by SAP HANA Dietmar E. Gasch, former Head and Global Process Owner at Bayer MaterialScience Page 1 • DIETMAR E. GASCH • OCTOBER 2013
  2. 2. PATH TO HANA CRM parameters of MyCo Reasons for HANA Proof of Concept The Move to HANA CRM after HANA Business Suite on HANA outlook Page 2 • DIETMAR E. GASCH • OCTOBER 2013
  3. 3. CRM parameters of MyCo  One single instance each: ERP, SCM, CRM, GTS, MDM, BW  SAP CRM was part of our global system landscape  CRM designed as single source for the 360° customer view  Replaced > 15 legacy systems  Very huge number of functionalities are available and used  Sales, Marketing and Service processes  Interaction Center  Web Shop including process automation (High e-commerce ratio)  Overall approximately 11.500 users internal and external Page 3 • DIETMAR E. GASCH • OCTOBER 2013
  4. 4. Reasons for HANA  Speed  CRM is about finding 360° customer data quickly  Non-indexed searches were slow = no acceptance  With HANA most searches hopefully improve. Users acknowledge the improvement and tend to accept the system better.  Analytics  Non-HANA CRM returns information on a detailed document level  With HANA we hoped to leverage analytical capabilities and to present results on aggregate level while enabling drilldown options  Mobility and Web Shop  With HANA the mobile applications can be used  Faster access to relevant information for our customers (via web shop) Page 4 • DIETMAR E. GASCH • OCTOBER 2013
  5. 5. Proof of Concept - Method  A copy of the productive CRM system was upgraded to the HANA version  Another copy acted as reference system  Use cases have been defined to compare both versions  The performance of the use cases were measured on the original system  After migration of the data base to HANA, the same use cases were measured in the HANA machine  Non satisfying results were analyzed and optimized in cooperation between SAP and MyCo  High Performance Analytics (in our case: customer segmentation) have been installed and evaluated Page 5 • DIETMAR E. GASCH • OCTOBER 2013
  6. 6. Proof of Concept - Results  Increased Performance Results of Test Cases - comparing Any DB, HANA, optimized HANA System  High Stability of the System 90% -27,1s 93% -22,5s Page 6 • DIETMAR E. GASCH • OCTOBER 2013 88% -27,5s 94% -20,2s  No base code adjustments needed  Optimizing code adds performace in some use cases  HPA created high business interest
  7. 7. POC PERFORMANCE ERP transaction “Material Document List” (MB51) • processed with several kind of selection criteria  HANA always ~1 second ! Runtime in seconds Any DB HANA Single Batch 64,40 0,12 Material in Plant & Movement Type 22,71 1,07 Plant at Posting Date Single Order 56,17 0,15 1,39 0,26 User in Posting Month 222,04 0,40 240 180 120 60 0 Single Batch • DIETMAR E. GASCH • OCTOBER 2013 P1Z Material in Plant & Movement Type Single Order P1X Plant at Posting Date User in Posting Month 7
  8. 8. Move to HANA Sandbox  Gain experience with most recent software versions  Document findings for fast productive Implementation  Interact with SAP for fast solution and optimization  Intensive functional and integrated testing  Load testing in a close to productive setup Development QA System Production  Update system, implementation of solutions from sandbox  Refine and implement optimization recommendations  Integrated business process test  Saveguarding the Go Live Page 8 • DIETMAR E. GASCH • OCTOBER 2013
  9. 9. Move to HANA - Result  Hardware  Data base migration is as short and problem free as described by SAP.  Data base compression rate is ca. 66%  The application server might be a bottleneck when sized too small.  SAP standard and self developed coding  Some standard code can reduce the performance advantage. SAP is working on this as part of the Suite on HANA roadmap.  Optimization of some own coding to the HANA development guidelines can increase performance  Data Base Performance: truly a speedy system  In some cases the use of indexes improves even HANA performance Page 9 • DIETMAR E. GASCH • OCTOBER 2013
  10. 10. CRM after HANA  User experience  The bigger the search the bigger the gain  Interaction center response times are faster  Web shop response is much faster for information queries of customers  Hyper care and pain points  In 4 weeks after go live not 1 HANA related incident ticket  Account management performance suboptimal, SAP solution is underway  Continuous improvement  Optimization of slowing codes ongoing @ MyCo and SAP  Definition and installation of interesting HPA’s Page 10 • DIETMAR E. GASCH • OCTOBER 2013
  11. 11. Business Suite on HANA an outlook  Base code adjustments will continue @ SAP to make HANA as efficient as possible  Hardware will change from appliance to virtualized set up  Application server to run integrated on HANA  One data set for all applications only  Fade out of business warehouse functions will be possible, when external data can be integrated into HANA  Non volatile memory technology in the hardware producer’s pipeline adds final potential for cost saving (no more transactional storage needed)  All of the above will lead to reduced TCO, thus the question for a company will not be if but when to move to HANA Page 11 • DIETMAR E. GASCH • OCTOBER 2013
  12. 12. Thank you Page 12 • DIETMAR E. GASCH • OCTOBER 2013