Unit 03 – SAP BW on HANA Migration BW 7.30 Upgrade/System copy/Implementation

1. Unit 03 – SAP BW on HANA MigrationBW 7.30 Upgrade/System copy/Implementation RBWHDB

2. Objectives • At the end of this module, you will be able to: • Understand the basic Process for the mandantory Upgrade of BW to the lastest Version available (7.30) • Explain the main Options for transfering the existing NetWeaver BW system running on anyDB to the SAP HANA database. • fresh system installation • system migration (w/o transfer system) • comination of both options • Find additional ressources within SAP to understand the complete picture surrounded by the new created e2e Guide for BW on HANA migration

3. Business Example With BW 7.30 SP05 it is now possible to move an existing BW system from anyDB to the new In-Memory database HANA.Tom is a SAP basis administrator who has to set up and implement the new BW system into the landscape and provide the Pilot/PoC environment in his company. Therefore he needs to familiarize himself with the upgrade, systemcopy (homogeneous / heterogeneous) and basis tasks of the current SAP NetWeaver BW release 7.30.

4. Agenda – SAP BW on HANA Migration System preparation • Upgrade NetWeaver 7.30 - ABAP System migration • homogeneous systemcopy • heterogeneous systemcopy System finalizing • systemcopy - post work • implementing BI-JAVA 7.30 • conversion of DataStore Objects and InfoCubes Further resources • operations, sizing • LES session, CW, online training

5. Upgrade to BW 7.30 - ABAP • NetWeaver Java 7.30 is now shipped together with BW 7.30. Mandatory you should separate the Java Stack prior to the Upgrade of the ABAP Backend, if not already done. The new split/deinstallation tool for the Java Stack is expected to be available November 2011. If you are already in the process, consider the manual deinstallation of the Java Add-In until it’s availability. • The BICS are moving to the upcoming SAP BusinessObjects Application Platform BI 4.x, which is also a prerequisite for the full usage of the BEx successor - Analysis - • The Java component BW-IP modeler is redeveloped for BW 7.30 in ABAP HTTP, so the Java Server will not be used anymore for the BW-IP infrastructure in the future after BW 7.30 • The new BI Authorization concept is now mandantory. Despite the fact that you either create a 7.0x System beforehand to migrate the old BW Authorization, a potential Upgrade from BW 3.5 to 7.30 would be possible. • Note 1641432 - SAP Product Master Releases • Some technology facts and updates

6. Upgrade to BW 7.30 - ABAP • Note 1532805 - Add-On Compatibility of SAP NetWeaver 7.3 • There is a SEM Add-On available with BW 7.30. The SEM (6.34) Add-On is available since end of Q1/2011 for all Customers. See Notes 1539356 and 1531022 for more details.SEM 6.34 is HANA enabled, see Note 1648413 for more Details. • There is also the BPC 10.0 Add-On available with BW 7.30 which is currently in Rampup (GA expected for November 2011). With NetWeaver Version there is no Windows Server necessary anymore (web based maintenance). See Notes 1585589 and 1620027 for details. It is planned with SP06 (CPMBPC 800) to be HANA enabled • Add-On´s GRC or DMIS are not enabled for the Upgrade to NetWeaver 7.30 • Decision about installed Add-On´s

7. Upgrade to BW 7.30 – ABAP Choose your NetWeaver BW Start Release • SEM Add-On Implications BW 7.0/SEM 6.0 Upgrade to • NetWeaver 7.30 • SEM 6.34 • Not possible! BW 7.02/SEM 6.05 Upgrade to • NetWeaver 7.30 • SEM 6.34 • Not possible! BW 7.0/SEM 6.0 Upgrade to • NetWeaver 7.01 • SEM 6.04 • possible! BW 7.01/SEM 6.04 Upgrade to • NetWeaver 7.30 • SEM 6.34 • possible! Consider Notes 1531022 and 1539356 Additional option: Upgrade BW 7.02/SEM 6.05 to BSi2011/BW 7.31/SEM 7.36(Application Innovation merge with NetWeaver 7.02 and 7.31)

