sap teched 2013 - sap hana success story

Successful Deployment of SAP Finance Rapidmart on HANA Platform at Eli Lilly

October 23, 2013

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

Successful Deployment of SAP Finance Rapidmart on HANA Platform at Lilly

Project Executive

Kiran YelamaneniAssociate Partner, IBM

[email protected]

SAP SLT & Basis Architect

Raj KandasamyManaging Consultant, IBM

[email protected]

Lead Solution Architect

Thyagarajan Balasubramanian

[email protected]

Agenda Lilly’s HANA Project Objectives & Technology Review

– Project Objectives

– Solution Architecture

– Systems Integration and HANA Landscape

Solution Review – Solution Migration from Oracle WH to HANA

– HANA views, models, universes, BI 4.0 tools setup

– Implementation schedule and required resources

SAP SLT Review– Setup, configuration and integration with non-SAP sources

– Data replication, special Settings and issue resolution

HANA Performance Optimization– HANA table partitions and load balancing

– SQL optimizations (TRIM, Case Switch, Run-time Analysis)

Key Learnings


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

HANA Program Objectives


ECC 6.0

Data Services(3.2 & 4.0 DS)

WHP

ORACLE

SAP BusinessObjects BI 4.0 SP4 P4

SAP BusinessObjects BI 4 SP4 P4 Web Intelligence,

Explorer

FACT tables

Master Data tables

Legacy Apps & External Systems

Reports(all Webi)Reports(all Webi)

• Approximate size is 2.3 TB• 1.6 TB is used for indexes• Indexes are not needed to

be copied to HANA

Self-service Business Analytics

Business Users

SAP BO Mobile

Explorer

Phase I - State

Reuse BW HR Extractors; SAP Rapidmarts for others

SAP BusinessObjects BO 3.1 SP 4.2 Web Intelligence

SAP BusinessObjects 3.1 SP 4.2 Server

SLT ServerSLT Server

SAP HANA

Solution Architecture for Rapidmart Migration


Successfully built SAP HANA Systems LandscapeNew Tools1.Analysis for Office2.Visual Intelligence3.Design Studio4.Information Composer

Existing Tools1.Webi2.Explorer3.Dashboards4.mobile

DEV QAS PRD BI 4.0 Systems

DEV PRDSAP HANA

Systems

DEV PRD

SAP SLT Systems

DEV QAS PRD

Oracle Data warehouse

Systems

DEV QAS PRD

SAP ERP Transaction

SystemsLegend: Production promotion path Data progression path

64-bit Citrix Server for:HANA Studio and BI tools

New Set of Systems













Key Learnings


Solution migration from Oracle WH to HANA

Key Process Steps for SAP Rapidmart migration from Oracle to HANA


HANA tables, views, models and data volumes

30+ HANA views developed

PLANT ZCOMPANY_CODE ZACCOUNT_NUMBER ZRPTG_CATEGORY ZCOST_CENTER ZFISCAL_MONTH ZFISCAL_YEAR ZMGMT_RPTG_AREA FISC_PERIOD ZPROFIT_CENTER ZMGMT_RPTG_AREA

ZSPL_MGMT_LEDGER_FACT

PLANT_ID

PLANT

COMPNY_CODE_ID

TB_THRESHOLD

ACCOUNTNUM BER

GL_ACCOUNT_MASTER_DESC

ZACCOUNT

ZCFP_ACCOUNT

ZCOMPANYCODE ZSPL_MGMT

ZCFP_MANUFACTURING

ZREPCATEGORY

ZCFP_REPCATEGORY

FSICYEAR MGMT_RPTG_AREA FISCAL_MONTH

COST_SUM_VR_CC

COST_CNTR_ID VALID_DATE_FROM

ZCOST_CENTER_FINANCE_MGMT

ZPROFITCENTER

ZCFP_PROFITCENTER

ZSCORE_ID ZBUSINESS_AREA ZMGMT_RPRT_AREA

ZSCORECARD_EXP

ZSCORECARD_ID

ZSCORECARD_HDR

ACCNT_FROM ACCNT_TO

TB_ACCNT_GRP ZMRA

ZCFP_MRA

COMPANYCODE MG MGMT_RPTG_AREA

ZTBMRACC

5 HANA models created for Finance Rapidmart

Account InfoMRA Company

Manufacturing

Management Ledger

Cost Summary

Cost Center

Account Master

Scorecard Scorecard Head

Account

Threshold

Plant

Category

Profit Center

