khnc - bw / hana mixed scenarios - news / added value...

KHNC - BW / HANA Mixed Scenarios - News / Added Value /

Customer Examples

Axel Meier, SAP AG, Strategic Customer Engagements (SCE) | Products & Innovation (P&I)

© 2013 SAP AG or an SAP affiliate company. All rights reserved. 2

Legal disclaimer

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.


Agenda

• HANA EDW

• BW on HANA 7.3x Features - Mixed-Scenarios

• BW on HANA - Mixed-Scenarios

• Review of BW on HANA - Mixed-Scenarios

• BW on HANA 7.40 Features - Mixed-Scenarios

HANA EDW


The Data Warehousing Quadrant data

volu

me

huge

modest

number of data models, sources, … modest huge

internet scale business process

(e.g. Ebay, Amazon, …) generating

huge amounts of (sensor) data

fairly modest challenges regarding

semantics, consolidation, harmoni-

zation, integration with other data

few data sources

mix of scenarios with small and

large amounts of data

many (1000s to 10000s) of data

models

many (100s to 1000s) different data

sources

data mart type of setup or

operational (OLTP) analytics

modest number of tables

modest (need for) integrations

between data models

VLDW XLDW

EDW Data Mart

more granular data

sensor / big data

more scenarios

m

ore

sce

na

rio

s

m

ore

co

mb

ina

tio

ns

of s

ce

na

rio

s

HANA

BW


The HANA EDW Blog: http://www.saphana.com/community/blogs/blog/2013/04/03/the-hana-edw


The “HANA-EDW” – strategy and mission

SAP BW-on-HANA is the strategic EDW solution by SAP offering a end-to-end integration

platform for DataWarehousing, Reporting and Planning.

SAP BW is the bracket around the layer, processing and orchestrating the data and metadata

management. SAP BW is also exposing and integrating new features of an EDW and options

based on the innovative SAP HANA platform.

SAP BWs OLAP engine evolves into an Analytic Manager including an „OLAP compiler“,

managing and delegating data intensive operations in SAP HANA.

BW on HANA 7.3x Features -

Mixed Scenarios


Overview: BW / Non-BW - Mixed (EDW) Scenarios powered by BW

on HANA

Interfaces

BI Clients

Analysis Office

WebI, Crystal Reports, Dashboards

Universe BICS Universe SQL

Design Studio Explorer Analysis OLAP

BICS .NET

BW HANA

BICS Java

BW HANA

SQL MDX

Excel

SAP BW Schema

SAP HANA Schema(s)

SAP HANA

HANA Analytic / Calc View

BW OLAP Engine


Interoperability BW and HANA

SAP BW Schema

SAP HANA Schema(s)

SAP HANA


HANA models in BW

• Consume HANA models – treat

them as InfoProvider

BW models in HANA Modeler

• Provide InfoProvider views

HANA schema data into BW

• Transfer data into (E)-DW BW data in HANA Modeler tables

• Transfer data

BW Services for HANA Modeler managed schemas & data


Consumption of SAP HANA models in BW

SAP NetWeaver BW – SAP HANA Mixed Scenarios

SAP BW on

HANA

InfoProvider TransientProvider

CompositeProvider

VirtualProvider

Query

Multi

Provider

SAP BW Schema

SAP HANA Schema(s)

SAP HANA

Query Query



Consumption of SAP HANA Models in BW on HANA TransientProvider vs. VirtualProvider

TransientProvider VirtualProvider

InfoObjects optional InfoObjects mandatory

Limited integration with BW

master data with assigned

InfoObjects (No Nav.

Attributes)

Full Integration with BW

master data

BW Authorizations for

assigned InfoObjects

All BW Authorizations

Combining HANA data with

BW data via

CompositeProvider

Combining HANA data with

BW data via MultiProvider

or CompositeProvider

TransientProvider based on HANA Model

For ad hoc scenarios

Generated not modeled, no InfoObjects required

Full BEx Query support

Can be included in a CompositeProvider to combine with

other BW InfoProviders

VirtualProvider based on HANA Model

For a flexible integration of HANA data with BW managed

metadata (e.g. lifecycle)

Security handled by BW

Full BEx Query support

Can be included to Composite- and MultiProvider to

combine with other BW InfoProviders

Reporting on HANA models in BW-on-HANA (www.saphana.com)