8. … (*) LCM Client ABAP 7.30 EP BICS BEx Web J2EE 7.01 J2EE 7.30 ABAP 7.01 ABAP 7.0 J2EE 7.0 EP (opt) BICS BEx Web BI Launch Pad New BI 4.0 Installation for SAP BW Customers SAP BW 7.01 SAP BW 7.0 SAP BW 7.30 • Platform View - Proposal Split BI Web Apps BI Web Tier BI Java BI Java EP XI Reporting & Infrastruc. Services EP EP BOE XI Web Tier BI Java Physical Server (optional) BO XI 3.1 SAP NetWeaver BI 4.x SAP NetWeaverFunctions Migr. SAP Usage Type and SAP BusinessObjectsTiers, Apps, Services BI Reporting & Infrastructure Services The XI 3.1/BI 4.0 Java apps can deployed either on an existing SAP J2EE 7.0x or 7.30 Engine, or ideally capsulated with BI with Tomcat. Consider the SAPJVM 4.1. A JVM switch toll is available as well

9. J2EE Options for BI 4.0 together with BW 7.30 BI 4.0 • use the recommendation with the BI 4.0 inbuilt Java Server SAP NetWeaver J2EE 7.30 Other J2EE (see PAM) BI 4.0 SP? Only BICS BEx Web BI 4.0 SP? Usage Type EP Usage Type BI Java(BICS, BEx Web) BI 4.0 BICS BEx Web Install Upgrade from BW 7.0x Install • BEx Web Limitations* • No Broadcasting (Portal/KM) • No Documents (Portal/KM) • No Xcelsius BW Connection • BEx Web Limitations* • No Broadcasting (Portal/KM) • No Documents (Portal/KM) • No Xcelsius BW Connection *Broadcasting is either a direct ABAP process (Excel) or an ABAP HTTP process publishing in a separate SAP EP Distinguish between 3.x and 7.x Web templates. 3.x Web template to not require BI - JAVA 7.x

10. Doublestack Options prior to the Upgrade BW 7.30 BW 7.0x Doublestack • separation of ABAP and JAVA easies the upgrade process Deinstall JAVA Add-In Use Split tool Deinstall JAVA 7.0x Stack Single ABAP 7.0x Stack Deinstall JAVA 7.0x Stack Fresh Install of JAVA 7.30 (without ADS) Upgrade to JAVA 7.30* Upgradeto BW 7.30 ABAP BW 7.30ABAP Stack NetWeaver 7.30JAVA Stack (with ADS) • JAVA 7.30 Upgrade limitation* • no automatic file system 7.x • no automatic SAPCryptoLib • disable SNC configuration ADS = Adobe Document Services (obsolete with NetWeaver 7.30 BI-Java)

11. SAP Business Intelligence Architecture 2011Choose the suitable combination

12. Accelerated Upgrade to NetWeaver BW 7.30Your single source for all pre and post upgrade steps Lower your TCO and time efforts by Managing your Upgrade with innovative tools • Complete Business Suite 7 connectivity (with EhP1): • abap - java connection (available) for connection BW-IP, EP, ESS/MSS, etc. • abap - abap (with EhP1) for backend connection e.g. ERP, CRM, BW, PI, etc. • java - java (upcoming) for frontend connection e.g. FPM, etc. • Note 1178800 2. CTC for BW-Java automatic connection between Abap and Java(Note 983156) 1. ASU toolbox (incl. BW Content) one single truth for all pre/post Upgrade Steps(Note 1000009) • Use the predefined content for: • upgrade to NetWeaver 7.x BW • upgrade to ERP 6.0 EhPx (upcoming) • upgrade to any SAP Product based on the NetWeaver 7.x Platform (upcoming) • create/modify own content (XML based) Check out the success story from the German Customer Karcher: http://service.sap.com/~sapidp/011000358700000162292010E/

