VELUX -

BW on HANA Migration
Contact Persons
• Torben R. Pedersen
– Accenture, SAP AIMS (SAP BW) Group, Denmark
– Project Manager & Technical SME
– [email protected]

• Joakim Frisberg
– Accenture, SAP AIMS (SAP BW) Group, Denmark
– Program Manager & SME
– [email protected]

Copyright © 2013 Accenture All rights reserved. 2

Agenda
• Introduction of VELUX/Presenter
• Project overview
• Project introduction
• Project timeline
• Migration approach
• Learnings

Copyright © 2013 Accenture All rights reserved. 3

Introduction of VELUX/Presenter
Presenter
• Torben R. Pedersen
• Accenture, Denmark
• Project manager & technical SME for HANA migration
• 7 years of experience with SAP BW
– 4 years with VELUX SAP BW installation

Copyright © 2013 Accenture All rights reserved. 4

Introduction of VELUX/Presenter
VELUX
• VELUX is the world’s largest manufacturer of roof
windows. Danish company with headquarters outside
of Copenhagen, Denmark.

15 Production VELUX A/S 40 Sales

Companies Companies

Copyright © 2013 Accenture All rights reserved. 5

Project introduction
• The SAP HANA project at VELUX is a program with two projects:
– A business related project (HANA business case driver)
• End target: implement SAP BPC
– A technical project
• End target: technical migration of the existing BW system to HANA
• HANA Appliance: HP High Availability Disaster Tolerant Scale Out Solution (6 *512
GB per site)

• Project parties:
– VELUX
– Accenture (PM, SAP Basis, Infrastructure, BW )
– HP (SAP HANA Appliance installation)
– SAP (Customer Validation Program, Rapid Deployment Solutions & AGS)
– Steering Committee with representatives from all parties
Copyright © 2013 Accenture All rights reserved. 6
 Project introduction
Going from & to

BPC SAP BO BPC SAP BO

Business Business
SAP Intelligence SAP Intelligence
BPC 10 BPC 10
Data Services Data Services

BWA SAP BW (7.30) BW BW

SP Stack Upgrade
SAP ABAP JAVA ABAP JAVA
BWA (SP04) (SP04)
Dual Stack Split (SP08) (SP08)
SAP HANA Migration

HANA
Oracle Oracle
Rev. 62
(11.2) (11.2)

6 TB of uncompressed Oracle 2,1 TB of compressed HANA

