bi216

SAP HANA 1.0 Implementation at MedtronicKiran Musunuru

Medtronic, Inc.

Sougata Dutta

SAP America

BI216

2 | MDT Confidential

In This Session …

• Understand why Medtronic chose to leverage SAP HANA

• Learn about the solution architecture and key integration points with SAP Business Warehouse (BW), BusinessObjects Data Services (DS), and the BusinessObjects Enterprise (BOE) Suite

• Learn about data modeling with Sybase PowerDesigner and HANA Studio

• Hear about project challenges and keys to success as well as future plans


What We’ll Cover …

• Medtronic Background• Business Drivers for HANA Solution Selection• Solution Architecture• Key Integration Points• Data Modeling Approach• Project Challenges & Keys to Success• Benefits, Outcomes & Future Plans• Wrap-up


Medtronic Impact Today

Employees: 38,000 Countries: 120 Locations: 270Revenue: $16B+Earnings: $3.5B+


Medtronic IT & BI Facts

• Complex Environment– Highly Regulated Industry– Over 700 Business Applications

• Innovative IT and Business Culture– One of the fastest adopters of iPads– Single Global SAP ERP Instance Strategy– Significant SAP footprint (Over 15 Applications)

• Significant Need for Data and Information– 2 Enterprise Data Warehouses, Many Large Data Marts– Large amounts of data not accessible or underutilized


So, Why SAP HANA?

Performance, Performance, Performance!!!

• In-Memory– Removes I/O overhead – even with the best storage technology,

this is the #1 culprit for performance issues

• Columnar– Enables fastest query operations for typical reporting workloads

• Low-Maintenance– No more need for overhead of maintaining aggregates and

indexes


And, Beyond Performance…

Multi-Source Data Acquisition – Best of Both Worlds!

• Non-SAP Sources– BW weakness overcome

• SAP Sources– Continued tight integration via BW, Data Services, SLT, and Sybase

Replication Server is extremely valuable

Long Text Handling – No problem!

• Large amounts of unstructured text data not easily handled by BW

• Single field storage and search capabilities


HANA Part I at Medtronic: Global Complaint Handling (GCH)

A complaint is any communication that alleges deficiencies related to the identity, quality, durability, reliability, safety, effectiveness or performance of a distributed device, and it’s associated labeling, packaging, or training materials.

• We serve 7 Million Patients annually, making more than 100,000 different finished goods, and 60,000 components -> big data

• Our goal is to provide the greatest possible quality and reliability in our products and services

• We want to be able to proactively sense the smallest signal in our environment before it ripples into a problem for patients


Lesson: Select A Good Business Case

• Need for breakthrough in performance and flexibility– Volume - data comes from different sources– Variety - structured + text, heterogeneous applications – Velocity - breakthrough in speed, interactive analysis

• IT program chartered with implementing a common complaint handling system for use in all business units and geographies.

• Enables global visibility across all product lines• Ensures timely reporting and response


SAP HANA: Project Implementation Overview

Solution Selection

BusinessCase

Level 2Workshop

Project Preparation

Kick-OffInstallation &

Setup of Systems

Project Planning Selection of Data Sets

IntegratedData Modeling

Security Planning

Reporting Tool Identification

Deployment Data Acquisition via DS

HANAModeling

Implement Security Build Reports

Production Go-Live

User Training System Support


GCH Reporting Architecture – Data Sources

Staging Record• Business Partners• Documents• Tasks• Communications

Product Event• Partner Functions

• Business PartnersProduct Line Item

• Product• Asset• Associated Drugs• Tasks• Codes• Analyses• Investigations• Reportability Decisions

Regulatory Inquiries

GCH

(SAP CRM)

ImplantsDART (Siebel)

CallsCRTS

ReturnsRPL

Sales (2004 - Present)Centerpiece (SAP

ERP)

Sales (1996 - 2007)JD Edwards – 14

installations

Sales (pre-1993? - 1999)TOPS

Sales (pre-1993? - 2000)Midas


GCH Reporting Architecture – Key Principles

• Leverage existing investment in SAP BW made in prior releases of GCH

• Use SAP BW for what it does best – acquisition of data from SAP applications

• Move long text from SAP CRM directly to SAP HANA due to inability for SAP BW to handle > 60 characters

• Use Medtronic Custom Data Integration Layer for acquisition of non-SAP data as well as Master Data harmonization

• Build an integrated data model in SAP HANA to enable high-performance reporting via SAP BusinessObjects


GCH Reporting Architecture – Data Flow


GCH Reporting Architecture – Platform

• SAP HANA Appliance– Cisco UCS w/ 512 GB RAM– Suse Linux Enterprise Server

(SLES) 11– HANA 1.0 SP2

• SAP BusinessObjects Data Services (DS)

– MS Windows Server 2008– DS 4.0 SP1