13. Solution Manager pre requisitesincorrect stack.xml can create unwanted follow up errors • In order to successfully work with the Solution Manager to create necessary stack.xml, which is a new requirement in NetWeaver based upgrades the following checks had to be fullfilled prio to the cration of the stack.xml. • Suffient privelidges for the s-user, which is connected to the Service Market Place (SMP) • Updated PPMS data, to ensure the correct processing of the desired Upgrade Target‘s • Latest SP‘s/correction/Notes for the correct usage of the Solution Manager applications • For more information about the Maintenance Optimizer, see SAP Support Portal at • http://service.sap.com/solman-mopz

14. Post Activites after Upgrade to BW 7.30Additional Notes (so far): • Note 1610259 - Controlling 'Returncode' behavior in update rules • Note 1489064 - DataSource problems after BW upgrade from 7.0 to 7.3 • Note 1633303 - RSMDATASTATE inconsistencies after upgrade from 7.0x to 7.3x • Note 1632284 - Program RSCOMPCONS should generate warning messages • Note 1635588 - Problems with Start / End routine created at BW 7.0+ Release

15. Postwork after 7.30 upgrade - existing • Get everything which is needed here: • Managing your Upgrade with Innovative Toolshttp://www.sdn.sap.com/irj/sdn/edw-ops • The „upgradeBible“  frompage 52http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60ecc07d-3a4b-2b10-ef83-c988e6ecabf6 • Check the generic post upgrade steps from here

16. Agenda – SAP BW on HANA Migration System preparation • Upgrade NetWeaver 7.30 - ABAP System migration • homogeneous systemcopy • heterogeneous systemcopy System finalizing • systemcopy - post work • implementing BI-JAVA 7.30 • conversion of DataStore Objects and InfoCubes Further resources • operations, sizing • LES session, CW, online training

17. System Copy Use Casesconsidering the “Initial System Copy” case Initial System Copy Execution of post copy activities with Post Copy Automation SourceABAP-System PROD Export und Import of tables with Post Copy Automation SAP NetWeaver ABAP 7.0 or higher System copy with SAPInst / DB-Tools System Copy with SAPinst / DB-Tools Export TargetABAP-System Execution of post copy activities TST TST Import System Copy Refresh TargetABAP-System TST SourceABAP-System TST PROD SAP NetWeaver ABAP 7.0 or higher

18. Option1: Fresh Installation of BW on HANA  copy only parts of your existing productive system * Fresh Install “ORANGE” (7.30) UC enabled transport only parts of the system Note 1090842 - Composite note: Transport across several releases Note 454321 - Transports between Basis Release 6.* and 7.0 Note 1273566 - Transports between Basis Release 700/701 and >=702 Production BWP ORANGE Development Consolidation BWx BWD BWQ * BW Transport Transport BW 7.0/7.0x7.30 BW 7.30SP05+ ALE / RFC ALE / RFC ALE / RFC ALE / RFC Transport Transport ERP alternate PoC scenarioduring ramp-up! Development Consolidation Production R3D R3Q R3P

19. Option2: System Copy with BW on HANA  PoC System creation via Production copy (“safe side”) copy of Production (7.x) homogeneous systemcopy Upgrade NetWeaver 7.30 copy to “ORANGE” (7.30) heterogeneous systemcopy UC migration included ORANGE Production BWx BWC Production BWP BW Transport BW 3.57.0/7.0x7.30 BW 7.30SP05+ BW 7.30SP05+ add. preparation data cleansing ALE / RFC ALE / RFC Transport ERP Production R3P preferred PoC scenarioduring ramp-up!

20. Option3: System Copy with BW on HANA  new System direct creation when BW 7.30 SP5+ is live copy to “ORANGE” (7.30) heterogeneous systemcopy UC migration included Production BWP ORANGE Development Consolidation BWx BWD BWQ BW Transport Transport BW 7.30SP05+ BW 7.30SP05+ ALE / RFC ALE / RFC ALE / RFC ALE / RFC Transport Transport ERP Development Consolidation Production R3D R3Q R3P

