This document discusses SAP BW on HANA and its value proposition. It outlines implementation options for deploying BW on HANA, including a mixed deployment with HANA Live and S/4 HANA. Key considerations for the optimized deployment of HANA include data loading, scheduling, maintenance, analysis and reporting. The document also discusses assessing customer BI landscapes, the architecture of BW on HANA, and empowering BI capabilities with use cases. It provides recommendations on sizing BW for HANA, general problems during migration, and the value proposition of BW on HANA including virtualization, real-time data, flexible modeling, increased availability and lower TCO.

1. SAP BW ON HANA
High Level
Service Architecture, Out-put,
Implementation Issues & Value Proposition
December, 2015

2. SAP BW IN THE AGE OF EVERYTHING HANA
SAP HANA Live
Implementation /
Migration to BW
on HANA
HANA Business
Suit S/4 HANA
Mixed
Deployment
BW BI implementation / deployment options on HANA

3. BW ON HANA OPTIMIZED DEPLOYMENT
Considering multiple options for HANA deployment scenarios we need
to assess the most efficient ways HANA can be deployed in an
organization.
Data loading, data scheduling, data maintenance
Analysis & reporting
Planning
Efficient
Reliable
Maintainable

4. HANA AS PLATFORM FOR ENTERPRISE
HANA DB HANA LIVE S/4 HANAHANA PLATFORM

5. CUSTOMER BI LANDSCAPE ASSSESSMENT
Current app landscape matrix can help understand BI solution needs

6. +
BW ON HANA - BEST OF BOTH WORLDS
SAP NETWEAVER
PLATFORM
SAP HANA PLATFORM
SAP NEW DATA MODEL - LAYERED SCALABLE ARCHITECTURE (LSA++)
BI Content for
enterprise data
warehouse capabilities,
Business content
evolved over yeas of
research
Explorative and
interactive real-time
analytics using the SAP
HANA in-memory
database
SAP HANA-optimized BI Content (BW ON HANA)

7. BW NETWEAVER + HANA OPTIMIZED = LSA++
Planning
Non-cumulative key
figures based models
Data load scheduling and
monitoring capabilities
Complex reporting
scenarios using master
data
BI business content
Extractors, Infocubes, Relational Data
Store objects, datasources, queries)
Delta capabilities of standard
extractors processing huge datasets
designing complex reporting scenarios,
historical
Master data enrichment with
attributes, text, hierarchies
Multiple tables extracted in one
datasource
changing organization structure
current master data point of view,
historical, or at a point in time,
IP Infocubes, Input ready Queries,
SAP BPC
Single app planning consolidation and
reporting
Process chains, OpenHubs capabilities
inventory, headcount

8. BW on HANA ARCHITECTURE
8
Web Methods
Legacy Apps
SLTECC (FI, CO,
SD MM)
Manual
Sources
Composite Provider
BEx Query
Data
Services
BO
Mobile
ExplorerLumira
BO Design
Studio
BO WEBI
Other
DW
HANA Schema
BW Schema
DSO DSO DSO DSO DSO
Analytical / Calculation Views
HANA LIVE
InfoProvider Transient Provider
Open
Hub
HANA
DB
BO Front end tools

9. BW ON HANA EMPOWERING BI
CAPABILITIS OF CUSTOMER – USE CASES
Master data NEEDS to be very up to date, near zero latency.
Master data IS UPTODATE, achieving near zero latency.
HANA real time Master data
attribute
Activation-less Loading of BW Master Data
Fast SLT replication to HANA

10. BW ON HANA EMPOWERING BI
CAPABILITIS OF CUSOMTER – USE CASES
NEED a navigational attribute of a navigational attribute
With HANA, Attributes NO NEED to copy attributes
joins CV_WBS through
HANA model
Modelling Navigational Attributes of Navigational Attributes
Region – > Person -> Project

11. BW ON HANA EMPOWERING BI
CAPABILITIS OF CUSOMTER – USE CASES
LARGE master data, with 000’s of records
Reports only needing ONE REGION retrieved from only one InfoObject
HAN modeling unions the
InfoObjects
Horizontal Partitioning of BW Master Data
Horizontal Partitioning of
Master data by Regions