http://www.saphana.com/servlet/JiveServlet/download/1463-2-4312/SDN_HANA_Models_in_BW+FINAL.pdf






http://www.saphana.com/


SAP NetWeaver BW Virtual Master Data

HANA attribute view exposed as master data in BW

No data staging of SAP HANA master data required

Prior to BW 7.30 SP8 / BW 7.31 SP8 information in master

data tables stored in SAP HANA schema could only be

consumed in BW query via staging into BW

SAP BW

on HANA

SAP BW Schema

SAP HANA Schema(s)

SAP HANA Attribute

View

Virtual

Info

Object

Master Data Read

Class

Query

InfoProvider

Virtual

Info

Object

Virtual

Info

Object

SAP HANA

Virtual Master Data on SAP HANA Attribute view

Easy consumption of HANA master data in BW queries


Generate Analytic View for BW

InfoProvider via HANA Modeler

Generated Analytic View contains basic BW

Metadata

Generated Analytic View can be consumed via

SAP HANA interfaces and used in further SAP

HANA models

This enables SAP BO Explorer on BW data

BW InfoCube (HANA-Optimized) and BW DSO

(Standard and HANA-Optimized)

Query Snapshot (SAP Note 1769374)

BW 7.40: BW Composite Provider and

InfoObjects

SAP BW

on HANA

SAP HANA Studio

SAP HANA

Explorer

consumes

BW Schema

SAP HANA

SAP BW Schema

SAP HANA Schema(s)

SAP HANA

HANA Analytic/Calc

Views

generates Info

Cube DSO

Master

Data

BW Models to SAP HANA

Easy BW InfoProvider Consumption

https://service.sap.com/sap/support/notes/1769374


Import of BW InfoProvider in SAP HANA Additional Information

Modeler Unplugged: Episode 1.1 - Importing BW Models as Native HANA Models http://www.saphana.com/community/blogs/blog/2012/09/27/modeler-unplugged-episode-11--importing-bw-models-

as-native-hana-models

Modeler Unplugged: Episode 1.2 - Understanding HANA Models imported from BW http://www.saphana.com/community/blogs/blog/2012/10/04/modeler-unplugged-episode-12--understanding-hana-

models-imported-from-bw

Modeler Unplugged: Episode 1.3 - Exploring Data for HANA Models Imported from BW http://www.saphana.com/community/blogs/blog/2012/10/11/modeler-unplugged-episode-13--exploring-data-for-

hana-models-imported-from-bw

Deploy HANA-models

Export/Import - http://help.sap.com/hana/hana_dev_en.pdf

http://www.saphana.com/community/blogs/blog/2012/09/27/modeler-unplugged-episode-11--importing-bw-models-as-native-hana-models




http://www.saphana.com/community/blogs/blog/2012/10/04/modeler-unplugged-episode-12--understanding-hana-models-imported-from-bw




http://www.saphana.com/community/blogs/blog/2012/10/11/modeler-unplugged-episode-13--exploring-data-for-hana-models-imported-from-bw




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

BW on HANA Mixed Scenarios


BW on HANA Mixed Scenarios Option 1: BW classic

EDW Transform

ED

W

Pro

pagato

r

DSO DSO

Arc

hitecte

d D

Ms

BW

Access

BW

Olap

Composite

DSO

Data Mart Transform

Attr

InfoObject

Txt Hier


BW on HANA Mixed Scenarios Option 1: BW classic - Review

• Business-orientierte Modelling through platform neutral EDW

semantics instead of technical descriptions

• Meta-Data Management: Load request maintained for every data

load as part of standard ‘metadata’

• Integrated Meta-Data and Transport-Management accross all

registered objects

• BW integrated OLAP-Processor is the interface to the Data-

Manager, incl. special feature and performance (i.e. pruning)

support

• Partitionierung based on semantic EDW Definitions (in addition

to DB Partitioning)

• Delta Data-Management: Configuration determines how delta data

changes are handled

• Data-Integrity: Uniform handling of key values for optimal

consistency and performance

• Rejected Data Handling: Complete handling of erroneous data on

a single record and semantic key level

• Near-Line Storage provides a configuration based approach for

aging out data in BW from expensive to ‘near-line tier’

• Authorization: Comprehensive fine-grained-access-control model

for security

• Frontend Support: Limitation to BW supported Frontend’s – no

Support of native SQL-Frontend’s


HANA Studio

