SAP HANA Live & SAP BW Data Integration A Case Study Matthias Kretschmer, Andreas Tenholte, Jürgen Butsmann, Thomas Fleckenstein July 2014
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. 2014 SAP AG. All rights reserved. 2
SAP NetWeaver BW New SAP Apps Partner Apps SAP HANA Live + SAP NetWeaver Business Warehouse Comprehensive operational + historical analytics and planning powered by SAP HANA SAP NetWeaver Business Warehouse on SAP HANA Multi-channel Unified User Experience SAP Business Suite Strategic and tactical Integration, harmonization, crosssystem consistency Consumption Planning Preconfigured content Data lifecycle Data governance Full-blown analytical suite SAP NetWeaver Multi-sourced data SAP HANA PLATFORM Application Services Database Services (include Virtual Data Models) SAP HANA Live Synchronizations Services Operational data Real-time Uniform Deployment model Lightweight modeling and consumption Model reuse in analytical applications Extensible All analytics requirements fulfilled with one unified solution 2014 2014 SAP SAP AG AG. or AG. All an rights SAP All rights affiliate reserved. reserved. company. All rights reserved. 33
tomorrow today Possible Hybrid Scenario BI Clients and other UI s Additional Data Marts SAP Business Suite (e.g. ERP) BW/OLAP Any DB Any DB Transact. Tables SAP DWH Data Data Staging BI Clients and other UI s SAP Business Suite (e.g. ERP) BW/OLAP Any DB/HANA HANA SAP HANA Live Other Datamart HANA optim. Transact. Tables Real-time replication (SLT) Transact. Tables HANA Tables SAP DWH Data Real-time replication 2014 2014 SAP SAP AG AG. or All an SAP rights affiliate reserved. company. All rights reserved. or Data Staging 44
SAP HANA Live & SAP BW Data Integration Scenarios* Scenario A: Transactional data provisioning via HANA Live Query View in BEx Query (Consumption of SAP HANA Live query views in BW via ODP Transient Provider) Scenario B: Transactional data provisioning via HANA Live Reuse View enriched by BW master data (Consumption of SAP HANA Live reuse views in BW adding BW master data features using Composite Provider) Scenario C: BEx Query with key figures based on historical/plan BW data and most current SAP HANA Live data (Consumption of SAP HANA Live views and BW DataStore Object by CompositeProvider in BW) Scenario D: Transactional and master data via HANA Live consumed by BW (Consumption of SAP HANA Live transactional and master data views by Open ODS Views in BW) Other possible scenarios: Historic BW data virtually accessed via HANA Calculation View which combines HANA Live and BW data (Custom built HANA Calculation View combines data from HANA Live view and BW generated HANA views) Loading of data into BW using Reuse Layer of HANA Live as data source (Extract data from HANA Live reuse views into BW) *Note: An SAP HANA Live and SAP BW data integration is also possible when both components are deployed on two different SAP HANA databases. In that case different integration capabilities are used. 2014 SAP AG. All rights reserved. 5
Scenario Description (standard content perspective) ERP Sales & Distribution Standard Entities HANA Live Content Reuse Calculation View: SalesOrderItem BW Content DataStore Object: Sales Document Item Data InfoObjects: e.g. 0CUSTOMER 2014 SAP AG. All rights reserved. 6
Scenario Description (custom content perspective) ERP Sales & Distribution Custom Entities HANA Live Content Calculation View BW Content Composite Provider BEx Query 2014 SAP AG. All rights reserved. 7
Integration Scenario A: Transactional data exploration via HANA Live Query View in BEx Query Consumption of SAP HANA Live query views in BW via ODP Transient Provider From SAP HANA Live 2014 SAP AG. All rights reserved. 8
Architecture for Integration Scenario A: Transactional data exploration via HANA Live Query View in BEx Query Consumption of SAP HANA Live query views in BW via ODP Transient Provider Capabilities All HANA Live Views automatically exposed as InfoProvider in BEx Query Designer Supports BEx variables Supports restricted key figures Supports exceptions and conditions Supports BW Report-to-Report interface Supports HANA Live privileges SAP BW on HANA BEx Query Transient Provider Not supported (Query not based on BW InfoObjects): - BW Hierarchies, node variables - BW analysis authorizations SAP BW Schema HANA Live Calculation View SAP HANA Schema(s) SAP HANA 2014 SAP AG. All rights reserved. 9
Recommendations / Findings for Integration Scenario A: Transactional data exploration via HANA Live Query View in BEx Query For query execution same user in BW and HANA database is required It is recommended to use only SAP HANA Live query views Input Parameters / Variables in SAP HANA Live query views must be defined as static filter in the BEx Query e.g. fix value or mandatory variable Quick way to add BW functionality without using BW modeling objects, but BW analysis authorizations & BW hierarchies are not supported BEx Queries created on ODP Transient Provider can be transported through the BW landscape as long as SAP HANA Live is deployed in each system 2014 SAP AG. All rights reserved. 10
Integration Scenario A Transactional data exploration via HANA Live Query View in BEx Query Step 1 BEx Query: Choose InfoProvider Create a new query in BEx Query Designer and search in InfoAreas for HANA Live query views Note: HANA packages (e.g. sap.hba.ecc) are exposed as InfoArea with all HANA Live views In BW 7.30 / 7.31 HANA views can be found in Unassigned Nodes Alternatively search for description of the HANA Live query view in the Name field 2014 SAP AG. All rights reserved. 11
Integration Scenario A Transactional data exploration via HANA Live Query View in BEx Query Step 2 BEx Query: Define BEx Query Definition a) Define the BEx Query using e.g.: Filter, variables Free characteristics, rows, columns Restricted & calculated key figures, formulas, structures, cell definition Conditions and exceptions b) As a minimum, you need to define a characteristic restriction (fix filter or mandatory variable without allowing initial values) for all Input Parameters / Variables defined in the corresponding HANA Live View 2014 SAP AG. All rights reserved. 12
Integration Scenario B: Transactional data exploration via HANA Live Reuse View enriched by BW master data Consumption of SAP HANA Live reuse views in BW adding BW master data features using CompositeProvider From BW From SAP HANA Live 2014 SAP AG. All rights reserved. 13
Architecture for Integration Scenario B: Transactional data exploration via HANA Live Reuse View enriched by BW master data Consumption of SAP HANA Live reuse views in BW adding BW master data features using CompositeProvider* Capabilities (in addition to Scenario A) For flexible integration of HANA Live data with BW managed master data (e.g. lifecycle, consolidated / harmonized master data) Security handled by BW authorizations only Full Support of BW hierarchies e.g. node variables Full Support of time dependent master data Full BEx Query support SAP BW on HANA Master Data Master Data BEx Query Composite Provider Transactional Data Note This scenario can also be implemented by using Open ODS Views instead of a CompositeProvider. SAP BW Schema HANA Live Calculation View ( Reuse Layer) SAP HANA Schema(s) SAP HANA *Prerequisite: Requires BW 7.4 SP 5 or higher. 2014 SAP AG. All rights reserved. 14
Recommendations / Findings for Integration Scenario B: Transactional data exploration via HANA Live enriched by BW master data Recommended to use SAP HANA Live reuse views To enable the consumption of SAP HANA views in the CompositeProvider, you have to attach the corresponding SAP HANA system to your BW project in the BW Modeling perspective in SAP HANA Studio Assign BW InfoObjects only for HANA view output fields if required (e.g. for hierarchy reporting, BW analysis authorizations, navigational attributes, time dependent master data) As a minimum you need to assign InfoObjects of type Unit (e.g. 0UNIT, 0CURRENCY) for unit and currency fields A static filter in the BEx Query must be added for SAP Client, e.g. fix value or mandatory variable Possible performance impact if query is restricted by hierarchy node value(s) as filtering in SAP HANA Live view will be pushed down based on single values BW Virtual Provider cannot be used as they cannot deal with HANA view output field names in lower cases If master data in BW needs to be provisioned in real-time consider: SLT and Real-time data acquisition into BW BW master data read access via HANA views Open ODS Views accessing HANA views 2014 SAP AG. All rights reserved. 15
Integration Scenario B Transactional data exploration via HANA Live enriched by BW master data Step 1 Create CompositeProvider a) In the BW Modeling perspective in SAP HANA Studio, in the context menu of your BW Project select the InfoArea and choose New -> CompositeProvider b) Specify an appropriate technical name & description and specify the default operation as Union 2014 SAP AG. All rights reserved. 16
Integration Scenario B Transactional data exploration via HANA Live enriched by BW master data Step 2 Assign HANA Live reuse view a) On the Scenario tab click Add InfoProvider in the Union definition b) Select SAP HANA View as search scope and search for the appropriate HANA Live reuse view (example: SalesOrderItem) c) The HANA Live reuse view is now added to your CompositeProvider and all output fields are listed on the graphical tab 2014 SAP AG. All rights reserved. 17
Integration Scenario B Transactional data exploration via HANA Live enriched by BW master data Step 3 Define Output structure of CompositeProvider a) Use the Graphical tab page on the Scenario tab to define the output structure of the CompositeProvider. Simply mark all fields required for the reporting scenario on the left hand side (all HANA View fields) and place them via drag and drop on the output structure on the right hand side. b) Field length of output fields is restricted to 12 characters. Cut output field names should be renamed (example reatedbyuser to CreatedBy ). 2014 SAP AG. All rights reserved. 18
Integration Scenario B Transactional data exploration via HANA Live enriched by BW master data Step 4 Add InfoObject Assignments where applicable In our example we assign in the Output tab of the CompositeProvider the following BW InfoObjects: - InfoObject 0MATERIAL for output field Material (needed for hierarchy display) - InfoObject 0SALESORG for output field Sales Organization (BW authorization relevant) - InfoObject 0CUSTOMER for output field SoldToParty (navigation attributes) - Unit InfoObjects 0UNIT and 0CURRENCY for QuantityUnit and for TransCurr Note: It is also possible to assign Open ODS Views instead of InfoObjects here. 2014 SAP AG. All rights reserved. 19
Integration Scenario B Transactional data exploration via HANA Live enriched by BW master data Step 5 Define Navigation Attributes where applicable a) If you want to add Navigation Attributes, ensure to mark the Direct Usage for Reporting checkbox in Association and right click on the output field b) You can select the Navigation Attributes by using the On/Off checkbox, rename the Description and choose the Representation and Filter Values settings 2014 SAP AG. All rights reserved. 20
Integration Scenario B Transactional data exploration via HANA Live enriched by BW master data Step 6 Activate CompositeProvider and create BEx Query Now you can activate the CompositeProvider and you can start implementing your BEx Queries 2014 SAP AG. All rights reserved. 21
Integration Scenario C: Combine transactional data from HANA Live view with BW DataStore Object data Consumption of SAP HANA Live views and BW DataStore Object by CompositeProvider in BW From BW From BW From SAP HANA Live 2014 SAP AG. All rights reserved. 22
Architecture for Integration Scenario C: Combine transactional data from HANA Live view with BW DataStore Object data Consumption of SAP HANA Live views and BW DataStore Object by CompositeProvider* in BW Capabilities (in addition to Scenario B) Supports integration of transactional data from SAP HANA Live view and SAP BW DataStore Object in CompositeProvider Real-time data provided via HANA Live view mixed with historical data provided by BW DataStore Object Actual data from HANA Live and plan data from BW SAP BW on HANA Master Data Master Data BW DSO Transactional Data BEx Query Composite Provider Transactional Data SAP BW Schema HANA Live Calculation View ( Reuse Layer) SAP HANA Schema(s) SAP HANA *Prerequisite: Requires BW 7.4 SP 5 or higher. 2014 SAP AG. All rights reserved. 23
Recommendations / Findings for Integration Scenario C: Combine transactional data from HANA Live view with BW DataStore Object data Recommended to use SAP HANA Live reuse views In order to enable the consumption of SAP HANA views in the CompositeProvider, you have to attach the corresponding SAP HANA system to your BW project in the BW Modeling perspective in SAP HANA Studio Before mapping an investigation is required if output fields of SAP HANA Live views and BW InfoObjects are sourced from the same table fields in SAP source system Key figure definition / calculation in SAP HANA Live view and BW DataStore Object may differ In some cases it might be necessary to implement a custom built reuse view / HANA calculation view to enhance standard SAP HANA Live views with missing output fields / functionality Use of constant values might be a helpful option to enrich missing fields in CompositeProvider definition (e.g. Version for plan vs. actual data) For the BW InfoProvider a unique constant value needs to be added in the CompositeProvider target definition for SAP Client A static filter in all BEx Queries on top of the CompositeProvider must be added for SAP Client e.g. fix value(s) or mandatory variable HANA Live view metrics and BW key figures may be combined in a BEx query using restricted & calculated key figures Possible performance impact if query is restricted based on hierarchy node value(s) as filtering in SAP HANA Live view will be pushed down based on single values 2014 SAP AG. All rights reserved. 24
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 1 Create CompositeProvider of type UNION Specify an appropriate technical name & description and specify the default operation as Union. 2014 SAP AG. All rights reserved. 25
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 2 Assign BW InfoProvider and HANA Live Reuse View In the Scenario tab page assign the BW DataStore Object and the SAP HANA Live View as part provider in the Union definition 2014 SAP AG. All rights reserved. 26
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 3 Define Target fields based on BW DataStore Object For the BW DataStore Object choose the InfoObjects that are common across both part providers and that you want to use for reporting. To define the output structure of the CompositeProvider simply drag and drop these InfoObjects into the target area. 2014 SAP AG. All rights reserved. 27
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 4 Map HANA view fields to BW InfoObjects in output structure Now map the corresponding SAP HANA Live view fields to the appropriate output fields that are already associated with BW InfoObjects in the target area of the CompositeProvider using drag and drop functionality. 2014 SAP AG. All rights reserved. 28
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 5 Add additional key figures from HANA Live view In our example additional SAP HANA Live key figures Open Amount and Open Quantity are added as real-time key figures into the target definition of the CompositeProvider. 2014 SAP AG. All rights reserved. 29
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 5 Add additional key figures from HANA Live view Remark: In case of combining plan data (BW) with actuals (HANA Live views): Add version information fields (e.g. 0VERSION, 0VTYPE) to the output fields of the CompositeProvider Fill with appropriate InfoObjects from the BW InfoProvider source (e.g. 0VERSION, 0VTYPE) Assign constant values for the SAP HANA Live view source (e.g. ACT for 0VERSION) Now the version information fields can be used in reporting for filtering and restricting key figures even though the SAP HANA Live view does not provide this information originally 2014 SAP AG. All rights reserved. 30
Integration Scenario C Combine transactional data from HANA Live view with BW DSO data Step 6 Enhance output definition a) Refine the output field properties, e.g. the Key-Figure-Specific Properties for the key figures added from HANA Live view. b) Now activate the CompositeProvider and you can start implementing your BEx Queries. 2014 SAP AG. All rights reserved. 31
Architecture for Integration Scenario D: Transactional and master data via HANA Live consumed by BW Consumption of SAP HANA Live transactional and master data views by Open ODS Views* in BW Capabilities (in addition to Scenario C) More flexible, agile modeling through Open ODS Views Real-time (transactional and master) data sourced via HANA Live views Optional: Historical data provided by BW DataStore Object can be flexibly added by using a CompositeProvider on top Note Future feature extension: Open ODS Views can be materialized if required Snapshot scenarios possible SAP BW on HANA Master Data Master Data BW DSO Transactional Data SAP BW Schema Composite Provider Open ODS View Transactional Data BEx Query Open ODS Open View ODS View Master Data HANA Live Calculation View ( Reuse Layer) SAP HANA Schema(s) SAP HANA *Prerequisite: Requires BW 7.4 SP 5 or higher. 2014 SAP AG. All rights reserved. 32
Recommendations / Findings for Integration Scenario D: Transactional and master data via HANA Live consumed by BW Recommended to use SAP HANA Live reuse views In order to enable the consumption of SAP HANA Live views in Open ODS Views, you have to attach the corresponding SAP HANA system to your BW project in the BW Modeling perspective in SAP HANA Studio Distinguish between transactional and master data (attribute and text) views and create associations accordingly Start with the Open ODS Views for SAP HANA Live master data views, then proceed with transactional Open ODS Views SAP Client needs to be added to the key of all Open ODS Views and needs to be uniquely filtered 2014 SAP AG. All rights reserved. 33
Integration Scenario D Transactional and master data via HANA Live consumed by BW Step 1 Create Open ODS View for Master Data a) In the context menu of your BW Project select the InfoArea and choose New -> Open ODS View b) Specify an appropriate technical name & description, define Semantic as Master Data and choose Source Type Database Table or View c) Define _SYS_BIC as DB Object Schema and Source System and select the SAP HANA Live view representing the master data (example: sap.hba.ecc/customerbasicdata) as DB Object Name 2014 SAP AG. All rights reserved. 34
Integration Scenario D Transactional and master data via HANA Live consumed by BW Step 2 Define key fields for Master Data Open ODS View As default all output fields of the SAP HANA Live view are assigned as Characteristics for the Open ODS View. It is mandatory to define the key fields: Representative Key Field Characteristics (Key): Additional compounded keys, like SAPCLIENT in case of SAP HANA Live Views 2014 SAP AG. All rights reserved. 35
Integration Scenario D Transactional and master data via HANA Live consumed by BW Step 3 Refine and activate Open ODS View for Master Data a) You can now further refine your Open ODS View e.g. by: Defining Text Fields as part of the view fields Changing the technical names for the view fields Adding field associations for view fields if applicable, e.g. with other Open ODS Views or BW InfoObjects Setting the view field as authorization relevant Changing the reporting properties such as key / text display b) When complete, you can activate the Open ODS View c) Define Open ODS Views for all Master Data views that you want to associate to your transactional Open ODS View 2014 SAP AG. All rights reserved. 36
Integration Scenario D Transactional and master data via HANA Live consumed by BW Step 4 Create Open ODS View for Transactional Data a) Now create an Open ODS View of type Facts for the transactional SAP HANA Live view similar like in the previous steps b) Characteristics and Key Figures will be automatically assigned to the appropriate structure folders based on the output field definition of the HANA Live view 2014 SAP AG. All rights reserved. 37
Integration Scenario D Transactional and master data via HANA Live consumed by BW Step 5 Maintain view fields and field associations for Open ODS View a) Define the key fields b) Define the currency and unit fields c) Maintain field associations e.g. to the previous created master data Open ODS Views 2014 SAP AG. All rights reserved. 38
Integration Scenario D Transactional and master data via HANA Live consumed by BW Step 6 Activate Open ODS View Now you can activate the Open ODS View and you can either reuse it in a CompositeProvider (e.g. combining the information with BW InfoProvider) or implement BEx Queries directly 2014 SAP AG. All rights reserved. 39
Other possible Scenarios Historic BW data virtually accessed via HANA View which combines HANA Live and BW data Loading of data into BW using Reuse Layer of HANA Live as ODP data source 2014 SAP AG. All rights reserved. 40
Architecture for Integration Scenario: Historic BW data virtually accessed via HANA View which combines HANA Live and BW data Consumption of BW InfoProvider in HANA Combined in calculation view with HANA Live reuse view data Custom built Calculation View combines data from HANA Live view and BW generated analytical/calc view To integrate historic BW data into HANA Live and consume the result via BI tools (e.g. Explorer) Generated Analytic View contains basic BW Metadata HANA Analytic Privileges based on BW analysis authorizations Additional Query Views (calculation views) needed to combine virtually accessed BW data and HANA Live data SAP BW on HANA BEx Query Composite Provider Master Data consumes BW DSO SAP BI Tools consume Calculation View generates BW Schema SAP BW Schema SAP HANA HANA Analytic/ Calculation View HANA Live Views SAP HANA Schema(s) SAP HANA 2014 SAP AG. All rights reserved. 41
Architecture for Integration Scenario: Extract data from HANA Live reuse views into BW Loading of data into BW using Reuse Layer of HANA Live Data Load into SAP BW utilizing SAP HANA Live views Reuse logic of HANA Live reuse layer as extraction logic for BW Strong alignment of data in BW and HANA Live reporting Only one logic to be supported and enhanced by SAP partners and customers SAP BW on HANA Master Data BW DSO Data Transfer Process ODP source system, context Hana Speed up extraction (vs. BW extractor logic) SAP HANA Live reuse views SAP BW Schema SAP HANA SAP HANA Schema(s) 2014 SAP AG. All rights reserved. 42
SAP HANA Live rapid-deployment solution Configuration guide on SAP HANA Live integration with SAP BW A detailed Configuration Guide H35 that describes possible scenarios for integration between SAP HANA Live and SAP BW: SAP BW and SAP HANA Live in the same HANA DB: 1. Consumption of SAP HANA Live views via ODP Transient Provider in SAP BW 2. Consumption of SAP HANA Live views and SAP BW Master data via Composite Provider in SAP BW 3. Consumption of SAP HANA Live views and SAP BW InfoProviders via Composite Provider in SAP BW 4. Consumption of SAP HANA Live views via Open ODS Views in SAP BW 5. Creating Views for BW Models in SAP HANA SAP BW and SAP HANA Live in two different DBs 1. Consume SAP HANA Models in SAP BW 2. Consume SAP BW Models in SAP HANA Link to this document in SMP: Configuration Guide H35 2014 SAP AG. All rights reserved. 43
Thank You! Matthias Kretschmer, SAP HANA Competence Center Andreas Tenholte, SAP HANA Analytical Content Team Jürgen Butsmann, Solution Management SAP HANA Thomas Fleckenstein, Product Owner SAP HANA Live
2014 SAP AG. 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. 2014 SAP. All rights reserved. 45