SAP BW On SAP HANA - Espresso Tutorials

SAP BW on SAP HANA Christian Savelli

TABLE OF CONTENTSTable of ContentsPreface9Acknowledgements1 Enterprise data warehouse on SAP BW10131.1SAP HANA as an in-memory database161.2SAP BW on SAP HANA181.3Benefits of running SAP BW on SAP HANA191.4Navigating this book212 An introduction to data modeling on EDW on SAP BW onSAP HANA232.1SAP HANA studio232.2SAP HANA native modeling262.3Summary343 Cross-consumption of data models on SAP BW on SAPHANA353.1Consuming SAP BW models in SAP HANA353.2Consuming SAP HANA models in SAP BW393.3SAP BW 7.4 composite providers413.4SAP BW open ODS views453.5Summary474 SAP BW backend optimized by SAP HANA494.1SAP BW administrator workbench optimized by SAPHANA514.2SAP BW optimized InfoCubes514.3SAP BW optimized datastore objects544.4SAP HANA optimized data staging554.5HANA analysis process (HAP)584.6Summary595

TABLE OF CONTENTS5 Data provisioning in SAP BW on SAP HANA5.1Data provisioning via extraction with persistence withinthe EDW database625.2SAP extractors635.3SAP Data Services715.4Flat file interface735.5SAP Landscape Transformation735.6Summary756 Enabling data virtualization in SAP BW on SAP HANA776.1Data virtualization and the SAP BW application776.2Open operational data store layer796.3Field-based data modeling836.4Association of open ODS view fields to SAP BW models856.5SAP HANA smart data access876.6Combining smart data access and open ODS views896.7Summary897 EDW modeling simplification enabled by SAP BW on SAPHANA917.1Evolving data warehouse modelling techniques917.2Layered scalable architecture (LSA)927.3Layered scalable architecture plus plus (LSA )947.4The LSA layer reduction flavor957.5The LSA modeling object simplification flavor977.6Advanced datastore objects (ADSO)997.7Enhanced composite providers1017.8Summary1038 Data lifecycle management of SAP BW on SAP HANA6611058.1Data temperature concept1058.2Data temperature concept applied to SAP BW1068.3Managing hot and warm data within an SAP BW on SAPHANA context108

TABLE OF CONTENTS8.4SAP HANA dynamic tiering1098.5Managing cold data within an SAP BW on SAP HANAcontext1118.6Managing frozen data within an SAP BW on SAP HANAcontext1158.7Data lifecycle management and Big Data1168.8Summary1189 Preparing an SAP BW application to run on SAP HANA1199.1Upgrade-migrate approach1199.2SAP BW adjustments prior to upgrading to an SAPHANA compatible version1219.3SAP BW HANA checklist1399.4Summary14010 SAP BW on SAP HANA post-migration tasks andoperations14110.1 Optimization of SAP BW cube layer14110.2 Enablement of Internet communication framework (ICF)services14310.3 Cleanup of obsolete process chain types14810.4 SAP HANA memory management14910.5 Summary15611 Final thoughts157A The Author160B Index161C Disclaimer1637

2 An introduction to data modeling onEDW on SAP BW on SAP HANAData modeling comes with a twist when running SAP BW on SAPHANA. As explained in Chapter 1, SAP HANA is not just an inmemory database but also a platform to build new applications. Thismeans data modeling is also available within SAP HANA itself. Having SAP BW on SAP HANA then entails two distinct modeling environments that can be easily integrated, allowing cross-modeling tosupport mixed scenarios. One environment is the SAP BW datawarehouse workbench, well known by SAP BW consultants. Theother modeling environment is SAP HANA studio.2.1SAP HANA studioSAP defines SAP HANA studio as an Eclipse-based development andadministration environment for working with SAP HANA. Eclipse itself isan integrated development environment (IDE) written mostly in Java thatoffers a base workspace extensible via plug-ins. SAP HANA studio isone of such plugins.Using lesser technical terms, SAP HANA studio is a client tool that allows one to connect to an SAP HANA database to perform typical database administrative tasks as well as to maintain SAP HANA artifacts,such as tables, views, and procedures. In addition, SAP HANA studioalso offers user and authorization management and SAP HANA extended application services (XS) for the development of applications basedon SAP HANA.23

AN INTRODUCTION TO DATA MODELING ON EDW ON SAP BW ON SAP HANAFigure 2.1: Launching SAP HANA studio, an Eclipse-based client tool fordevelopment and administration of SAP HANA databaseBecause it is an Eclipse-based IDE, SAP HANA studio can be openedlike any desktop application, as demonstrated in Figure 2.1. As with other Eclipse-based environments, SAP HANA studio offers several perspectives. A perspective is a collection of screen elements that are selected and customized for visualization according to the interaction desired with SAP HANA database. In a nutshell, a perspective is a predefined view of SAP HANA studio. A partial list of the perspectives can beseen in Figure 2.2.24

AN INTRODUCTION TO DATA MODELING ON EDW ON SAP BW ON SAP HANAFigure 2.2: Perspectives are predefined views within SAP HANA studioTwo perspectives are of interest when discussing data modeling withinan SAP BW on SAP HANA context: SAP HANA modeler perspective andBW modeling perspective. The next sections of this chapters dive intothese two perspectives specifically.BW modeling perspective requirementsThe BW modeling perspective is only available for SAPBW 7.4 SP5 and higher. As per SAP documentation,other requirements for the availability of the BW modeling perspective within SAP HANA studio include: Windows OS 7 on local PCJava Runtime Environment (JRE) 1.6 or higherInternet Explorer 7.0 or higher or Firefox 4.0 or higherSAP GUI for Windows 7.20, patch level 9 or higherSAP HANA studio (32-bit or 64-bit for Windows) SP08 or higheron local PC25