BW on HANA Mixed Scenarios Option 2: BW ETL & Staging / HANA SQL-View accessing BW Data

EDW Transform

ED

W

Pro

pagato

r

DSO

Arc

hitecte

d D

Ms

BW

Attr

InfoObject

Txt Hier

DSO

HANA Calc view

Virtual Transform

Gen. HANA

Analytic View

Gen. HANA

Analytic View

Access


BW on HANA Mixed Scenarios Option 2: BW ETL & Staging / HANA SQL-View accessing BW Data - Review


semantics in combination with technical HANA-models (Transfer of

business logic to the data – virtual data-model)




to DB Partitioning)


changes are handled







• Integrated Meta-Data and Transport-Management accross all

registered objects

• Performance- and Functional- Aspects need to be integrated to the

HANA-Modell (no leverage of BW integrated OLAP-Prozessor)

• Combination of the BW-Authorizationconcept with HANA

Priviledges on the level of „Record" and Object (Table or View)

• Frontend Support: Limitation to native SQL-Frontend’s – no support

of BW enabled Frontend’s


HANA Studio

BW on HANA Mixed Scenarios Option 3: BW ETL & Staging / HANA SQL-View accessing BW Data / BW-Provider

connected to HANA-Model (Optional: Use of InfoObjects)

EDW Transform

ED

W

Pro

pagato

r

DSO

Arc

hitecte

d D

Ms

BW

Access

BW

Olap

Composite

HANA Calc view

Virtual Transform

Gen. HANA

Analytic View

Gen. HANA

Analytic View

DSO

Virtual Provider

Attr

InfoObject

Txt Hier


BW on HANA Mixed Scenarios Option 3: BW ETL & Staging / HANA SQL-View accessing BW Data / BW-Provider

connected to HANA-Model (Optional: Use of InfoObjects) - Review






• BW integrated OLAP-Processor is the interface to the Data-

Manager, incl. special feature and performance (i.e. pruning)

support


to DB Partitioning)


changes are handled







• Combination of BW Meta-Data and Transport-Management with de-

coupled transport of HANA-Models



• Frontend Support: Limitation to BW supported Frontend’s – no

Support of native SQL-Frontend’s


HANA Studio

BW on HANA Mixed Scenarios Option 4: BW classic / Persisting BW Query-Results (Snapshot) / HANA SQL-View

accessing Query-Snapshot

ED

W

Pro

pagato

r A

rchitecte

d D

Ms

BW

Access

BW

Olap

EDW Transform

DSO

DSO

Data Mart Transform

Attr

InfoObject

Txt Hier

DSO

Query

Snapshot

Gen. HANA

Analytic View

HANA

Analytic View

HANA Calc view

Virtual Transform

Local

Data


HANA Studio

BW on HANA Mixed Scenarios – SAP BW 7.40 Option 5: BW classic / BW Composite Provider auf Vielzahl von BW Providern / HANA

SQL-View accessing BW Data

EDW Transform

ED

W

Pro

pagato

r

DSO

Arc

hitecte

d D

Ms

BW

Access

Attr

InfoObject

Txt Hier

Composite

Gen. HANA

Calc. View

DSO

DSO

SPO

HANA

Analytic View

Virtual Transform

HANA Calc view

Local

Data


BW on HANA Mixed Scenarios Option 4 and 5: BW classic / BW Composite Provider connected to a variety of BW

Provider / HANA SQL-View accessing BW Data - Review



• Combination of the BW integrated Delta-Data Processing with a

case-by-case defined ETL Delta-Data handling for HANA locale

Data

• Combination of the BW ‚optimale‘ Data-Consistency and Integration

of HANA locale Data i.e. by 'Surrogate-ID'

• Combination of the BW Rejected Data Handling and options provided

by ETL-Tools to handle and process HANA locale data










• Performance- and Functional- Aspects need to be integrated to

the HANA-Modell (no leverage of BW integrated OLAP-

Prozessor)


to DB Partitioning)




HANA Studio

BW on HANA Mixed Scenarios – SAP BW 7.40 Option 6: BW InfoObjects / HANA SQL-View connected to BW Masterdata (HANA

Attribute View)

EDW Transform

ED

W

Pro

pagato

r A

rchitecte

d D

Ms

BW

Access

Virtual Transform

HANA Calc view

Attr

InfoObject

Txt Hier

Gen. HANA

