DMM301 – SAP BW powered by SAP
HANA – Mixed Scenario Overview and
Experiences
Public
Speakers
Las Vegas, Oct 19 - 23
Barcelona, Nov 10 - 12
 Sebastian Baumgärtner
 Dr. Oliver Schall
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
2
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
3
Agenda
Introduction / Motivation for Mixed Case Scenarios
Overview of Mixed Scenario Architectures
Experiences with:
 BW on HANA Transformations
 Generated HANA Views
 Integrating HANA Views
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
4
Mixed Architecture with SAP BW and SAP HANA
Definition
SAP’s best practice for modern data warehousing
A Mixed Architecture consists of an overall data model that is
implemented at the same time by BW and native HANA tools
 It combines processes, data and metadata of BW and
HANA native (= best-of-both-worlds to gain additional
insight and flexibility)
 SAP HANA and SAP BW deliver integrated tools to
manage mixed scenarios end-to-end including modeling,
transport mechanisms and consumption interfaces.
 SAP HANA Database as central runtime for reporting and
data warehouse processes offering best in class
performance and scalability for large data warehouses
i
DMM300 (L1)
Modeling modern Data Warehouses based on
SAP BW and SAP HANA, Mixed Architectures
BI Clients
<
SAP BW
Mixed Architecture
HANA Modeling
BW Modeling
SAP HANA
Sources
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
5
Introduction / Motivation
Mixed Case Scenarios
In addition to “classic” BW scenarios, pure native modeling capabilities are now available as well as
BW powered by HANA (BW optimized with HANA features, e.g. BW on HANA Transformations)
More possibilities / larger flexibility
New know-how / guidelines / best practices required
This session aims to provide insight / experiences how to approach modeling and shows different
options
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
6
Introduction / Motivation
Mixed Case Scenarios
Application requirements and the existing landscape are drivers for a new architecture
and its focus area
We will introduce selected options in an overview before showing best practices for detailed
implementation aspects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
7
Architecture Overview
Public
Architecture Overview
Staging Capabilities
Repository
SAP BW
SAP HANA Views
Data Warehousing
SQLScript
SAP BW provides HANA enabled
Transformations with optimizations for
standard functionality as well as the ability to
use HANA Expert Script (“SQL Script Exit”)
Data Acquisition
SAP HANA
Sources
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
9
Architecture Overview
BI Clients
SAP
HANA
Views
Repository
SAP BW
SAP
HANA
Views
Generated HANA Views for BW Info
Providers
Neglects reporting layer and does use BWs
staging capabilities
Data Warehousing
Data Acquisition
SAP HANA
gen.
SAP
HANA
Views
Often driven by client decision which does not
have a tight integration with BW backend (BW
query, BICS)
Sources
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
10
Architecture Overview
BI Clients
Generated HANA Views for BW Queries
SAP BW
Analytic Engine
BW Query
Data Warehousing
Workspaces
Repository
BW Query
Data Acquisition
gen.
SAP
HANA
Views
gen.
SAP
HANA
Views
Alternative to previous scenario with usage of
analytic engine
Re-use of certain query properties possible
(e.g. restricted / calculated keyfigures) for BI
clients with shallow BW integration
SAP HANA
Sources
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
11
Architecture Overview
BI Clients
Integration of modeled HANA Views from
agile scenarios
SAP BW
Analytic Engine
Repository
BW Query
Composite Provider
SAP
HANA
Views
Replicated and processed data from a
separate schema is integrated into BW
Data Warehousing
Data Acquisition
SAP HANA
HANA view is consumed in a Composite
Provider / Open ODS View and mixed with
BW data
Sources
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
12
Architecture Overview
BI Clients
Integration of modeled HANA Views from
agile scenarios
SAP BW
Analytic Engine
Repository
BW Query
Composite Provider
SAP
HANA
Views
Data management completely native
Integration into BW to use feature-set of
analytic engine
SAP HANA
Sources
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
13
BW on HANA Transformations
Repository
SAP BW
SAP HANA Views
Data Warehousing
SQLScript
Data Acquisition
SAP HANA
Sources
Public
BW on HANA Transformations
Why to use Transformations with HANA Execution?
HANA enabled transformations avoid data roundtrips between application server and database
Better parallelization inside the HANA database
Better performance / more flexibility (adaptation of HANA features)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
15
BW on HANA Transformations
How do Transformations with HANA Execution work?
After the design of the transformation capability whether HANA processing is possible is shown
Similar to generated program for ABAP the generated HANA Transformation can be displayed
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
16
BW on HANA Transformations
HANA Analysis Process
Calculation Scenario
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
17
BW on HANA Transformations
Prerequisites for Transformations with HANA Execution
Supported targets: Standard + Write-optimized DSO, Advanced DSO (ADSO), SPOs based on DSOs, OpenHub destinations for DB tables or 3rd party tools
Queries as Info Providers are not supported as a source
ABAP routines are not supported (field routine, characteristic routine, start routine, end routine, expert routine)
Rule groups are not supported
Read from DSO  entire key must be specified
Near-line connections are not supported
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
18
BW on HANA Transformations
The DTP combines Transformations between two Info Providers with persistence.
HANA Expert Script
0BW_OPER_PROC
HAP
TR_00O2TMRZFVSBOQ6FLWQERAEAH
Standard
0BW_PROJECTION
HAP
TR_00O2TMRZFVSBOQ6FLWQERAEAH2
Standard
0BW_PROJECTION
HAP
TR_00O2TMRZFVSBOQ6FLWQERAEAH1
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
DTP_00O2TMRZFVSBOQ6FLWQERAEAH
Public
19
BW on HANA Transformations
The calculation scenarios for the related transformations are stacked.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
20
BW on HANA Transformations
During the HANA Execution of a DTP (availability can be checked) an package-wise “insert as select”
statement is generated
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
21
BW on HANA Transformations
Prerequisites for HANA Execution Availability of a DTP
Error handling is deactivated; no requests in the DTP error stack
No semantic grouping
Data target is DSO  “subsequent processing without master data” is selected
Data target is Open Hub  data target is database table or 3rd party tool
Data source is DSO  Delta Init from Active Table (with Archive) not set
Data source is BW Data Source  Extraction is performed from PSA table
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
22
BW on HANA Transformations
Novel BW 7.50 features
In data flows with multiple transformations HANA Expert Script and ABAP Transformations can be mixed (HANA Expert Script must be first transformations)
Data Target with SIDs are also supported (e.g. Info Cube, Info Object)
Start-, End- and Field routines can be implemented in SQL Script
ABAP and SQL Script can both be implemented in a Transformation at the same time (where only one can be active)
Intermediate results can be displayed in the DTP simulation mode
PERI7 conversion exit is supported
DTP with error handling is supported
ADSO with NLS-IQ archive is supported as a source
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
23
BW on HANA Transformations
Conclusions how to approach design / development
Use standard push-down capabilities (only use HANA Expert Script if necessary)
•
allows the execution in ABAP as well as HANA  easier for functional debugging; later HANA as performance mode
•
profit from general improvement of the HAP framework
•
transferring ABAP code to SQL Script in AMDPs requires careful review from performance perspective
•
new skillset for programming / debugging / performance analysis required (new debugging features with HANA SP10)
•
expert routine was often used to avoid “overhead” of the generated program  no driver for HANA Expert Script
•
please review Note 2057542 - Recommendation: Usage of HANA-based Transformations
Avoid the usage of many Info Sources for one DTP
•
embedded calculation scenarios create complex plans which are complicated to analyze
•
even optimized plans might contain more operations than necessary  performance drain
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
24
Generated HANA Views
BI Clients
Sources
gen.
SAP
HANA
Views
BW Query
BW Query
Data Warehousing
Workspaces
Data Warehousing
Analytic Engine
Repository
Repository
SAP
HANA
Views
SAP HANA
SAP BW
SAP
HANA
Views
SAP BW
Data Acquisition
BI Clients
gen.
SAP
HANA
Views
gen.
SAP
HANA
Views
Data Acquisition
SAP HANA
Sources
Public
Generated HANA Views
Modeler Usage based on Info Provider models
leads to many content objects which require maintenance:
•
Transport Management / Consistency
•
Visibility / Privileges for many content objects
Activation times of content objects increase (dependency handling)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
26
Generated HANA Views
Decrease of activation times
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
27
Generated HANA Views
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
28
Generated HANA Views
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
29
Generated HANA Views
Data Categories
<blank> - output node type projection, no
hierarchy views
<CUBE> - output node aggregation, hierarchy
views
<DIMENSION> - output node projection, no
hierarchy views, no measures
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
30
Generated HANA Views
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
31
Generated HANA Views
Composite Provider
Usage simplifies:
•
Transport Management / Consistency / Visibility / Privileges directed by BW
•
Composite Provider does only deploy one view (no dependency problem)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
32
Generated HANA Views
Composite Provider
Modeler has a more comprehensive feature-set compared to the Composite Provider
Composite Provider restricted to:
•
•
•
Pure union logic (consumable)
Joins (inner, left outer) on unions (not consumable)
Text joins / Navigational attribute joins are performed on top of actual calculation scenario
 improvements planned in BW 7.50
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
33
Generated HANA Views
External Query Views
Composite Provider is an Info Provider
BW Info Provider sometimes / often do not represent a complete view on the data regarding end-user
expectations
External Query Views add analytical capabilities compared to Composite Provider
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
34
Generated HANA Views
Supported
Ignored
Not Supported
Characteristics
Hierarchy display settings
Filter on a hierarchy
Nav. Attributes with standard master data
access type
Default values for characteristics
Constant selection
MIN, MAX, SUM Keyfigures
Conditions, Exceptions
Cell definitions
Restricted / Calculated Keyfigures
(Note 2080686)
Local calculations (frontend driven calculations)
Exception aggregation
Non-cumulative Keyfigures (exception
aggregation LAST; Note 2032830)
Display options (number of decimal places)
Elimination of internal business volume
Currency Translation
Zero suppression
Quantity Conversion
Query properties (cache mode, read mode, near-line storage mode)
Variables (Manual Entry / Default value)
Hidden key figures
Filters (one variable per characteristic;
only multiple single value variables
supported)
Display attributes
Stable data during navigation
Structures
More detailed information:
http://help.sap.com/saphelp_nw74/helpdata/en/cd/4fa7a807014032a88d882bb91dffbc/content.htm
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
35
Generated HANA Views
Novel BW 7.50 features
HANA Exit (analog to customer exit)
SAP Exit Variables (0CMONTH, 0CWEEK, 0CYEAR, 0CQUART, 0DAT)
Pruning (for NLS connections and SPOs; Note 2190204)
External HANA Views for InfoObject Hierarchies
XXL Attributes in the External Master Data HANA View
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
36
Generated HANA Views
Conclusions / Short Summary
Precondition: data is located in BW Info Providers
Publishing on physical Info Provider level enables more flexible modeling with larger feature set at the
expense of higher maintenance efforts.
Future BW feature enhancements can be simply adapted by regeneration of the external HANA views.
Decision is influenced by existing landscape, release level, application requirements and the reporting
client decision and its integration depth into BWs analytic engine.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
37
Integrating HANA Views
BI Clients
BI Clients
SAP BW
Repository
BW Query
Composite Provider
Data Warehousing
SAP
HANA
Views
Analytic Engine
BW Query
Repository
Analytic Engine
SAP BW
Composite Provider
SAP
HANA
Views
Data Acquisition
SAP HANA
Sources
SAP HANA
Sources
Public
Integrating HANA Views
Why to integrate HANA Views?
Data is located partly or completely outside of BW
Data might have been processed / produced by any HANA native application
Integration into BW is desired to:
•
combine data for subsequent processing (e.g. planning)
•
use features dedicated to the analytic engine
•
create a persistence in BW
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
39
Integrating HANA Views
How to integrate HANA Views (or external data)?
Two new providers are available in BW 7.40
Composite Provider
•
combines data from BW Info Providers (Info Object, DSO, SPO, Info Cube, HANA Views, Open ODS Views) for reporting
Open ODS View
•
integrates / conforms data from external objects like database tables, database or HANA views, virtual tables or BW
Datasources with direct access
•
can generate ADSO (Advanced Datastore Object) as persistence in BW
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
40
Integrating HANA Views
Modeling options
1) Integration of database table, database
view or virtual table only possible via
Open ODS View
2) Integration of HANA View into Composite
Provider via Open ODS View
3) Direct Integration of HANA View into
Composite Provider
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
41
Integrating HANA Views
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
42
Integrating HANA Views
Performance Implications
Conforming models to BW (e.g. ALPHA conversion, no integer datatype for characteristics)
•
basic conversions available in Open ODS View (calculation scenario since BW 7.40 SP8)
•
SQL View  not recommended as it can disrupt query optimization especially before HANA SP10
•
more complex conversions can be explicitly modeled in a calculation view (cast operations with calculated columns)  might
prevent filter push-down / causes larger intermediate results
•
conversion during staging / HANA optimized transformations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
43
Integrating HANA Views
Performance Implications
Query Execution
Part Providers may be requested separately from CP
scenario; results are merged differently depending on
query execution mode
mode 3  ABAP OLAP
mode 6  merge in query calculation scenario
Open ODS View creates Calculation Scenario which is
able to represent associations to Info Objects
Composite Provider creates transient scenario on top of
its own scenario in BW 7.40 (improved in BW 7.50)
Composite Provider uses a special union operator with
BW semantics (union in HANA view not equivalent, e.g.
pruning)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
44
Integrating HANA Views
Conclusions / Short Summary
Goal: external data should be integrated into BW
Two Info Providers available: Open ODS View and Composite Provider
Consider functional aspects (feature-driven) which Provider to use
Performance aspects influence the modeling approach
•
additional encapsulation of information view into Open ODS View might be beneficial
•
consider effects of conforming data types (Open ODS View Conversions to staging solution via HANA enabled
transformations)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
45
SAP TechEd Online
Continue your SAP TechEd education after the event!
 Access replays of keynotes, Demo Jam, SAP TechEd live interviews, select lecture sessions, and more!
 Hands-on replays
http://sapteched.com/online
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
46
Further Information
Related SAP TechEd sessions
DMM300 - Modeling Data Warehouses Based on SAP BW and SAP HANA, Modern Architectures
DEV103 – Migrating from the Repository to Deployment Infrastructure for SAP HANA
DEV161 – Introduction to SQL Script (Hands-On Workshop)
DEV360 – Using Advanced Features of SQL Script (Hands-On Workshop)
SAP Public Web
scn.sap.com
www.sap.com
SAP Education and Certification Opportunities
www.sap.com/education
Watch SAP TechEd Online
www.sapteched.com/online
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
47
Feedback
Please complete your session evaluation for
DMM301.
©©2015
2015
SAP
SAP
SESE
oror
anan
SAP
SAP
affiliate
affiliate
company.
company.
AllAll
rights
rights
reserved.
reserved.
Public
4848
Thank you
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
49