How-To Migrate to BPC 10 on HANA Technical Considerations Applies to: SAP Business Planning and Consolidation 10, version for SAP NetWeaver, powered by SAP HANA Summary This guide covers technical aspects of migrating from SAP Business Planning and Consolidation 7.5, version for SAP NetWeaver to SAP Business Planning and Consolidation 10, version for SAP NetWeaver, powered by SAP HANA Author: Bruno Ranchy Company: Created on: 20 December 2012 Author Bio Bruno Ranchy has been working the SAP Customer Solution Adoption team (CSA, formerly RIG) since 2007 as a Senior Technical Specialist, with a primary focus on SAP Business Planning and Consolidation, SAP HANA, SAP BusinessObjects BI and Cloud environments. Before joining the CSA team, he was part of the IT team at OutlookSoft for over 7 years. 2012 SAP AG 1
Table of Contents Solution Overview... 3 Architecture and Topology of SAP Business Planning and Consolidation, version for SAP NetWeaver... 4 BPC 7.5 NetWeaver... 4 BPC 10 NetWeaver... 5 BPC 10 on HANA... 6 HANA Accelerator... 6 Comparison of architecture and requirements of the different versions... 7 Sizing... 7 Migration Strategy... 7 In-Place upgrade... 7 System copy and upgrade... 10 System Migration... 11 Security... 13 Impact on FIM... 13 Related Content... 14 Copyright... 15 2012 SAP AG 2
Solution Overview SAP Business Planning and Consolidation 10, version for SAP NetWeaver - Powered by SAP HANA is part of the Enterprise Performance Management suite and provides everything you need to meet your bottom-up and top-down financial and operational planning requirements, as well as a complete consolidation and reporting solution through a single application and user interface. It can be used for the Business Planning (Budgeting, Sales/revenue planning, Expense planning), Consolidations (Intercompany matching/reconciliation/ eliminations, legal consolidations), Forecasting and consensus building and Financial reporting and analysis. With In-memory technology offered by HANA, SAP Business Planning and Consolidation, version for SAP NetWeaver - Powered by SAP HANA can handle big volumes of data easily, supports real-time planning and analysis, enables cross functional detailed planning and shrinks decision cycle time. Key Benefits of SAP Business Planning and Consolidation, version for SAP NetWeaver - Powered by SAP HANA: Increased Agility Helps to plan better and act fast with instant insight into all relevant information. Boost Performance Accelerate planning and consolidation processing leveraging the power of inmemory technology. Engage Everyone - Simplify the input and exploration of data with a next generation mobile interface Note: for practical reasons, we will refer to SAP Business Planning and Consolidation 10, version for SAP NetWeaver, powered by SAP HANA as BPC 10 on HANA and SAP Business Planning and Consolidation 7.5, version for SAP NetWeaver as BPC 7.5 NetWeaver for the rest of this document. 2012 SAP AG 3
Architecture and Topology of SAP Business Planning and Consolidation, version for SAP NetWeaver Since the document is about migrating from version 7.5 to version 10, let s compare the different architectures and topologies: BPC 7.5 NetWeaver Requirements are: SAP NetWeaver ABAP 7.01, 7.02, 7.03 (7.31) or 7.3 Application Server Database: Any that the above versions of SAP NetWeaver support Operating System: for the database layer and SAP NetWeaver layer: any that are supported by the selected versions of SAP NetWeaver and the selected database engine. Web Server/.Net Application Server: Microsoft Windows Server 2003 or 2008 Please refer to the Product Availability Matrix for more details Note the presence of the Web Server and.net Application Server layer. While this layer can run on either 32-bit or 64-bit MS Windows servers, it uses Microsoft IIS in 32-bit architecture. This limits it to using a maximum of 4 GB of memory, regardless of the actual amount of physical RAM that might be available (above 4 GB) in the server. As a consequence, large installations with lots of concurrent users must use several Web/Application servers with Network Load Balancing. 2012 SAP AG 4
BPC 10 NetWeaver Requirements are: SAP NetWeaver ABAP 7.3 or 7.31 Unicode Application Server Database: Any that the above versions of SAP NetWeaver support Operating System: any that is supported by the selected versions of SAP NetWeaver and the selected database engine. Please refer to the Product Availability Matrix for more details 2012 SAP AG 5
BPC 10 on HANA Requirements are: SAP NetWeaver ABAP 7.3 SP06 (or above) Unicode Application Server. SAP NetWeaver 7.31 is not currently supported by BPC 10 on HANA but support is planned for the near future. Database: SAP HANA SPS3 Platform Edition or above Operating System: any that is supported by SAP NetWeaver 7.3 Please refer to the Product Availability Matrix for more details Note: SAP HANA typically runs as an appliance on certified hardware HANA Accelerator SAP HANA provides not only a new database engine for SAP NetWeaver, but also introduces a shift of the processing, from the Application layer toward the Database layer BPC 10 on HANA introduces an additional software component, HANABPC. This component is an accelerator for Planning and Consolidation and implements some BPC logic/functions which can be accelerated by SAP HANA. There is a correlation between Service Pack level for HANABPC and Service Packs for BPC 10 on HANA (CPMBPC Component) CPMBPC 800 BPCHANA 800 SP06 SP07 SP08 SP00 SP01 SP02 2012 SAP AG 6
This software component currently requires SAP NetWeaver 7.3 SP06 or above and BPC 10 SP06 or above. Support for NetWeaver 7.31 and 7.4 is planned for future release Comparison of architecture and requirements of the different versions An obvious difference between version 7.5 and 10 is the evolution of the web server component. BPC 7.5 NW uses Microsoft ISS while BPC 10 NW and BPC 10 on HANA use the web server that is part of SAP NetWeaver. The latter is more scalable than IIS in 32-bit mode, and greatly simplifies the topology of the system (no more separate web server and Network Load Balancing, that were typical of BPC 7.5 implementations.) A less visible difference is the required version of SAP NetWeaver. BPC 7.5 NW supports SAP NetWeaver 7.01 and 7.02, but BPC 10 NW and BPC 10 on HANA don t support those versions. However the requirements for SAP NetWeaver 7.01 and 7.02 are quite different than those for SAP NetWeaver 7.3. This means that many BPC 7.5 NW systems might be running on older versions of Operating Systems and relational databases that are not supported by NetWeaver 7.3. Examples include Microsoft Windows Server 2003, Microsoft SQL Server 2005, HP UX 11.11, IBM DB2 9.1, etc Please refer to the Product Availability Matrix for more details Sizing Sizing a BPC 10 on HANA system is a two-step process, and should be done with assistance from SAP Technical Services: Sizing the associated BW on HANA system using the SAP Quicksizer (http://wervice.sap.com/quicksizer). Sizing BPC 10. A sizing guide can be found at http://service.sap.com/sizing Please consult notes 1736976 and 1637145 for details on using Quicksizer for BW on HANA and related activities A sizing guide dedicated to BPC on HANA should be coming soon. Migration Strategy There are several possible strategies that need to be considered: In-Place upgrade System Copy of the source system, and then in-place upgrade on the copy Fresh installation of a BPC 10 on HANA system, and migration of the BPC content from the BPC 7.5 system Each solution has pros and cons, and their respective appeal will vary depending on the existing environments and on corporate strategy. In most cases the third option (fresh installation) will be the most sensible approach. In-Place upgrade In this case, all components are upgraded to meet the requirements of BPC 10 on HANA, directly on the existing server. While this can seem attractive as the hardware is reused, it is also a potentially disruptive option as it means that the BPC system will be unavailable during the upgrade. 2012 SAP AG 7
Typical progression of an in-place upgrade from BPC 7.5 NW to BPC 10 on HANA 1. The platform software is updated to meet the requirements of SAP NetWeaver 7.30 2. NetWeaver is upgraded to 7.30 3. The BPC 10 ABAP add-in is installed, replacing the BPC 7.5 ABAP add-in 4. The database is migrated to SAP HANA 5. The HANABPC Accelerator ABAP add-in is installed The scope of such upgrade will depend a lot on the versions of required software running on the existing BPC 7.5 NW server. For example, if BPC 7.5 NW is installed on NetWeaver 7.01 running on MS SQL Server 2005 on Windows Server 2003, then upgrading to BPC 10 on HANA would require (for example) the following steps: 1. Upgrading MS Windows Server 2003 to Windows Server 2008 2. Upgrading MS SQL Server 2005 to MS SQL Server 2008 3. Upgrading SAP NetWeaver 7.01 to SAP NetWeaver 7.30 SP06 4. Upgrading BPC 7.5 NW to BPC 10 NW 5. Migrating the database from MS SQL Server 2008 to SAP HANA 1.0 SP03 6. Installing the BPC 10 HANA Component in SAP NetWeaver (HANABPC) In a typical landscape comprised of a development system (DEV), a test system (QA) and a production system (PROD), it is a advisable to star the upgrade with the DEV system, and assess the result before continuing with upgrading the other systems Pros: lower cost of hardware Maintains customizations in BW that might not be related to BPC but nevertheless might be necessary for other usage. Cons: Somewhat risky, as it alters the original BPC 7.5 NW system Disruptive. The BPC 7.5 NW system is no longer available from the moment the upgrade is started Not currently possible if the BPC 7.5 NW system is built on NetWeaver 7.31 as BPC 10 on HANA currently supports only NetWeaver 7.30. Can potentially carry over some problems from the old system Can turn into a rather complex upgrade if the BPC 7.5 NW system is built on a platform (Operating System or database server) that is not supported by NetWeaver 7.30 2012 SAP AG 8
Breaks the bug-fix path. Once the DEV server has been upgraded, there is no more system on which to test changes to the BPC 7.5 NW systems, which is still the version that is in use for Production. The migration of the database to SAP HANA is covered in the following documents: SAP NetWeaver BW, powered by SAP HANA - End-to-End Implementation Roadmap Technical considerations when migrating an existing NetWeaver BW system to run on SAP HANA New Tools to ease Migration to SAP NetWeaver BW on SAP HANA 2012 SAP AG 9
System copy and upgrade In this case a system copy of the BPC 7.5 NW NetWeaver system is done first, and the upgrade takes place on the copy. First Step: System Copy Second step: In-Place Upgrade on the copy This option alleviates the risk and disruption of the in-place upgrade, while keeping most of the benefits of the in-place upgrade. It has, however, additional cost as extra hardware is needed. 2012 SAP AG 10
System Migration The BPC 10 on HANA system is built as a new system, and then BPC data is migrated from the BPC 7.5 NW system to the BPC 10 on HANA system. A new system is built directly on an SAP HANA database The BPC 7.5 NW Appsets are backed up using UJBR and then restored (also with UJBR) in the new BPC 10 on HANA system, where they are called Environments. 2012 SAP AG 11
Pros: It is a straightforward, standard installation There is no dependencies on outdated Operating System and database software as the system can be provisioned directly with versions that are supported by BPC 10 on HANA and NetWeaver 7.3 There is no impact on the BPC 7.5 systems. This is a fresh installation. It is not carrying over possible problems from an older system. Cons: This is a fresh installation. It will not contain prior customizations of BW. There is the cost of provisioning new hardware. Subsequent steps Once the system has been upgraded or migrated to BPC 10 on HANA, the BPC environment (appset) needs to be migrated to the BPC 10 format and then optimized for BPC 10 on HANA. Those steps are outside of the scope of this guide but are covered in the following guide on SDN: How To Migrate to BPC 10 on HANA (http:///docs/doc-33863) 2012 SAP AG 12
Security Security is handled differently between BPC 7.5 NW and BPC 10 on HANA In BPC 7.5, the authentication was handled by the.net tier, and was using either Active Directory or CMS accounts In contrast, BPC 10 on HANA uses SAP ABAP accounts. In both cases, user rights, team, profiles are still managed within BPC As a consequence, the user accounts will need to be created in SAP NetWeaver, either manually or through an import. Impact on FIM The implementation of Financial Information Management with BPC is outside of the scope of this document, however there are some aspects that need to be considered if FIM is used with the BPC system being upgraded Financial Information Management is a tool that allows transfer of data between several products, such as BPC, PCM (SAP Profitability and Cost Management) and several others. It uses CMS security, which is part of SAP BusinessObject BI. FIM 7.5 is compatible with BPC 7.5 and FIM 10 is compatible with BPC 10. In BPC 7.5 NW, using FIM with BPC requires BPC to be using CMS authentication, rather than Active Directory authentication. With BPC 10 on HANA however, there is no possibility of CMS authentication. In this case the topology is a bit different. Rather than BPC delegating its authentication to CMS, it is CMS that uses SAP ABAP authentication. This change in authentication mode means that the configuration of CMS will need to be modified, and the impact on other products using that same CMS server needs to be evaluated 2012 SAP AG 13
Related Content How To Migrate to BPC 10 on HANA Technical considerations when migrating an existing NetWeaver BW system to run on SAP HANA New Tools to ease Migration to SAP NetWeaver BW on SAP HANA 2012 SAP AG 14
Copyright Copyright 2012 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. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Oracle Corporation. JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. 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. 2012 SAP AG 15