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

12 Pages·2017·1.21 MB·English

Implementation Guide CUSTOMER
Document Version: 1.5 – 2018-01-12
End-to-End Implementation Roadmap for SAP
NetWeaver AS ABAP
SAP NetWeaver AS ABAP 7.4, 7.5 or Higher
Content
1 About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.1 New Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
2.2 One-Step Upgrade and Migration with Database Migration Option (DMO) of Software Update
Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Downtime-Optimized DMO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Classical Upgrade and Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
3 How To Choose the Best Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
2 CUSTOMER Content
1 About This Document
This document describes the high-level end-to-end process to implement SAP NetWeaver Application Server
ABAP 7.4 or higher 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.
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
About This Document CUSTOMER 3
2 Options
You can newly install SAP NetWeaver Application Server ABAP 7.4 or higher on SAP HANA or you can migrate the
existing database to the new one.
To implement SAP NetWeaver Application Server ABAP 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 or higher 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.
Figure 1: Option 1: New Installation
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
4 CUSTOMER Options
Table 1:
Advantages Considerations
● No risk for production system with greenfield approach ● Greenfield approach unsuited to replace the current pro­
● Leveraged flexibility since you can move only parts of your duction system
scenarios ● Requires transfer (transport, migration, and load) of rele­
● Results in clean system with no outdated data vant 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 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. If you have special downtime requirements, you can benefit from minimized downtime
services – for more information, see SAP Note 693168 .
For more information about landscape transformation, see https://support.sap.com/saplt .
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. To
smooth the way to SAP HANA, it combines in one step all relevant steps for the in-place migration to SAP HANA:
Unicode conversion, system update, and database migration. In addition, it offers features to optimize downtime.
In contrast to other target releases, the DMO of SUM does not support the one-step upgrade and migration of non-
Unicode systems to SAP NetWeaver ABAP 7.5 or higher. Therefore, note the following:
● If you plan to migrate a non-Unicode system to SAP NetWeaver ABAP 7.5 or higher using DMO of SUM,
perform a standalone Unicode conversion beforehand, using the Software Provisioning Manager. For more
information about Unicode, see SAP Note 1322715 .
● If you plan to migrate a non-Unicode system to SAP NetWeaver ABAP 7.4x using DMO of SUM, you can either
perform a standalone Unicode conversion before the migration or you can plan to combine the Unicode
conversion with the DMO procedure. For more information on Unicode, see SAP Note 1322715 .
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
Options CUSTOMER 5
● If you plan to migrate a Unicode system to SAP NetWeaver ABAP 7.4x or higher, perform the DMO procedure.
For more information about DMO, see:
● SAP Community Network (SCN): Database Migration Option (DMO) of SUM - Introduction
● For the Database Migration Option of SUM, see the documentation and SAP Notes available at https://
support.sap.com/sltoolset System Maintenance Database Migration Option (DMO) with SUM 1.0
<Current SP> .
2.2.1 Downtime-Optimized DMO
If you have special downtime requirements, you can apply for a pilot registration of the downtime-optimized DMO.
This features integrated SAP Landscape Transformation technology to enable the migration of selected (large)
application tables during uptime processing of DMO, thereby reducing the downtime migration time.
After you apply to register a pilot project, SAP development decides whether you meet the conditions and whether
the project can be supported.
For more information and how to register, see: dmo-downtime-optimization-by-migrating-app-tables-during-
uptime-preview .
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 as a separate step. 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
Figure 2: Option 2: Database Migration
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
6 CUSTOMER Options
Table 2:
Advantages Considerations
● Clear separation of tasks – you can first perform an up­ ● No data and performance comparison possible between
grade project and then a migration project the former setup and the system powered by SAP HANA
● Apart from SAP HANA appliance, no additional hardware ● Typically requires extended downtime of production sys­
is required tem and several downtime windows (for example, one for
● Allows hardware replacement of application server a database upgrade - if SAP NetWeaver ABAP 7.4 or
higher 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) [page 5] 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.
Note
For SAP Business Warehouse, the available migration paths and considerations differ. Therefore, see the
corresponding guide End-to-End Implementation Roadmap – SAP BW, powered by SAP HANA, which is available
at https://help.sap.com/netweaver <Release> Integration .
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 and the AS Java system to
SAP HANA separately.
For more information, see 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 at
https://support.sap.com/sltoolset under System Provisioning Split Option of Software Provisioning
Manager .
2. Migration to SAP NetWeaver ABAP 7.5 or higher only: Unicode conversion (if required)
○ If you plan to migrate a non-Unicode system to SAP NetWeaver ABAP 7.5 or higher, perform a standalone
Unicode conversion using the Software Provisioning Manager. For more information on Unicode, see SAP
Note 1322715 .
Note
In contrast to other target releases, the Software Update Manager does not support the update or
upgrade of non-Unicode systems to SAP NetWeaver ABAP 7.5 or higher.
○ If you plan to migrate a non-Unicode system to SAP NetWeaver ABAP 7.4x, you can either perform a
Unicode conversion before the migration or you can plan to combine the Unicode conversion with the
heterogeneous system copy (step “Heterogeneous System Copy: Database Migration” below). For more
information on Unicode, see SAP Note 1322715 .
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
Options CUSTOMER 7
3. Upgrade / update:
Upgrade:
If your system has a lower release, upgrade it to the latest product supported by SAP HANA.
For more information, see the corresponding Upgrade Master Guide, such as the Upgrade Master Guide – SAP
NetWeaver 7.4 available at https://help.sap.com/netweaver <Release> Installation and 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 correct release but an Enhancement Package not
supported by SAP HANA, apply the required Enhancement Package.
For more information, see the update guide available at https://support.sap.com/sltoolset System
Maintenance Software Update Manager (SUM) 1.0 SPxx .
4. Heterogeneous System Copy: Database Migration
Perform the heterogeneous system copy as described in the SAP HANA System Copy Guide, which is available
at https://support.sap.com/sltoolset System Provisioning System Copy Option of Software
Provisioning Manager .
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
8 CUSTOMER Options
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?
● Do you expect significant downtime due to the large volume of your database?
All these aspects are reflected in the following matrix, which is intended as a starting point for your individual
assessment as outlined above:
Example
In 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
End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP
How To Choose the Best Option CUSTOMER 9
○ System is already Unicode
○ Running on Linux SUSE SLES 11/x86_64 and SAP MaxDB 7.8
○ Goal is to migrate this system to SAP NetWeaver 7.4 on SAP HANA
● Checking the matrix above:
○ Upgrade is required, in this example 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 ABAP
10 CUSTOMER How To Choose the Best Option