20+ Attribute Views 3+ Analytical Views 8+ Calculation Views

20+ Attribute Views 3+ Analytical Views 8+ Calculation Views

25+ HANA tables created

Over 300+ mil records loaded HANA DEV System

• 31+ million HANA PRD System

• 311+ million

HANA DEV System• 31+ million

HANA PRD System• 311+ million


Successfully installed advanced BI tools

SAP Visual Intelligence

HANA Information Composer


Implementation Schedule

Define(2 weeks)

Design(2 weeks)

Develop(6 weeks)

Deploy(2 weeks)

Program Management

Integration, Replication & Data Management

End-to-end HANA Services, Consistent Processes and Effective Governance

22 29 06 13 20 27 03 10 17 24 01 0826 03 10 17 24 31 07 14 21 28 05 12

Working Days 5 5 5 5 5 4 5 5 5 5 3 5

Define Architecture & Scope

Setup/Integrate HANA, SLT & BO

Define/Confirm Migration Reports

Design Solution

Develop & Migrate Reports

Build & replicate tables

Schemas, Analytical View sCalc View s, BO Universes

Security, BO Reports

Unit Testing & Verifcation

Test & Accept SolutionSystem Integration Testing

User Acceptance Testing

Knowledge Transfer

Deploy

PRD Systems/Users SetupVerify & Start Phase II

May June JulyApril


• 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 Executive

• 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 Modeling Architect

• 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 reportsSAP BI 4.0 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 HANA SME

• Guide and assist with SLT installation and setup.• Provide best practices for SLT configuration and connectivity / integration.SAP SLT SME

• Install and integrate BI 4.0 with HANA system• Configure JDBC connectivity and Kerberos authentication• Migrate universes and reports from Rapidmarts to HANA environment

BI 4.0 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 Architect

• 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 reviewsProject Leader

• Define and develop BI4.0 reports solutions• Design and convert BI 4.0 Universes and Webi reports SAP BI 4.0 Developer

• Install and integrate HANA, SLT systems. • Update support patches and provide assistance on SLT replication. • Administer HANA, SLT and BI systems.

SAP SLT & Basis Architect

IBM Roles Lilly RolesIBM CoE / Extended TeamKey Project Resources













Key Learnings


Leveraged SLT for data replication from non-SAP sources

SAP SLT on existing ECC system 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

SAP SLT allows real-time and scheduled data replication for both SAP and non-SAP systems

Facilitates automatic conversion of non-Unicode data to Unicode data during data load/replication process

Ability to maintain table settings and transformation capabilities for data filtering, enrichment, etc.

Provides enhanced monitoring capabilities via SAP Solution Manager 7.1 SP5 and mobile application replication Manager

SAP SLT is an Online/Offline replication tool for HANA

After careful and thorough analysis Lilly decided to implement separate dedicated SAP SLT server to support data replication process


SAP SLT Setup, Configuration and Integration

Setup and Key Installation Steps Server Configuration Considerations

1. Install SAP NW 7.31 ABAP System2. Install DMIS_2011_1_731 Add on ( SLT) using SAINT3. Apply all DMIS relevant notes for SAP and non SAP Source systems4. Adjust ABAP Memory parameter for Dialog and Non Dialog work

process5. Install HANA client tools

• 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)

Oracle 10.2 NW 7.31 SP6 SP5 (REV 55)


• 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.

Special Considerations

SLT Replication from non-SAP systems


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

• Access Plan calculation failed along with memory allocation error on SLT

• Multiple dumps in ST22 while replicating particular table

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 SPsSolution: 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

Solution: First field of tables does not have enough distinct values. Reading type value should set to ‘5’Solution: First field of tables does not have enough distinct values. Reading type value should set to ‘5’

Solution: Tables created with mixed cases at multiple places and it has to be set with same caseSolution: Tables created with mixed cases at multiple places and it has to be set with same case













Key Learnings


HANA table partitioning and load balancing

•Supports Hash, Round Robin and Range•Enabled multiple partitions with partition type combinations•Achieved report performance improvement

•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

HANA Table Partitions HANA Load balancing


HANA - SQL Performance Analysis

SQL Trace Settings

SQL Diagnosis

Runtime AnalysisRuntime Analysis of individual column reads

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

HANA Load balancing













Key Learnings


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


Any Questions

Page Break

sap teched 2013 - sap hana success story

Education

processing large volume

sap finance rapidmart

sap rapidmart migration

hana hana views

sap systems

sap slt

special settings

hana platform