21. distributed (ABAP/DB) heterogeneous systemcopy using existing App Servers UC migration included Go-Live: System Copy with BW on HANA complete BW Landscape transformation Development Consolidation Production BWD BWQ BWP Transport Transport BW Consolidation Production Development BHQ BHP BHD Transport Transport BW on HANA

22. Agenda – SAP BW on HANA Migration System preparation • Upgrade NetWeaver 7.30 - ABAP System migration • homogeneous systemcopy • heterogeneous systemcopy System finalizing • systemcopy – pre/post work • implementing BI-JAVA 7.30 • conversion of DataStore Objects and InfoCubes Further resources • operations, sizing • LES session, CW, online training

23. Checklist - prior to the import to SAP In-Memory DB • Check binaries for SAPInst, R3*, import/export tools • Run report RSUPGRSUM, if needed use „repair InfoObjects“ to repair Objects from RSD1 • Check DBACOCKPIT for missing indexes and run SAP_INFOCUBE_INDEXES_REPAIR • Check SE14 for unfinished table conversion • Run Report SAP_DROP_TMPTABLES and RSAN_UT_RESULT_DROP_RESULTS (interim) to delete all kind of BW specific temporary tables beforehand. • Clean/delete the messages for error logs (Note 1095924) • Check: RSB_ANALYZE_ERRORLOG • Clean: RSBM_ERRORLOG_DELETE • Check ODS objects in RSA1 for correct activation (RSDS_DATASOURCE_ACTIVATE_ALL) • Optionally: stop any deamon‘s and process chains with report RS_SYSTEM_SHUTDOWN before you stop all batch processes with BTCTRNS1 • Run Report SMIGR_CREATE_DDL before export (SP5 or higher version needed), check as well for the latest correction prior to it´s execution. • Choose target database „SAP In-Memory DB“, unicode and the target directory • Run option export from SAPInst from transfer system (export preparation/table splitting) • Choose target database „HDB“ (in-Memory DB) • Choose „little endian“ (for OS linux) and unicode option

24. Check for the biggest Tables before the export creationReport SMIGR_BIG_ROW_STORE_TABS (for row store tables) • <export>/ABAP/DB/HDB/rowstorelist.txtNote 1659383 - RowStore List for SAP Netweaver on SAP HANA Database

25. Check for the biggest Tables before the export creationTransactionDBACOCKPIT/DB02(for row/column store tables) • consider table splitting for export/import for the „top50“ largest tables • house keeping jobs, cleaning, reduction of data in the largest tables to consider prior to th export

26. BW system copy post steps • Crosscheck the availability of the following files prior to the import into HDB: • The DDLHDB.TPL file in <export>/ABAP/DB (Note 1639744) • The (correct) *.SQL files with report SMIGR_CREATE_DDL in <export>/ABAP/DB/HDB (Note 1600929) • The updated rowstorelist.txt in <export>/ABAP/DB/HDB (Note 1659383) • Run BTCTRNS1 to prevent the unwanted start of batch job’s • BDLS (check for corrections)  Test Run and Productive run • RSA1  source systems  BW system  restore • run in background • optional: check for RFC GTADIR_SERVER and Note 1586248  remove RFC connection • run RSAR_PSA_NEWDS_MAPPING_CHECK in advance • check the partner profiles in WE20 for the systems, and check IDoc ports in WE21 for the systems. • Report RS_BW_POST_MIGRATION (run in Background with Variant SAP&POSTMGRHDB) • RSSGPCLA  reset programs for ODS and DTP • Optional: Report RSUPGRCHECK (check for inactive objects overall) • Report RUTMSJOB  use the transaction above to solve inconsistencies • Run report RS_SYSTEM_SHUTDOWN to restart all process chains and deamon´s again

