End-to-End Implementation Roadmap.pdf

Implementation Guide CUSTOMERDocument Version: 1.0 - May 28, 2014

End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPSAP NetWeaver 7.4 SP05

Table of Contents1 About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 New Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 One-Step Upgrade and Migration with Database Migration Option (DMO) of Software Update Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Classical Upgrade and Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

3 How To Choose the Best Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2C U S T O M E R 2014 SAP AG or an SAP affiliate company. All rights reserved.

End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPTable of Contents

1 About This DocumentThis document describes the high-level end-to-end process to implement SAP NetWeaver Application Server ABAP 7.4 based on SAP HANA.

Depending on your use case and your existing system landscape, you must consider different options, aspects, and required activities to bring your system to SAP HANA. This document provides an overview of these aspects and guidance on how to find the most suitable procedure for your requirements.

NoteFor SAP NetWeaver Business Warehouse, there is a separate guide available. See the End-to-End Implementation Roadmap SAP NetWeaver BW, powered by SAP HANA at http://help.sap.com/nw73bwhana.

For SAP NetWeaver Application Server Java systems, use the classical upgrade and migration procedure as outlined below.

End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPAbout This Document

C U S T O M E R 2014 SAP AG or an SAP affiliate company. All rights reserved. 3

http://help.sap.com/nw73bwhana

2 OptionsYou can newly install SAP NetWeaver Application Server ABAP 7.4 on SAP HANA or you can migrate the existing database to the new one.

To implement SAP NetWeaver Application Server ABAP 7.4 on SAP HANA, you have the following options:

You install a new system on SAP HANA: New Installation [page 4] You migrate an existing system to SAP HANA by performing one of the following procedures:

One-Step Upgrade and Migration with Database Migration Option (DMO) of Software Update Manager [page 5]

Classical Upgrade and Migration [page 6]

For more information, see Migration of SAP Systems to SAP HANA .

2.1 New Installation

You can install a new system based on SAP NetWeaver Application Server ABAP 7.4 in parallel to your existing system, either without changing your existing solutions (greenfield approach) or by transforming an existing solution to SAP HANA by performing (selective) data migration.


End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPOptions

http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-49743

Table 1:Advantages Considerations

No risk for production system with greenfield approach

Leveraged flexibility since you can move only parts of your scenarios

Results in clean system with no outdated data

Greenfield approach unsuited to replace the current production system

Requires transfer (transport, migration, and load) of relevant business data, if possible at all

No real data and performance comparison possible

Recommendation:

For systems with resident transactional data (such as SAP Business Suite), the greenfield approach is recommended for testing the overall SAP HANA approach and for gaining initial experience, but not for migrating or replacing your current production system.

If you face new or changed business requirements indicating that your existing solution landscape has to be changed in order to fulfill current objectives, consider performing a new installation to transform your system landscape. This lets you correct corresponding design issues of your SAP landscape, such as consolidating SAP systems or harmonizing data.

In addition, with the option to perform a selective migration, you gain more flexibility since you can migrate only specific data without business disruption. You can optionally combine this with data cleansing, leaving unused master data behind. This means you can smoothly introduce new business processes as part of your move to SAP HANA. To help you achieve this, SAP Landscape Transformation software reduces the effort to build a new targeted landscape such as via shell creation with carve-out options and system consolidation, complemented by corresponding transformation services such as Data Management Services or System Landscape Optimization consulting services.

For more information about landscape transformation, see http://service.sap.com/sapLT

For more information about services offered by SAP, contact [email protected] using the email subject HANA.

2.2 One-Step Upgrade and Migration with Database Migration Option (DMO) of Software Update Manager

The database migration option (DMO) of Software Update Manager (SUM) is the standard database migration. It combines in one step all relevant steps for the in-place migration to SAP HANA: Unicode conversion, upgrade, and migration.

To smooth the way to SAP HANA, SAP provides a one-step procedure that combines Unicode conversion, system update, and database migration for the migration to SAP HANA. This is provided with DMO, which is delivered with SUM in the Software Logistics Toolset (SL Toolset).

For more information, see:

SAP Community Network (SCN): Database Migration Option (DMO) of SUM - Introduction

