SAP HANA Success Story

1. Successful Deployment of SAP Finance Rapidmart
on HANA Platform at Eli Lilly
October 23, 2013

2. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Session Objectives
At the end of this session, you should be able to Understand :
 HANA Program Objectives and Technology Review
 Solution Review (Rapidmart migration, schedule, and required skills)
 SAP SLT (setup, config, replicate, special settings, etc.)
 HANA Performance Optimization
 Key Learnings
Lead Solution Architect
Project Executive
SAP SLT & Basis Architect
Thyagarajan
Balasubramanian
Kiran Yelamaneni
Raj Kandasamy
Associate Partner, IBM
Managing Consultant, IBM
balasubramanian_thyagar
ajan@lilly.com
kyelamaneni@us.ibm.com
312.320.4615
rajaveluk@us.ibm.com
317.656.1062

3. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Agenda

Lilly’s HANA Project Objectives & Technology Review
–
Project Objectives
–
Solution Architecture
Systems Integration and HANA Landscape
–

Solution Review
–
–
–

–
Setup, configuration and integration with non-SAP sources
Data replication, special Settings and issue resolution
HANA Performance Optimization
–
–

Implementation schedule and required resources
SAP SLT Review
–

Solution Migration from Oracle WH to HANA
HANA views, models, universes, BI 4.0 tools setup
HANA table partitions and load balancing
SQL optimizations (TRIM, Case Switch, Run-time Analysis)
Key Learnings

4. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
HANA Program Objectives

Implement scalable, reliable and highly available HANA appliance for Business Analytical solutions

Develop a phased approach for HANA solutions starting with SAP Rapidmart migration to HANA
platform as the Phase I

Minimize business user impact while migrating SAP Rapidmarts to HANA platform by keeping the
reporting layer remain intact (Universes, reports, security, data synchronization, batch schedules,..)

Develop additional business value-cases by leveraging advanced HANA capabilities for Phase II
and beyond

Utilize converged architecture in future when SAP will release HANA capable of running on
virtualized hardware

Establish end-to-end integrated support for HANA solutions as well as HANA Appliance

5. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Solution Architecture for Rapidmart Migration
SAP BusinessObjects BO 3.1 SP 4.2
Web Intelligence
SAP BusinessObjects BI 4
SP4 P4 Web Intelligence,
Explorer
SAP BusinessObjects 3.1 SP 4.2
Server
Business Users
SAP BusinessObjects
BI 4.0 SP4 P4
Reports
(all Webi)
SAP BO Mobile
Reuse BW HR
Extractors; SAP
Rapidmarts for others
SAP HANA
ECC
6.0
Legacy Apps &
External Systems
Phase I - State
•
•
•
SLT Server
SLT Server
Data Services
(3.2 & 4.0 DS)
FACT tables
Master Data
tables
Approximate size is 2.3 TB
1.6 TB is used for indexes
Indexes are not needed to
be copied to HANA
WHP
ORACLE
Explorer
Self-service
Business Analytics

6. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Successfully built SAP HANA Systems Landscape
New Tools
1.Analysis for Office
2.Visual Intelligence
3.Design Studio
4.Information Composer
64-bit Citrix Server for:
HANA Studio and BI tools
DEV
Existing Tools
1.Webi
2.Explorer
3.Dashboards
4.mobile
PRD
DEV
QAS
DEV
Legend:
QAS
New Set of Systems
SAP HANA
Systems
PRD
DEV
DEV
BI 4.0
Systems
PRD
QAS
SAP SLT
Systems
Oracle Data
warehouse
Systems
PRD
PRD
Production promotion path
SAP ERP
Transaction
Systems
Data progression path

7. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Agenda

Lilly’s HANA Project Objectives & Technology Review
–
Project Objectives
–
Solution Architecture
Systems Integration and HANA Landscape
–

Solution Review
–
–
–

–
Setup, configuration and integration with non-SAP sources
Data replication, special Settings and issue resolution
HANA Performance Optimization
–
–