AN INTRODUCTION TO DATA MODELING ON EDW ON SAP BW ON SAP HANA2.2SAP HANA native modelingSAP HANA native modeling relates to the activities associated with creating views on top of database tables to depict desired business scenarios or address reporting requirements. Figure 2.3 demonstrates SAPHANA studio’s modeler perspective and how a user would view his orher home screen. Notice the list of views that can be created. Theseviews are information views in SAP HANA and can be created, changed,and deleted via the SAP HANA modeler perspective.Figure 2.3: SAP HANA modeler perspectiveInformation views are therefore logical, non-materialized structures acting as a semantic layer over the SAP HANA index server, allowing reporting tools to access data stored within SAP HANA tables.SAP HANA tables are organized by schemas under the catalog folder.Schemas are groups of tables, database views, and procedures of adatabase. Schemas can be seen as the blueprints of the database andare commonly used to restrict access to certain database content. Theassociation of users to schemas results into proper segregation of access to content groups.26

AN INTRODUCTION TO DATA MODELING ON EDW ON SAP BW ON SAP HANAInformation views are organized by packages under the content folder.They organize data as per business needs and do not follow technicallydefined schemas. An information view, for example, could be createdassociating tables from sales and finance schemas to address reportingneeds of a sales department. An information view like this would probably be stored under a package with a suggestive name such as “Order toCash Analysis” package.In a nutshell, SAP HANA tables are organized by schemas under thecatalog folder representing the technical view of the database. Information views are organized by packages under the content folder representing the business view of the database contents. Figure 2.4 demonstrates the file structure within SAP HANA studio.Figure 2.4: SAP HANA studio catalog and content foldersThe catalog, therefore, is the usual workspace for SAP HANA developers. A dedicated SAP HANA perspective named SAP HANA development is available for such users. The focus for SAP HANA modelers onthe other hand is centered on the content folder. It is under this folderthat information views can be maintained to slice, filter, and join SAPHANA tables to address specific business requirements. Three types ofinformation views can be created within the content folder: attributeviews, analytical views, and calculation views.2.2.1 Attribute viewsAttribute views are used to represent an entity relationship model at theattribute level. As an analogy, an attribute view could be seen as similarto an SAP BW master data model with a main entity combined with itsattributes and texts. An attribute view is a self-contained unit, a dimension that joins SAP HANA tables and can be reused on any other SAPHANA model or consumed directly by reports.27

INDEXB IndexCColumn storageData compression 17Indexation 17Sorting 17Surrogate keys 17Column views 35FFilter 27IInformation views 27Analytical views 28Attribute views 27Calculation views 32In-memory data platform 18JJoin 27NNative modeling 26PProcessing engines 17SSAP BW on SAP HANABenefits 19Data lifecycle management (DLM)105Big Data initiatives 116Data archiving process 115Data temperature concept 105Dymanic tiering 109Near-line storage (NLS) 111Data modelingAdvanced datastore objects(ADSO) 99Consuming SAP HANA models39Cross-consumption of datamodels 35EDW modeling simplification 91Enhanced Composite providers41Layered acalable architectureplus plus (LSA ) 94Layered scalable architecture(LSA) 92LSA layer reduction 96SAP BW open operational datastore (ODS) 45Data provisioning 45, 61BusinessObjects Data Services(BODS) 71Data Extraction 61Data persistency 61Data Replication 61Data virtualization 61Flat file interfaces 73Operational data provisioning(ODP) 63SAP extractors 63SAP Landscape Transformation(SLT) 73Data virtualizationData association 85Field based modeling 83161

INDEXOpen ODS view semantics 79Open operational data store layer79SAP BW OptimizedAdministrator workbench 51Analysis process 58Data staging 55Datastore objects 54InfoCubes 51SAP HANA studioPerspectives 24BW modeling perspective 25HANA modeler perspective 26Schemas 26Slice 27Smart Data Access (SDA) 87162TTables 26UUpgrade-migrateAdjustments to SAP BW 122Delta merge 151ICF services 143Checks and cleanup 148Master data maintenance 143Metadata repository viewer 145In-place migration 120Memory management 149New installation route 120Optimization of SAP BW cubelayer 141Parallel landscape 120

DISCLAIMERC DisclaimerThis publication contains references to the products of SAP SE.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarksor registered trademarks of SAP SE in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects,Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and otherBusiness Objects products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,and other Sybase products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks ofSybase, Inc. Sybase is an SAP company.SAP SE is neither the author nor the publisher of this publication and isnot responsible for its content. SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additional warranty.163

9.2 SAP BW adjustments prior to upgrading to an SAP HANA compatible version 121 9.3 SAP BW HANA checklist 139 9.4 Summary 140. 10 SAP BW on SAP HANA post-migration tasks and operations 141. 10.1 Optimization of SAP BW cube layer 141 10.2 Enablement of Internet communication framework (ICF) services 143 10.3 Cleanup of obsolete process chain types 148 10.4 SAP HANA memory management 149 10.5 .