• SAP BusinessObjects Enterprise (BOE) Suite

– IBM AIX 6.1– BOE 4.0 SP2

• SAP Business Warehouse (BW)– IBM AIX 5.3 / IBM DB2 LUW 9.7– BW 7.01


SAP BusinessObjects Data Services

• ETL from all source systems to HANA using DS Data Integrator

– SAP BW – via OpenHub– SAP CRM – via RFC– Custom Data Integration Layer

(Oracle DB) – via ODBC

• DS connectivity to HANA via ODBC

SAP BW Oracle DB

SAP BusinessObjects Data Services

SAP In-memory Computing EngineSAP

HANA (Appliance)

SAP CRM


DS Data Flow – Example


SAP BusinessObjects Enterprise Suite

• GHC Ad-Hoc Reporting Solution delivered using BusinessObjects Web Intelligence (WebI)

• BOE connectivity to HANA via JDBC

SAP In-memory Computing EngineSAP

HANA (Appliance)

SAP BusinessObjects BI 4.0

Semantic Layer

CrystalWebI Dashboards

Explorer A Office

SQL(ODBC/JDBC)

BICS

Mic

roso

ft

Exc

elM

DX

(O

DB

O)

DBSQL

Crystal

SQL(JDBC)


Modeling Physical Tables in HANA

• With multiple data sources and business requirements for Ad-Hoc reporting on related data, an Integrated Data Model was a must

– BW DSOs for Complaint Data (modeled in BW)– Long Text (part of SAP CRM application)– Non-SAP Sources in Custom Integration Layer (modeled using Sybase

PowerDesigner)

• Elected to use Sybase PowerDesigner to build Integrated Data Model from all sources

– Majority of team members already familiar with the tool– HANA is ANSI SQL compliant and therefore allows for PowerDesigner

generated DDL to be used to create the physical tables in HANA


Sybase PowerDesigner Data Model - Example


Sybase PowerDesigner Generated DDL - Example


SAP HANA studio – Attribute, Analytic, and Calculation Views

• Attribute Views – “Dimensions”– Add context to data– Can be regarded as Master Data tables– Can be linked to fact tables in Analytical Views

• Analytic Views – “Cubes”– Multidimensional reporting model– Fact table (data foundation) joined against modeled dimensions (attribute

views)

• Calculation Views – “Virtual Provider with Services”– Column view that implicitly executes a function on access– Function defined in the HANA-specific language ‘SQL Script’


HANA Studio – Example Attribute View


Project Challenges

• Installation of Data Services 4.0 is supported on platforms which do not have a supported ODBC driver for connectivity to HANA

Cross-Reference SAP Product Availability Matrix (PAM) to ensure installation of tools as well as drivers for HANA connectivity are supported (applies to DS and BOE)

• Project team members with extensive database experience struggled to understand the value of using views in HANA

Views should be created for all tables, even when the view is a 1:1 match of the physical table itself. If you can generalize views so that joins occur in HANA rather than the reporting layer do so

• Lack of Experience & Best Practices

Leverage SAP Consulting in order to have direct access to the development organization, trust SAP, prototype as often as you can.


Keys to success

Select a strong business case – Helps implementing expensive technology

Get executive and product support from SAP– Helps implementing in new technology

Do a Level 2 Workshop– Helps implementing in validating use case to capabilities efficiently

Look for a hybrid of knowledge/experience in traditional DW and SAP BW– Need to handle SAP BW and non SAP data

Consider using your existing standard data modeling tool– Sybase PowerDesigner


Project Results & Outcomes

Global Complaint Handling Go Live With HANA – 10/16/2011

• Integration Test Results

• Performance Test Results

• User Experience Feedback


HANA Part II at Medtronic: Global Sales Reporting (GSR)

The Global Sales Reporting (GSR) project purpose is to standardize the information provided to the Sales Forces globally to support and enhance their ability to sell Medtronic product

• Introduce Sybase Replication Server for real-time replication of Open Orders from ERP

• Custom Web Application to write data into HANA (via Data Services) in real-time for Sales Forecast


Long-Term Roadmap for HANA at Medtronic


Additional Sessions

Medtronic/Cisco Session - BI220 on Thursday at 10:30 AM

SAP Insider Reporting and Analytics Conference 2011 in Las Vegas in November for a post go-live update


Resources

http://help.sap.com/hana/

Plattner, Hasso and Alexander Zeier. In-Memory Data Management.Heidelberg: Springer, 2011

http://www.sapinmemorycomputing.comproduct site

https://cw.sdn.sap.com/cw//community/docupedia/hanadocupedia (requires login)

http://help.sap.com/hana/

http://www.sapinmemorycomputing.com/

https://cw.sdn.sap.com/cw/community/docupedia/hana


Questions - Your Turn!

Sougata [email protected]

Kiran [email protected]