Attribute View

Gen. HANA

Analytic View

Local

Data


HANA Studio

BW on HANA Mixed Scenarios – SAP BW 7.40 Option 7: BW InfoObjects / HANA SQL-View conected (timedep.) BW Masterdata

(HANA Analytic View)

EDW Transform

ED

W

Pro

pagato

r A

rchitecte

d D

Ms

BW

Access

Gen. HANA

Analytic View

Virtual Transform

HANA Calc view

Attr

InfoObject

Txt Hier

Gen. HANA

Attribute View

DSO

DSO

SPO

Composite

T-Attr Txt Hier

InfoObject

Time dep.


BW on HANA Mixed Scenarios Option 6 and 7: BW InfoObject / HANA SQL-View connected to (timedep.) BW

Masterdata (HANA Analytic View) - Review






• Relevante Performance- und Funktionale- Aspekte müssen in

das HANA-Modell integriert werden





• Combination of the BW integrated Delta-Data Processing with a

case-by-case defined ETL Delta-Data handling for HANA locale

Data

• Combination of the BW ‚optimale‘ Data-Consistency and Integration

of HANA locale Data i.e. by 'Surrogate-ID'

• Combination of the BW Rejected Data Handling and options provided

by ETL-Tools to handle and process HANA locale data





Considerations of BW on HANA

Mixed-Scenarios


Considerations of BW on HANA Mixed-Scenarios

BW OLAP

BW

HANA Engine

HANA Schema

Content of this Session

Integrated Solution

+13.000 Installations

SAP-typical Functionality

Analytic Manager

EDW

ETL (Misc Tools)

Real-time (SLT + RDA)

Lifecyle Management

Authorization

Delta-Data Processing

SQL-Interface

HANA-Models

Function to data (in

Combination with HANA-

Models)

ETL (Data Services)

Real-time (SLT)

Analytical Privileges

BW Virtual- and

Composite Provider

based on HANA-

Models

HANA Models based on

BW InfoProvide

HANA field based BW

Objects (BW 7.40)

Bulk-Loader (BW 7.40)


Aspects of leveraging SQL-Frontend & native HANA-Models I

Freedom to choose Front-end tool and Modeling option based on requirements

Use of existing SQL knowledge and skills in the company

Use of existing SQL front-end tools (SAP HANA certification process on-ging)

No option/budget for employee training on BW on HANA frontend tools specifics

BW on HANA OLAP-Compiler (Analytic Manager) features and functions are not required to meet business

requirements


Aspects of leveraging SQL-Frontend & native HANA-Models II

Specific frontend features are currently not available / planned for BW on HANA enabled frontend tools

Leverage data modeling techniques (SAP HANA Views) to increase the performance and to bring the

business logic closer to the data (Function to Data: BW on HANA OLAP compiler / Analytic manager also

pursues this approach)

Flexible options of data modeling with SAP HANA Views (SQL data model) and integration of BW data with

local data (BW on HANA also offers options to Agile Modeling, such as BW workspaces)


Aspects of BW Feature / Functions in combination with SAP HANA

models - I

BW Analysis Authorizations concepts compared to HANA Analytic Privileges - BW uses the "barrier concept“,

HANA uses automatic filtering

Separate content / model life cycle, especially when model extensions have been created on the basis of the

generated HANA views, but also in the areas Locking, naming conventions, impact analyzes ...

BW managed data life cycle and aging mechanisms such as Near-line storage and the active / non-active

data concept are only available and fully functional when the BW reporting layer is used

BW partitioning and derived pruning mechanisms are optimized for data loading and reporting - this functionality

is unused if the reporting layer is not leveraged

Planning - and generally data insert - is not supported by HANA Views. It also requires a thorough integration of

object-layers, as it is provided with BW-IP/PAK and BPC


Aspects of BW Feature / Functions in combination with SAP HANA

models - II

Internal and external value representations: Simple value conversions as "alpha" conversion and currency

shifts are available, but others, such as customer extensions can not be transferred automatically and need to

be re-modeled in HANA.

Improved semantics of the BW InfoObjects may not or only partially taken over by the generated HANA

views, such as Compounding, default client mapping, inventory logic or exception aggregation for keyfigures.

This needs to be re-modeled to augment in the HANA views or by the frontend / client.

Handling of BW hierarchies is deeply integrated in the BW Analytic Manager and is a core function and