Copyright © 2013 Accenture All rights reserved. 7
Project Introduction
VELUX BW – Short facts
Functional Areas (#40) Technologies
• Logictics • History
– SD Billing, SD Sales, Purchasing, Quality – Established in 2000/2001
Management, Shipment, LE Shipping, Inventory
Controlling, Shop Floor Control, Plant Maintenance, • Backend
Customer Service
– 3.x & 7.x Data Models (& 3.x/7.x in combination)
• Finance • Frontend
– Overhead Cost Controlling, CO-PA, Profit Center – BEx 3.x Web and Analyzer Report & Web Templates
Accounting, General Ledger accounting, Project
System, Accounts Receivable Accounting, Overhead – BEx 7.x Web reports & Web Templates
Order, Cost Center Accounting – Webi MDX (Universes on top of BEx queries)
• Planning – Webi BICS (Limited usage - on top of BEx queries)
– APO Forecast reporting – BO Analysis for Office
– BO Dashboards
• IP
– BPC 10
– Budgeting
• Counts and size • Data Sources
• BPC
– Number of Users: 2.000+ – SAP: ECC, APO, CRM,
– Consolidation (and Planning going forward)
PI, DataServices
– Number of InfoCubes: 350
• … – Non-SAP: Flat Files,
– Number of Reports: 5.000
FTP
– Size (pre migration): 6 TB
Copyright © 2013 Accenture All rights reserved. 8
Project Introduction
SAP HANA Appliance
HP High Availability Scale Out Disaster Tolerant Solution
- 6 x 512 GB blades at each site – additional storage at secondary site

Secondary Site
Primary Site SAP HANA Disaster & Add-on Storage for
SAP HANA Production SAP HANA Sbx, Dev. & QA Non-prod SAP HANA

Storage replication by Continuous Access

Storage replication by Continuous Access

Copyright © 2013 Accenture All rights reserved. 9

 Project Timeline
Jan Feb Mar Apr May Jun July Aug
SP Stack Upgrade
Sandbox
Development
Quality
Production
Dual Stack Split
Sandbox (CUV)
Development
Quality
Production
SAP HANA
HW Installation
Migration Sandbox
Migration Development
Migration Quality
Migration Production

Copyright © 2013 Accenture All rights reserved. 10

Migration Approach
Greenfield or Migration

Greenfield Migra,on
Pro Pro
• Provides the ability to maximize usage of HANA • Retains investments
functionality • Quick benefits after initial database migration
• Quickest route to providing operational realtime
reporting & access to new use cases
• Under-utilized parts of the existing solution
likely to be left out
Con Con
• Higher cost of implementation • Under-utilized / defunct components will also be
migrated
• Less re-use of existing investments • Harder to maximize HANA usage
• Longest route to a complete MI solution • Requires a well designed existing environment to
covering achieve benefits
all required functional areas

• Maximizes usage of HANA Capabilities • When constrained in time or budget

• Required if existing design is sub-optimal • Can work well if current system is effective

Copyright © 2013 Accenture All rights reserved. 11

Lessons Learned
Is it possible to…
• Get a stable BW on HANA environment?
– Yes
• No issues since system was released after go-live

• Get a well performing BW on HANA environment?

– Yes
• Reports are in general faster than with BWA
• Hierarchy reports are really fast
• Loadtime has been reduced significant
– But
• A few exceptions were negative impact has been identified
Copyright © 2013 Accenture All rights reserved. 12
Lessons Learned
Benchmarks – BEx Analyzer Reports
BEx Analyzer Comparison  
Pre Migration (sec)   Post Migration (sec)   Improvement (%)  
Report A   4.7   4   15  
Report B   3.5   2.6   26
Report C   8.1   6.1   25  
Report D   5.9   4.6   22  
Report D + Drilldown   9.7   5.2   46  
Report E   5.2   4.4   15  

Copyright © 2013 Accenture All rights reserved. 13

 Lessons Learned
Benchmarks – BEx Web Reports
Web Reports Comparison  
Pre Migration (sec)   Post Migration (sec)   Improvement (%)
Mangement Reports (sum)   35.8   14.6   59
Mgmt Report A   6.2   2   68
Mgmt Report B   17.9   4   78
Mgmt Report C   11.7   8.6   26
Standard Reports (sum)   66.1   47.6   28
Standard Report A   7.9   4.8   39
Standard Report B   16   10.9   32
Standard Report B + drilldown   36.2   27.9   23
Standard Report C   6   4   33

Copyright © 2013 Accenture All rights reserved. 14

Lessons Learned
Benchmarks – Webi Reports
Webi Report BIP Comparison  
Report   Pre Migration (sec)   Post Migration (sec)   Improvement (%)
Sales & CRM (Sum)   59   30   49
Sales & CRM Report A   25   10   60
Sales & CRM Report B   34   20   41
Logistics (Sum)   149   189   -27
Logistic Report A   22   18   18
Logistic Report B   127   171   -35
SRS (Sum)   56   57   -2
SRS Report A   25   29   -16
SRS Report B   12   13   -8
SRS Report C   9   8   11
SRS Report D   10   7   30

Copyright © 2013 Accenture All rights reserved. 15

Lessons Learned
Benchmarks – Process Chains
Process Chain Execution  
Chain   Pre Migration (min)   Post Migration (min)   Improvement (%)  
Chain 1   64   29 55
Chain 2   291   216 26
Chain 3   28   23 18
Chain 4   69   39 43
Chain 5   272   80 71
Chain 6   122   42 66
Chain 7   31   10 68
Chain 8   436   124 72
Chain 9   238   87 63
Chain 10   232   75 68
Chain 11   463   217 53

Copyright © 2013 Accenture All rights reserved. 16

Lessons Learned
Was it easy to…
• Install the SAP HANA Appliance in the infrastructure?
– No, but not that bad
• It is a complicated solution
• It is new technology, experience is limited from other installation

• Migrate to HANA and reach current system status?

– No, but not that bad
• 100+ SAP Notes applied (purely related to HANA migration)
• 30+ OSS Messages (purely related to HANA migration)
• 4 new HANA revisions applied
• Nights without sleep

Copyright © 2013 Accenture All rights reserved. 17

Lessons Learned
Main Lessons Learned
• Management
• IT steering committee à high project attention
• Sizing
• Take seriously à 20% off can be expensive
• Infrastructure
• New technology à extended installation/error fixing time
• Application/setup
• Performance à Manage expectations
• Stability à Fight for it

Copyright © 2013 Accenture All rights reserved. 18

 Lessons Learned
Main Lessons Learned
• SAP MAX
– “Migration Planning Workshop” à Helps understanding
complexity/risks
• Go-live
– Go-live downtime: 6½ days

– Go-live errors
• Blade causing error during import à Restart of import à 1 Day lost
• Error at storage level à Import paused à 12 hrs lost

– Post go-live errors

• Inconsistent data in BW system
Copyright © 2013 Accenture All rights reserved. 19
 Lessons Learned
Performance
• Manage expectations
– Expect in avg. little improved reporting performance (in
case BWA is in place)
• Hierarchy reporting on HANA provides significant improvement
• Expect some reports can get a negative performance impact

– Expect improved loading performance

• Expect some loads can get a negative performance impact (due to
”bad” ABAP logic)

– Expect to fight for proper performance and stability

Copyright © 2013 Accenture All rights reserved. 20

 Lessons Learned
Performance
• Challenges
– Customers has higher expectations than what can be
realized
• SAP tends to (or used to) oversell/promise to much…

• General
– HANA has got great potential
– Don’t take performance for granted

Copyright © 2013 Accenture All rights reserved. 21

Leassons Learned
Performance - Don’t take performance for granted – Examples
Existing Setup (with BWA) With HANA as DB
Report Before migration Right after migration

1,82
32,30sec.
sec. 32,30 sec.
1,82 sec.

Revision: 50 à 55 (32,3 à 16,12)

Now
Operation mode in HANA/BWA: 3 à 2 (16,64 à 3,30)
HANA Optimize all InfoCubes in MP (3,30 à 1,37) 1,37 sec.

DSO Activation
(HANA Optimized) 250 min. 6½ min.
Limited source system extraction time - a lot of logic and loads
performed within BW (no optimization done)

Process chain 7h 15min. 2h 04min.

Execution
4h 40min. Never completes
Copyright © 2013 Accenture All rights reserved. 22
Questions
• Questions?

Copyright © 2013 Accenture All rights reserved. 23

 Links
HANA Cookbook (good starting point to get input about monitoring, memory usage, migration etc)

https://cookbook.experiencesaphana.com/bw/

Contents: SAP Hana Command Line Tools and SQL Reference Examples for NetWeaver Basis Administrators

http://scn.sap.com/community/hana-in-memory/blog/2013/05/27/andy-silvey--sap-hana-command-line-tools-and-sql-reference-examples-for-netweaver-basis-
administrators

General Documentation Overview:

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

Administration Guide:

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

SAP HANA Backup notes:

http://bobj.sapbiblog.com/2013/03/20/sap-hana-backup-notes/

HANA: Potential failure of connections with scale out nodes

http://www.saptechies.com/hana-potential-failure-connections-scale-out-nodes/

More backup stuff:

http://scn.sap.com/community/distinguished-engineers/blog/2012/12/18/guidelines-for-sap-hana-backup-and-alter-system-reclaim-log

Technical documents, library (ZIP’ed)

http://www.saphana.com/docs/DOC-2171/version/8

HANA System tables and views:

http://help.sap.com/hana/html/monitor_views.html
Copyright © 2013 Accenture All rights reserved. 24
 SAP Notes
HANA – Certified 3rd party tools for HANA (ex backup tools)

• 1730932

HANA - Sizing report for migration of existing BW system

• 1736976 (sizing report for sizing existing BW system)

HANA - Partitioning:

• 1715048 (essential parameters for BW on HANA)

• 1819123 (configuration/optimization of partitioning)

BW – Compression of InfoCubes in a scale-out solution

• 1773398

BW – HANA Optimized DSO optimization for normal DSOs

• 1849497
• Apply SAP note 1888106 & 1884903 in combination with 1849497

ABAP

• 1662726
• Optimizing select with FOR ALL ENTRIES in SAP HANA databased

Copyright © 2013 Accenture All rights reserved. 25

Credential: BW 7.3 on HANA
Scenario
VELUX is the worlds largest roof windows manufacturer. VELUX has 15 production companies and 40 sales companies around the globe. A
strong SAP tradition has resulted in a large and complex BW system which supports all companies with reporting from the entire SAP functional
landscape. Whilst redefining the corporate performance model they sought to energize their BI solution in order to meet future demand by
introducing HANA.

Challenge Solution Results and Benefits

The challenge was to migrate the entire BW Scope: The project should migrate the entire After go live, VELUX has obtained business
system on to HANA. The scope of the project BW system which consisted of: benefits by implementing SAP BW powered by
were: HANA.
• 40 functional areas, including finance,
• Migrate BW to HANA, migrate all four logistics, planning, budgeting (IP), BPC The initial benefits achieved by simple putting the
systems (Sandbox, Development, Quality & consolidation existing data warehouse on HANA:
Production)
• 5000+ reports • Up to 4x faster report execution
• Install disaster tolerant solution, HP’s
• 290 infocubes, 370 DSO’s • Faster loading performance of process chains.
solution for disaster tolerant HANA
Average load time went down by 50%
environment • Multiple frontends; Bex (xls, web), BO
(Webi, Analysis, Dashboards), IP, BPC • Up to 40x shorter DSO activation time
• Allow for new functionality, enabling VELUX
to implement new planning process (BPC) • Integration within VELUX landscape (SAP Long term benefits which can be realized due to
and analytics capabilities (Predictive ECC, BO XI 4, SAP APO, SAP CRM, the implementation of HANA:
Analysis, Management dashboards) legacy systems)
• Future proof data warehouse solution. By
• Start small think big, migrating current data • 2000+ users migrating the entire existing BW solution to
models and flows. Get initial benefits from HANA VELUX got a data warehouse platform
• 6,5 TB of data
migration and then optimize solution going that can leverage future technology and tools,
forward Time: Project was delivered in 7 months. This i.e. Predictive Analysis, HANA studio
included the following activities:
• Going from good to great, VELUX had a • Improving performance of data warehouse, by
stable and well performing data warehouse. • Patch BW to SP8 utilizing the in-memory calculations VELUX will
Reporting performance was achieved be able to implement new planning process
• Split stacks (ABAP & JAVA) on BW system
through the use of BW Accelerator and which requires real-time calculation of data
effective data modeling • Migrate BW database to HANA
• Drastically improve reporting performance. By
• Install HP High Availability Disaster Tolerant redesigning data flows and reports gain the
Scale Out Solution true potential that BW on HANA brings
Copyright © 2012 Accenture All rights reserved. 26