27. Report RS_BW_POST_MIGRATION detailed view of the steps (Variant SAP&POSTMGRHDB)

28. Report RS_BW_POST_MIGRATION run in Background with Variant SAP&POSTMGRHDB • The Report is intend to run directly in Background with the Variant for HDB,updated with Note 1657995 • However the reset of ODS Objects are still necessary (next page)

29. ODS/DTP migration after BW SystemcopyTransaction RSSGPCLA (not ORANGE related)

30. Optional: Run Report RSUPGRCHECK for Object concistency overall

31. BW system copy post In-Memory conversion steps for the visualization of the transaction RSMIGRHANADB you can add the following RSADMIN parameter ENBL_HDB_MIGR_DSO = X Run ONLY for selected Cubes and DSOs

32. HANA optimized InfoCube Design in BW HANA can work with “flat” structures and doesn’t need E- and F-fact tables! • Physical schema of BW InfoCube tailored towards traditional RDBMS MD MD MD MD D E Conversion / New F F Facts Facts D MD MD MD MD Benefits:Fast data loads (no DIMIDs)  up to 80% time reductionDimensions not physically present  simpler modeling and faster structural changesAll processes, all Queries and MultiProviders can remain unchanged

33. In-Memory Optimized DataStore ObjectsOverview and Design Change Log Active Data Delta calculation completely integrated in InMemDB– no data processing in ABAP Using in-memory optimized data structures for faster access No roundtrips to application server needed View View History Index(column based) Main Index(column based) Delta Index(column based) Activation triggered by BW, performed byInMemDB

34. Conversion Steps and Log Overview • Create temporary fact table with “flat” structure Z0<InfoCube> • Read data out of the original fact tables dissolving the starschema and save data in temporary fact table • Rename package dimension database table TP<InfoCube>Rename validity table (in case inventory mgmt InfoCube) TL<InfoCube> • Empty the InfoCube tables • Set InfoCube subtype to “flat” • Activate the InfoCube - As it is empty the structures and their DDIC description can be adjusted • Delete Fact DB-table and rename the temporary one • Delete PDIM and rename the temporary one • Delete validity table and rename the temporary one • Delete temporary DDIC objects • Create logical index(This can be done with transaction RSMIGRHANADB)

35. Agenda – SAP BW on HANA Migration System preparation • Upgrade NetWeaver 7.30 - ABAP System migration • homogeneous systemcopy • heterogeneous systemcopy System finalizing • systemcopy – pre/post work • implementing BI-JAVA 7.30 • conversion of DataStore Objects and InfoCubes Further resources • operations, sizing • LES session, CW, online training

36. detailed description in the e2e BW on HANA guidehttp://help.sap.com/nw73bwhana#section2

37. Notes to consider for sizing, tools, DBSL, etc. • Note 1600929 - SAP BW powered by SAP inMemory DB – Information • Note 1600066 - Available DBSL patches for NewDB • Note 1639744 - heterogenious systemcopy NetWeaver 7.30 to HANA target DB • Note 1657994 - SAP BW 7.30 powered by HANA - Special SP06 • Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database • Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database • Note 548016 - Conversion to Unicode • Note 551344 - Unicode Conversion Documentation • Note 1589175 - System Copy: Task Content for Task Manager • Note 1589145 - Task Manager for Technical Configuration • Installation/Operational Guides: http://help.sap.com/nw73bwhana

38. Main Landing Page – „one stop“ and e2e Guidehttp://www.sdn.sap.com/irj/sdn/edw-ops

39. Internal Collaboration Workspace – BW on HANAhttps://community.wdf.sap.corp/sbs/docs/DOC-94307

40. You should now be able to to understand the possible impacts regarding upgrade BW 7.30 to disdinguish between the different migration option to phrase the steps of the in-memory conversion and finally: If you don‘t unterstand any of these, you are capable to point into the right direction/resources for internal/external guidance on „BW on HANA – migration“ Summary