12. BW ON HANA EMPOWERING BI
CAPABILITIS OF CUSOMTER – USE CASES
Deployment of BW template configuration, InfoObject has many rows with
LOCALISATION needs
LOCALISTTION INFO can be added separate InfoObjects
HANA modeling join with
the localisation object
Vertical Partitioning of BW Master Data
Multiple objects to hold Loc.
info

13. BW ON HANA EMPOWERING BI
CAPABILITIS OF CUSOMTER – USE CASES
Key figures must be summed across every transaction since the start.
NO ADDITONAL efforts or process is needed, and memory use is still kept to a
minimum, with in-memory and on Compressed disk
Available for all previous
years, no carry forward
solution required
Modelling last N years to Date Key Figures
Required KF Columns will be
stored in memory, rest in
compressed format on disk
Semantically Partitioned Object (SPO)
is partitioned by year. Generated SPO
Partition DSOs contain year data each.

14. BW ON HANA EMPOWERING BI
CAPABILITIS OF CUSOMTER – USE CASES
BW on HANA systems where HANA Live is also deployed
NO REDUNDANT effort to extract for BW on HANA with HANA already deployed
Traditional FI GL ECC
extraction
Handling BW extraction and HANA Live replication of similar
data
FI GL for BW on HANA data used
from HANA Live
No redundant effort to extract
for BW on HANA
Logic
Logic
Logic

15. HIGH LEVEL RECOMMENDATIONS
Sizing BW for HANA
No wild guesses must use SAP QuickSizer
In case of single HANA database, BW and all other apps require intendent sizing and added
together
Consult SAP sizing notes for right sizing guidelines and select recommend server hardware mix
Follow best practices for migration, upgrade team should keep up-to-
date with SAP latest notes
Take care with BW versions, Service packs, EhPs, Choose the right approach for BW upgrade and
DMO, always read the latest notes
Use the right tools e.g. The application-specific upgrade (ASU ) toolbox, PCA, SW provisioning
manger, and SUM, UC and NUC conversions
General BW housekeeping
care about outdated date, inconsistent data and corrupted data, carry out BW house cleaning first

16. GENERAL BW PROBLEMS DURING MIGRATION
SAP BW SERVER MEMORY CAN IMPACT THE IMPORT OF DATA INTO HANA DB
CPU Chips on SAP BW SERVER NEED TO BE SUPPORTED BY THE HANA NODES AND PROGRAMS
RUN DATA CHECK PRIOR TO THE DATABASE EXPORT TO ENSURE NO DUPLICATE DATA IN ANY
FIELDS
RUN A TEST RUN OF ON THE PROPOSED INFRASTRUCTRE TO MINIMISE SURPRISES
BE CLEAR ABOUT HANA LICENSCING
ADAPT A FLEXIBLE APPROACH TO INFRASTRUCTURE WITH CONSTANTLY CHAING VERSION
AND PATCHES
FOCUS ON BACKUP AND RECOVERY SHOULD YOU LOOSE SERVER OR DATABASE

17. BW ON HANA VALUE PROPOSITION
HANA-Optimized InfoProvider
Virtualization of persistent Data Marts
Query-able all EDW layers
Virtual Data Marts
Real Time EDW Master Data, load to
report quickly
New easier Modeling options
Flexible Master Data Modeling by slicing
attributes
Large Master Data Modeling, partitioning
increased availability, lower TCO
increased availability, lower TCO
increased availability, lower TCO
increased flexibility, lower TCO
new solutions, lower TCO
increased flexibility & coverage of
business needs
By virtually joining semi-stable master
data in HANA accessible in BW
realignment through compounding
instead of fact-table join
Following BI technical enhancements eliminate many pain areas for IT managers, Consultants and
Enterprises creating tangible cost savings and streamlining BI solutions of the future

18. HANA IMPLEMENTATION PARTNER
HANA Advisory
services
Implementation
integration and
migration
Cost-effective
solutions
Data modelling,
mining and
reporting
APPs on HANA
A HOLISTIC APPROACH FOR ENTERPRISE LEVEL HANA STRATEGY
Right HANA Implementation partner can make all the difference ….
..between this ..and this

19. Thank You!
19
Waheed Abbas
SAP & Non-SAP BI Consultant
Email: wabbas.uk@gmail.com