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

Transcription

1 KHNC - BW / HANA Mixed Scenarios - News / Added Value / Customer Examples Axel Meier, SAP AG, Strategic Customer Engagements (SCE) Products & Innovation (P&I)

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 SAP AG or an SAP affiliate company. All rights reserved. 2

3 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

4 HANA EDW

5 data volume The Data Warehousing Quadrant huge of scenarios internet scale business process (e.g. Ebay, Amazon, ) generating huge amounts of (sensor) data HANA more granular data sensor / big data more scenarios modest fairly modest challenges regarding semantics, consolidation, harmonization, integration with other data few data sources data mart type of setup or operational (OLTP) analytics modest number of tables modest (need for) integrations between data models VLDW Data Mart XLDW EDW mix of scenarios with small and large amounts of data many (1000s to 10000s) of data models many (100s to 1000s) different data sources more scenarios more combinations BW modest number of data models, sources, huge 2013 SAP AG or an SAP affiliate company. All rights reserved. 5

6 The HANA EDW Blog: SAP AG or an SAP affiliate company. All rights reserved. 6

7 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 SAP AG or an SAP affiliate company. All rights reserved. 7

8 BW on HANA 7.3x Features - Mixed Scenarios

9 Overview: BW / Non-BW - Mixed (EDW) Scenarios powered by BW on HANA BI Clients Analysis Office Design Studio Analysis OLAP WebI, Crystal Reports, Dashboards Explorer Excel Universe BICS Universe SQL Interfaces BICS.NET BICS Java BW HANA BW HANA BW OLAP Engine SQL MDX HANA Analytic / Calc View SAP BW Schema SAP HANA Schema(s) SAP HANA 2013 SAP AG or an SAP affiliate company. All rights reserved. 9

10 Interoperability BW and HANA HANA models in BW Consume HANA models treat them as InfoProvider HANA schema data into BW Transfer data into (E)-DW BW Services for HANA Modeler managed schemas & data BW models in HANA Modeler Provide InfoProvider views BW data in HANA Modeler tables Transfer data HANA Analytic / Calc View SAP BW Schema SAP HANA SAP HANA Schema(s) 2013 SAP AG or an SAP affiliate company. All rights reserved. 10

11 SAP NetWeaver BW SAP HANA Mixed Scenarios Consumption of SAP HANA models in BW SAP BW on HANA Query Query Query CompositeProvider Multi Provider InfoProvider TransientProvider VirtualProvider HANA Analytic / Calc View SAP BW Schema SAP HANA Schema(s) SAP HANA 2013 SAP AG or an SAP affiliate company. All rights reserved. 11

12 Consumption of SAP HANA Models in BW on HANA TransientProvider vs. VirtualProvider 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 TransientProvider InfoObjects optional Limited integration with BW master data with assigned InfoObjects (No Nav. Attributes) BW Authorizations for assigned InfoObjects Combining HANA data with BW data via CompositeProvider VirtualProvider InfoObjects mandatory Full Integration with BW master data All BW Authorizations Combining HANA data with BW data via MultiProvider or CompositeProvider Reporting on HANA models in BW-on-HANA ( SAP AG or an SAP affiliate company. All rights reserved. 12

13 Virtual Master Data on SAP HANA Attribute view Easy consumption of HANA master data in BW queries 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 Virtual Info Object Query InfoProvider Virtual Info Object Virtual Info Object SAP BW on HANA Master Data Read Class SAP HANA Attribute View SAP HANA SAP BW Schema SAP HANA Schema(s) 2013 SAP AG or an SAP affiliate company. All rights reserved. 13

14 BW Models to SAP HANA Easy BW InfoProvider Consumption 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 ) BW 7.40: BW Composite Provider and InfoObjects SAP BW on HANA Master Data Info Cube SAP HANA SAP BW Schema BW Schema SAP SAP HANA HANA DSO generates Explorer consumes SAP HANA Studio HANA Analytic/Calc Views SAP HANA Schema(s) 2013 SAP AG or an SAP affiliate company. All rights reserved. 14