SAP Note 1875197 for SAP Business Suite systems



http://help.sap.com/disclaimer?site=http://service.sap.com/sapLThttp://help.sap.com/disclaimer?site=http://scn.sap.com/community/it-management/alm/software-logistics/blog/2013/01/15/dmo-upgrade-and-migrate-sap-systems-to-sap-hanahttp://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1875197

SAP Note 1799545 for SAP NetWeaver Business Warehouse systems

SAP Note 1813548 for the Database Migration Option of SUM

With later versions, it is planned that DMO of SUM also provides features to optimize the downtime. If you have special downtime requirements, you can combine DMO with a Near Zero Downtime (NZDT) service for SAP Business Suite on SAP HANA.

2.3 Classical Upgrade and Migration

You can upgrade your existing system and then perform the database migration (or a combined operating system and database migration) with the classical migration procedure for databases. Optionally, you can combine the Unicode conversion into the upgrade or the migration procedure.

For more information, see the corresponding page in the SAP Community Network: Classical Migration to SAP

HANA

Table 2:Advantages Considerations

Clear separation of tasks you can first perform an upgrade project and then a migration project

Apart from SAP HANA appliance, no additional hardware is required

Allows hardware replacement of application server

No data and performance comparison possible between the former setup and the system powered by SAP HANA

Typically requires extended downtime of production system and several downtime windows (for example, one for a database upgrade - if SAP NetWeaver ABAP 7.4 does not support your current database release, one for the upgrade of the SAP system, and finally one for the database migration).

Recommendation:

If the standard Database Migration Option (DMO) of Software Update Manager (SUM) does not meet your requirements - for example, because your system is already on a release supported by SAP HANA, or because DMO of SUM is not available for your release, scenario, or platform, or because you prefer separate phases rather than the big-bang approach with DMO of SUM - consider using the classical migration with a heterogeneous system copy.



http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1799545http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1813548http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-49744http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-49744

It is done with the software provisioning manager, which is continuously being improved for this use case.

NoteFor SAP NetWeaver Business Warehouse, the available migration paths and considerations differ. Therefore, see the corresponding guide End-to-End Implementation Roadmap SAP NetWeaver BW, powered by SAP HANA, which is available in SAP Service Marketplace at http://help.sap.com/nw73bwhana.

When you migrate a system to SAP HANA with the classical approach, the following steps are required:

1. Dual-Stack Split (if required)SAP HANA does not support dual-stack systems (that is, systems running both AS ABAP and AS Java in one system with one SAP system ID and one startup framework). Before the upgrade, you must split existing dual-stacks or remove the AS Java. After the split, you can migrate the AS ABAP system to SAP HANA, while the Java system remains on its current database (until Java on SAP HANA is released).

For more information, see SAP Community Network: Dual-Stack Split and 1797362 (Dual-Stack Split for Systems Based on SAP NetWeaver).The dual-stack split procedure is performed by the software provisioning manager, which is available in SAP

Service Marketplace at http://service.sap.com/sltoolset under Software Logistics Toolset 1.0 System Provisioning .

2. Upgrade / update:Upgrade:If your system has a lower release, upgrade it to the latest product supported by SAP HANA.For example, you upgrade from SAP ECC 5.0 to SAP ECC 6.16 Enhancement Package 7. For more information, see the corresponding Upgrade Master Guide, such as the Upgrade Master Guide SAP

NetWeaver 7.4 available at http://service.sap.com/instguidesnw74 under Upgrade.With the application-specific upgrade toolbox (ASU toolbox, transaction /ASU/START), you can perform the application-specific and technical preparation and post-upgrade tasks. For more information, see SAP Note

1000009 (ASU Toolbox 2008).Update:If your SAP Business Suite system already has the right release but an Enhancement Package not supported by SAP HANA, apply the required Enhancement Package.For example, you update from SAP ECC 6.0 Enhancement Package 5 to SAP ECC 6.0 Enhancement Package 7. For more information, see the Update Guide of SAP Systems Using Software Update Manager 1.0 SP0x

available at http://service.sap.com/sltoolset under SL Toolset 1.0 Update of SAP Systems Using Software Update Manager (ABAP Systems) Update Guide - Update of SAP Systems Using Software Update Manager 1.0 SP0x .