strength of BW on HANA. BW hierarchies can not be used with generated or enhanced HANA Views (at least in

the medium term)


The OLAP Compiler in BW-on-HANA

An Example

Figure 1 shows a standard OLAP query result.

The following items are displayed:

- quantities of sold items per product and

country

- number of distinct customers who bought

those products can be seen.

- quantity relative to the overall number of sold

products in a country are presented as

percentages.

Figure 1: Example of a result of an OLAP query

http://tfxz.wordpress.com/2013/02/15/the-olap-compiler-in-bw-on-hana/



Figure 2: Challenges in the example

This means that the quantity key figure and its subtotals has to be calculated prior to calculating key figure

quantity per country.

This means there is an order of processing imposed by mathematics.

Some Challenges in the Example

The numbers of distinct customers do not sum up.

There are 5 distinct customers buying pencils and 3

buying paper, both in Germany (DE), but only 6 are buying

products in DE – and not 5+3=8 –.

There must be 2 customers that have bought both, pencils

and paper. In processing terms this means that the subtotal (e.g. by

country) cannot be calculated out of the preceding

aggregation level (e.g. by country and product) but needs

to be calculated from the lowest granularity (i.e. by

country, product, customer). The calculated key figure quantity per country refers to the

key figure quantity and sets the latter’s values in relation

to its subtotals.



What you can do with SQL

• Classic BW (or SQL-based OLAP tools in general) would issue a

SQL statement that retrieves a rowset (!) similar to the one shown

in figure 3.

• That rowset constitutes the base set of data from which the result

of figure 1 can be calculated.

• Consequently and caused by real-world combinatorics, the result

of the SQL query in figure 3 is likely to be huge in such cases.

• The “sub-result” needs to be further processed, traditionally in an

application server, e.g. SAP BW’s ABAP server or the

WebIntelligence server.

A huge amounts of data have to be transported from the DB server

to such an application server or a client tool !!!

Figure 3: Rowset retrieved by a SQL query to

calculate result of figure 1



The “OLAP Calculation Graph”

There is a natural sequence of how to calculate the

- various formulas (behind the calculated key figures)

- various SQL group aggregations (i.e. the subtotals and

totals).

Figures 4a and 4b show the resulting dependency graph:

LQ is the label for the query of figure 3.

- L1, L2, …, L6 are “queries” or calculations on top.

- BW’s OLAP compiler derives that graph and sends it

down to the SAP HANA Query-Optimizer (using a

proprietary interface) where SAP HANA optimizes and

processes that graph and sends back the result. as in fig.

1). - Post-processing step is executed to receive the result and converts it to the desired result set of the OLAP

query (i.e. a cell-set as in fig. 1).

Figure 4a: Graph derived for processing the final result (as in fig. 1) from

the data in fig. 3



Figure 4b: Structure of the OLAP Calculation Graph

Concluding Remarks

1. Even though individual processing steps can be expressed

via SQL, it is in the end a well defined sequence of processing

steps that yield the result.

2. Transport a potentially huge SQL query result set over the

network to the client in order to calculate on the client level.

3. BW-on-HANA resolves those issues by:

• providing a powerful option to define an OLAP query – i.e.

the BEx query – this is a precondition to allow all of that in

the first place, sending down the entire “processing graph”

to HANA and allowing HANA to optimize and pipeline the

individual processing steps, and

• having the capability to assemble the partial results of the

processing steps into the final (OLAP) result.

BW on HANA 7.4 Features -

Mixed Scenarios


MetaData & Modeling - Full Functionality in SAP BW 7.40

Object Interoperability between BW and HANA: BW HANA


SAP BW InfoProvider consumption in SAP HANA

BW 7.30-on-HANA

Generate SAP HANA View in HANA Modeler for InfoCube &

DSO

Derive SAP HANA Analytic Priviledges

BW 7.40-on-HANA

Automatic HANA View generation

SAP BW Composite Provider and BW InfoObject as

additional InfoProvider types

Life Cycle coupled to SAP BW

SAP BW Analysis Authorizations based on SAP BW data

© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Thank you

Axel Meier

Strategic Customer Engagements (SCE) | Products & Innovation (P&I)

SAP AG

[email protected]

mailto:[email protected]

mailto:[email protected]


© 2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth

in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and

other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx



khnc - bw / hana mixed scenarios - news / added value...

Documents