15 Import of BW InfoProvider in SAP HANA Additional Information Modeler Unplugged: Episode Importing BW Models as Native HANA Models Modeler Unplugged: Episode Understanding HANA Models imported from BW Modeler Unplugged: Episode Exploring Data for HANA Models Imported from BW Deploy HANA-models Export/Import SAP AG or an SAP affiliate company. All rights reserved. 19

16 BW on HANA Mixed Scenarios

17 EDW Propagator Architected DMs BW on HANA Mixed Scenarios Option 1: BW classic Access BW Olap Composite DSO InfoObject Attr Txt Hier Data Mart Transform DSO DSO EDW Transform BW 2013 SAP AG or an SAP affiliate company. All rights reserved. 21

18 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 22

19 EDW Propagator Architected DMs BW on HANA Mixed Scenarios Option 2: BW ETL & Staging / HANA SQL-View accessing BW Data Access HANA Calc view InfoObject Attr Txt Hier Virtual Transform DSO DSO Gen. HANA Analytic View Gen. HANA Analytic View EDW Transform BW HANA Studio 2013 SAP AG or an SAP affiliate company. All rights reserved. 23

20 BW on HANA Mixed Scenarios Option 2: BW ETL & Staging / HANA SQL-View accessing BW Data - Review Business-orientierte Modelling through platform neutral EDW semantics in combination with technical HANA-models (Transfer of business logic to the data virtual data-model) Meta-Data Management: Load request maintained for every data load as part of standard metadata 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 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 24

21 EDW Propagator Architected DMs 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) BW Olap Access Composite Virtual Provider HANA Calc view InfoObject Attr Txt Hier Virtual Transform DSO DSO Gen. HANA Analytic View Gen. HANA Analytic View EDW Transform BW HANA Studio 2013 SAP AG or an SAP affiliate company. All rights reserved. 25

22 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 Business-orientierte Modelling through platform neutral EDW semantics in combination with technical HANA-models (Transfer of business logic to the data virtual data-model) Meta-Data Management: Load request maintained for every data load as part of standard metadata 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 Combination of BW Meta-Data and Transport-Management with decoupled transport of HANA-Models Combination of the BW-Authorizationconcept with HANA Priviledges on the level of Record" and Object (Table or View) Frontend Support: Limitation to BW supported Frontend s no Support of native SQL-Frontend s 2013 SAP AG or an SAP affiliate company. All rights reserved. 26

23 EDW Propagator Architected DMs BW on HANA Mixed Scenarios Option 4: BW classic / Persisting BW Query-Results (Snapshot) / HANA SQL-View accessing Query-Snapshot Access BW Olap Query Snapshot InfoObject Attr Txt Hier DSO Data Mart Transform HANA Calc view Virtual Transform DSO DSO Gen. HANA Analytic View HANA Analytic View EDW Transform BW HANA Studio Local Data 2013 SAP AG or an SAP affiliate company. All rights reserved. 27

24 EDW Propagator Architected DMs 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 Access Composite HANA Calc view InfoObject Attr Txt Hier SPO Virtual Transform DSO DSO Gen. HANA Calc. View HANA Analytic View EDW Transform BW HANA Studio Local Data 2013 SAP AG or an SAP affiliate company. All rights reserved. 28

25 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 Business-orientierte Modelling through platform neutral EDW semantics in combination with technical HANA-models (Transfer of business logic to the data virtual data-model) Meta-Data Management: Load request maintained for every data load as part of standard metadata Performance- and Functional- Aspects need to be integrated to the HANA-Modell (no leverage of BW integrated OLAP- Prozessor) Partitionierung based on semantic EDW Definitions (in addition to DB Partitioning) Near-Line Storage provides a configuration based approach for aging out data in BW from expensive to near-line tier Combination of BW Meta-Data and Transport-Management with decoupled transport of HANA-Models 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 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 29