Implementation schedule and required resources
SAP SLT Review
–

Solution Migration from Oracle WH to HANA
HANA views, models, universes, BI 4.0 tools setup
HANA table partitions and load balancing
SQL optimizations (TRIM, Case Switch, Run-time Analysis)
Key Learnings

8. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Solution migration from Oracle WH to HANA
Key Process Steps for SAP Rapidmart migration from Oracle to HANA

9. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
HANA tables, views, models and data volumes
30+ HANA views developed
+
 20+
Attribute Views
+
 3+
Analytical Views
+
 8+
Calculation Views
5 HANA models created for Finance Rapidmart
TB_ACCNT_GRP
Account Info
ACCNT_FROM
ACCNT_TO
ZCFP_MRA
MRA
ZTBMRACC
Company
ZMRA
MG
COMPANYCODE
MGMT_RPTG_AREA
ZCFP_PROFITCENTER
Profit Center
ZCFP_MANUFACTURING
Manufacturing
25+ HANA tables created
Over 300+ mil records loaded
 HANA DEV System
+
• 31+ million
 HANA PRD System
+
• 311+ million
ZCOMPANYCODE
ZSPL_MGMT
COST_SUM_VR_CC
Cost Summary
FSICYEAR
MGMT_RPTG_AREA
FISCAL_MONTH
ZCOST_CENTER_FINANCE_MGMT
Cost Center
ZSPL_MGMT_LEDGER_FACT
Management Ledger
PLANT
ZCOMPANY_CODE
ZACCOUNT_NUMBER
ZRPTG_CATEGORY
ZCOST_CENTER
ZFISCAL_MONTH
ZFISCAL_YEAR
ZMGMT_RPTG_AREA
FISC_PERIOD
ZPROFIT_CENTER
ZMGMT_RPTG_AREA
ZCFP_REPCATEGORY
Category
ZREPCATEGORY
PLANT
Plant
PLANT_ID
TB_THRESHOLD
Threshold
COST_CNTR_ID
VALID_DATE_FROM
COMPNY_CODE_ID
ZSCORECARD_EXP
Scorecard
GL_ACCOUNT_MASTER_DESC
Account Master
ACCOUNTNUM BER
ZPROFITCENTER
ZSCORE_ID
ZBUSINESS_AREA
ZMGMT_RPRT_AREA
ZSCORECARD_HDR
Scorecard Head
ZSCORECARD_ID
ZCFP_ACCOUNT
Account
ZACCOUNT

10. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Successfully installed advanced BI tools
SAP Visual Intelligence
HANA Information Composer

11. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Implementation Schedule
Define
Design
Develop
Deploy
(2 weeks)
(2 weeks)
(6 weeks)
(2 weeks)
End-to-end HANA Services, Consistent Processes and Effective Governance
Program Management
Integration, Replication & Data Management
Apr il
Wor k ing Days
De fine Ar chite ctur e & Scope
Setup/Integrate HA NA , SLT & BO
Def ine/Conf irm M
igration Reports
De s ign Solution
De ve lop & M igr ate Re por ts
Build & replic ate tables
Schem
as, A nalytical V iew s
Calc V iew s, BO Universes
Security, BO Reports
Unit Testing & V erif cation
Te s t & Acce pt Solution
System Integration Testing
User A cceptance Testing
Know le dge Tr ans fe r
De ploy
P
RD System
s/Users Setup
V e r ify & Star t Phas e II
22
26
5
29
03
5
M ay
06
10
5
13
17
5
20
24
5
June
27
31
4
03
07
5
10
14
5
17
21
5
July
24
28
5
01
05
3
08
12
5

12. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Key Project Resources
IBM Roles
IBM CoE / Extended Team
Lilly Roles
Project Executive
•
•
Serve as overall coordinator for SAP HANA Program
Monitor risks (i.e. Technical, Functional, Organizational, Resource related) and take proactive action when needed to drive successful
completion of the project
Project Leader
•
•
Manage HANA program plan and support the team on successful project delivery
Work with IBM project executive on project staffing, project plan updates and status reviews
SAP HANA Modeling Architect
•
•
•
Architect solution, define data models, systems integration and analytics
Design data models, analytical views and calculation views.
Configure data models, load data, performance testing and system tuning
SAP HANA Architect
•
•
•
Partner with HANA Modeling Architect and design the solution architecture
Analyze HANA performance issues and make necessary adjustments.
Review SQL Script design that is used to composing the information views
SAP HANA SME
•
•
•
Review the information model design based on the reporting requirement.
Analyze HANA performance issues and make necessary adjustments.
Review SQL Script design that is used to composing the information views
SAP SLT & Basis Architect
•
•
•
Install and integrate HANA, SLT systems.
Update support patches and provide assistance on SLT replication.
Administer HANA, SLT and BI systems.
SAP SLT SME
•
•
Guide and assist with SLT installation and setup.
Provide best practices for SLT configuration and connectivity / integration.
SAP BI 4.0 SME
•
•
Analyze BOBJ universes, reports, variables to assist HANA Modeling Architect on conversion activities
Assist with building design and technical specifications. Provide guidance and support to convert the reports
BI 4.0 Architect
•
•
•
Install and integrate BI 4.0 with HANA system
Configure JDBC connectivity and Kerberos authentication
Migrate universes and reports from Rapidmarts to HANA environment
SAP BI 4.0 Developer
•
•
Define and develop BI4.0 reports solutions
Design and convert BI 4.0 Universes and Webi reports

13. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Agenda

Lilly’s HANA Project Objectives & Technology Review
–
Project Objectives
–
Solution Architecture
Systems Integration and HANA Landscape
–

Solution Review
–
–
–

–
Setup, configuration and integration with non-SAP sources
Data replication, special Settings and issue resolution
HANA Performance Optimization
–
–

Implementation schedule and required resources
SAP SLT Review
–

Solution Migration from Oracle WH to HANA
HANA views, models, universes, BI 4.0 tools setup
HANA table partitions and load balancing
SQL optimizations (TRIM, Case Switch, Run-time Analysis)
Key Learnings

14. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Leveraged SLT for data replication from non-SAP sources
SAP SLT is an Online/Offline replication tool for HANA 
SAP SLT allows real-time and scheduled data replication for
both SAP and non-SAP systems


Ability to maintain table settings and transformation
capabilities for data filtering, enrichment, etc.

SAP SLT on existing ECC system
Facilitates automatic conversion of non-Unicode data to
Unicode data during data load/replication process
Provides enhanced monitoring capabilities via SAP Solution
Manager 7.1 SP5 and mobile application replication Manager
Separate dedicated SAP SLT server
Pros

Simplified landscape and administration


No software maintenance dependencies
Provides flexibility to connect non-SAP systems without impacting ECC
Cons


Performance impact
Potential software maintenance dependencies

Investment and maintenance effort for separate server / NW instance
After careful and thorough analysis Lilly decided to implement separate dedicated SAP SLT
server to support data replication process

15. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
SAP SLT Setup, Configuration and Integration
Oracle 10.2
NW 7.31 SP6
Setup and Key Installation Steps
1.
2.
3.
4.
Install SAP NW 7.31 ABAP System
Install DMIS_2011_1_731 Add on ( SLT) using SAINT
Apply all DMIS relevant notes for SAP and non SAP Source systems
Adjust ABAP Memory parameter for Dialog and Non Dialog work
process
5. Install HANA client tools
SP5 (REV 55)
Server Configuration Considerations
•
•
•
•
•
Maintain HANA DB connection in transaction DBCO
Enable web Dynpro replication related web services (transaction SICF)
Increase background jobs based on requirements
Assign SLT roles to SLT administrator
Configure SLT connections to source and HANA using transaction LTR
(new transaction LTRC)

16. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
SLT Replication from non-SAP systems
Special Considerations
•
•
•
•
For non SAP (Oracle Source) – Schema name
should be in Capital letter.
Table without keys cannot be replicated. Only initial
load is possible
Monitor SLT Server jobs in SM50 and memory
utilization in ST02 . Adjust settings accordingly.
Some tables require specific reading type for
efficient calculation and replication.

17. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
SLT Replication – Key Issues and Resolutions
•
Could not create connection in LTR ( to HANA and Source)
Solution: Schema Name should be in caps for non SAP Oracle Source
•
Replication fails with ORA 955 Object Already exists
Solution: Whenever replication is stopped and started , Trigger and logging table need to be cleaned up. Only for
Non SAP Source. Fix may come in next SPs
•
Access Plan calculation failed along with memory allocation error on SLT
Solution: First field of tables does not have enough distinct values. Reading type value should set to ‘5’
•
Multiple dumps in ST22 while replicating particular table
Solution: Tables created with mixed cases at multiple places and it has to be set with same case

18. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Agenda

Lilly’s HANA Project Objectives & Technology Review
–
Project Objectives
–
Solution Architecture
Systems Integration and HANA Landscape
–

Solution Review
–
–
–

–
Setup, configuration and integration with non-SAP sources
Data replication, special Settings and issue resolution
HANA Performance Optimization
–
–

Implementation schedule and required resources
SAP SLT Review
–

Solution Migration from Oracle WH to HANA
HANA views, models, universes, BI 4.0 tools setup
HANA table partitions and load balancing
SQL optimizations (TRIM, Case Switch, Run-time Analysis)
Key Learnings

19. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
HANA table partitioning and load balancing
HANA Table Partitions
•Supports Hash, Round Robin and Range
•Enabled multiple partitions with partition type combinations
•Achieved report performance improvement
HANA Load balancing
•Load balancing is very important especially processing large volume of data
on a multi-node environment
•The project team resolved memory overflow errors with effective load
balancing configuration

20. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
HANA - SQL Performance Analysis
HANA Load balancing

Load balancing is very important especially processing large volume of data on a multi-node environment

The project team resolved memory overflow errors with effective load balancing configuration
SQL Trace Settings
SQL Diagnosis
Runtime Analysis of individual column reads
Runtime Analysis

21. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Agenda

Lilly’s HANA Project Objectives & Technology Review
–
Project Objectives
–
Solution Architecture
Systems Integration and HANA Landscape
–

Solution Review
–
–
–

–
Setup, configuration and integration with non-SAP sources
Data replication, special Settings and issue resolution
HANA Performance Optimization
–
–

Implementation schedule and required resources
SAP SLT Review
–

Solution Migration from Oracle WH to HANA
HANA views, models, universes, BI 4.0 tools setup
HANA table partitions and load balancing
SQL optimizations (TRIM, Case Switch, Run-time Analysis)
Key Learnings

22. Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly
Key Lessons
•
•
Build strong team with right mix of skills and HANA experience.
SAP SLT is used for extracting data from non-SAP systems (Oracle) to HANA for the first time. The project
team has to spend significant amount of time resolving data transformation issues by uncovering additional
SLT system settings and capabilities.
• Connectivity and replication settings
• Special SLT settings for non-SAP systems integration
• Source table clean up and Oracle level settings
•
•
•
•
HANA SQL engine does not work exactly as Oracle SQL engine, which means some of the Rapidmart queries
should be reworked on HANA platform to achieve better performance as well as optimal memory
consumption.
HANA DB skills are required to carefully analyze data and apply appropriate table partitions within HANA for
better report results.
Conduct thorough SQL analysis for replacing special calculations and nested joins on BO Universes with
HANA fields for better performance.
Work collaboratively with SAP HANA development team to understand the product limitations and implement
alternate solutions

23. Any Questions

24. Page Break