3. Heterogeneous System Copy: Database MigrationPerform the heterogeneous system copy as described in the SAP HANA System Copy Guide that is available

in SAP Service Marketplace at http://service.sap.com/sltoolset under SL Toolset 1.0 DocumentationSystem Provisioning Copying Systems Based on NW 7.1 or Higher-SW Prov. Mgr. 1.0 Database of the target system: SAP HANA Database Select the version for your operating system .If you have a non-Unicode system, perform a Unicode conversion before the migration or plan a migration combined with a Unicode conversion.



http://help.sap.com/nw73bwhanahttp://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-25162http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1797362http://help.sap.com/disclaimer?site=http://service.sap.com/sltoolsethttp://help.sap.com/disclaimer?site=http://service.sap.com/instguidesnw74http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1000009http://help.sap.com/disclaimer?site=http://service.sap.com/sltoolsethttp://help.sap.com/disclaimer?site=http://service.sap.com/sltoolset

3 How To Choose the Best Option

The best option depends on your individual requirements and the boundary conditions you are facing, so take the recommendations above as a starting point for an individual assessment and decision, together with the cross-functional team involved in the planning of your migration project. To support you in this process, SAP provides the matrix shown below, which is intended to highlight important aspects for your decision on the right migration procedure, including these key considerations:

What is the release and Support Package level of your existing SAP system? Is an update mandatory or desired as part of the migration procedure?

Is your existing SAP system already Unicode? Do you plan any landscape changes - such as changing the SAPSID of your SAP system or the hardware of

your application server - as part of the migration or do you rather prefer an in-place migration? Do you plan the migration of your complete system or a partial migration? Are your operating system and your database versions supported according to the Product Availability Matrix

(PAM) of the target release or are corresponding updates required?

All these aspects are reflected in the following matrix, which is intended as a starting point for your individual assessment as outlined above:

ExampleIn this example, the matrix above is used to consider the best migration approach as follows:

Task:

Migration of an SAP NetWeaver ABAP 7.0x system System is already Unicode Running on Linux SUSE SLES 11/x86_64 and SAP MaxDB 7.8


End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPHow To Choose the Best Option

http://help.sap.com/disclaimer?site=http://service.sap.com/pamhttp://help.sap.com/disclaimer?site=http://service.sap.com/pam

Goal is to migrate this system to SAP NetWeaver 7.4 on SAP HANA Checking the matrix above:

Upgrade is required, from SAP NetWeaver 7.0x to 7.4. Unicode conversion is not required since the existing system is already Unicode. Landscape changes are not required or desired in this example. Based on the information from the Product Availability Matrix for SAP NetWeaver 7.4, SUSE SLES 11 is

supported, so no update of the operating system is required. Based on the information again from the Product Availability Matrix for SAP NetWeaver 7.4, only SAP

MaxDB 7.9 is supported, so the database has to be updated from SAP MaxDB 7.8 to 7.9. So the last row in the matrix above is valid for our use case.

Result (to be used as the starting point for an individual assessment as outlined above):

The usage of the DMO of SUM is highly recommended in this example, as this procedure does not require the interim update of the database with the classical migration procedure, this interim update would be mandatory, resulting in a total of three downtime windows (one for the database update, one for the SAP system upgrade, and one for the database migration).

Nevertheless, if for any reason the DMO of SUM does not fit (for example, because the upgrade is to be performed as a separate project before the actual migration), classical migration could be performed for this use case.

End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPHow To Choose the Best Option


www.sap.com/contactsap

2014 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 http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

http://www.sap.com/contactsaphttp://www.sap.com/corporate-en/legal/copyright/index.epxhttp://www.sap.com/corporate-en/legal/copyright/index.epx

End-to-End Implementation Roadmap for SAP NetWeaver AS ABAPTable of Contents1 About This Document2 Options2.1 New Installation2.2 One-Step Upgrade and Migration with Database Migration Option (DMO) of Software Update Manager2.3 Classical Upgrade and Migration

3 How To Choose the Best OptionCopyright and Trademarks

Documents

End-to-End Implementation Roadmap.pdf