26 EDW Propagator Architected DMs BW on HANA Mixed Scenarios SAP BW 7.40 Option 6: BW InfoObjects / HANA SQL-View connected to BW Masterdata (HANA Attribute View) Access HANA Calc view InfoObject Attr Txt Hier Virtual Transform Gen. HANA Attribute View Gen. HANA Analytic View EDW Transform BW HANA Studio Local Data 2013 SAP AG or an SAP affiliate company. All rights reserved. 30

27 EDW Propagator Architected DMs BW on HANA Mixed Scenarios SAP BW 7.40 Option 7: BW InfoObjects / HANA SQL-View conected (timedep.) BW Masterdata (HANA Analytic View) Access Composite InfoObject Attr Txt Hier InfoObject Time dep. T-Attr Txt Hier SPO HANA Calc view Virtual Transform DSO DSO Gen. HANA Attribute View Gen. HANA Analytic View EDW Transform BW HANA Studio 2013 SAP AG or an SAP affiliate company. All rights reserved. 31

28 BW on HANA Mixed Scenarios Option 6 and 7: BW InfoObject / HANA SQL-View connected to (timedep.) BW Masterdata (HANA Analytic View) - Review Business-orientierte Modelling through platform neutral EDW semantics in combination with technical HANA-models (Transfer of business logic to the data virtual data-model) Meta-Data Management: Load request maintained for every data load as part of standard metadata Relevante Performance- und Funktionale- Aspekte müssen in das HANA-Modell integriert werden Near-Line Storage provides a configuration based approach for aging out data in BW from expensive to near-line tier Combination of BW Meta-Data and Transport-Management with decoupled transport of HANA-Models 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 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 32

29 Considerations of BW on HANA Mixed-Scenarios

30 Considerations of BW on HANA Mixed-Scenarios BW OLAP Integrated Solution Installations SAP-typical Functionality Analytic Manager BW Virtual- and Composite Provider based on HANA- Models HANA Models based on BW InfoProvide Content of this Session HANA Engine SQL-Interface HANA-Models Function to data (in Combination with HANA- Models) BW EDW ETL (Misc Tools) Real-time (SLT + RDA) Lifecyle Management Authorization Delta-Data Processing HANA field based BW Objects (BW 7.40) Bulk-Loader (BW 7.40) HANA Schema ETL (Data Services) Real-time (SLT) Analytical Privileges 2013 SAP AG or an SAP affiliate company. All rights reserved. 34

31 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 35

32 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) 2013 SAP AG or an SAP affiliate company. All rights reserved. 36

33 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 37

34 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) 2013 SAP AG or an SAP affiliate company. All rights reserved. 38

35 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 2013 SAP AG or an SAP affiliate company. All rights reserved. 40

36 The OLAP Compiler in BW-on-HANA 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 Figure 2: Challenges in the example key figure quantity and sets the latter s values in relation This to its means subtotals. 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 SAP AG or an SAP affiliate company. All rights reserved. 41

37 The OLAP Compiler in BW-on-HANA 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 SAP AG or an SAP affiliate company. All rights reserved. 42

38 The OLAP Compiler in BW-on-HANA 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). Figure 4a: Graph derived for processing the final result (as in fig. 1) from the data in fig. 3 - 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) SAP AG or an SAP affiliate company. All rights reserved. 43

39 The OLAP Compiler in BW-on-HANA 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. Figure 4b: Structure of the OLAP Calculation Graph 2013 SAP AG or an SAP affiliate company. All rights reserved. 44

40 BW on HANA 7.4 Features - Mixed Scenarios

41 MetaData & Modeling - Full Functionality in SAP BW 7.40 Object Interoperability between BW and HANA: BW HANA 2013 SAP AG or an SAP affiliate company. All rights reserved. 46

42 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. 47

43 Thank you Axel Meier Strategic Customer Engagements (SCE) Products & Innovation (P&I) SAP AG 2013 SAP AG or an SAP affiliate company. All rights reserved.

44 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 for additional trademark information and notices SAP AG or an SAP affiliate company. All rights reserved. 49