of SAP BW to SAP HANA: Software and Delivery …sapidp/012002523100002085562015E/RDS...of SAP BW to...

SAP HANA

April 2015

English

Rapid database migration of SAP BW to SAP HANA: Software and Delivery Requirements

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Rapid Deployment Solutions Software and Delivery Requirements

© SAP SE Public Page 2 of 12

Copyright

© 2015 SAP SE 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example

text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example

text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Table of Contents Contents

1 Purpose of the Document .............................................................................................................. 5

2 General Project Prerequisites ....................................................................................................... 5

3 Scenario Overview ........................................................................................................................ 5

4 Technical Requirements ................................................................................................................ 6

4.1 Software Product Versions.................................................................................................. 6

4.1.1 Scenario 1a / Scenario 3a (for SAP Cloud only) ............................................................ 6

4.1.1.1 Start Release before Migration ................................................................................... 6

4.1.1.2 Migration Tools ........................................................................................................... 6

4.1.1.3 Target Release after Migration ................................................................................... 7

4.1.2 Scenario 1b / Scenario 3b (for SAP Cloud only) ............................................................ 7


4.1.2.2 Migration Tools ........................................................................................................... 8


4.1.1 Scenario 2a ..................................................................................................................... 9


4.1.1.2 Migration Tools ........................................................................................................... 9


4.1.2 Scenario 2b ................................................................................................................... 10

4.1.2.1 Start Release before Migration ................................................................................. 10

4.1.2.2 Migration Tools ......................................................................................................... 10

4.1.2.3 Target Release after Migration ................................................................................. 10

4.2 Supported Database Releases ......................................................................................... 11

4.3 SAP Notes ......................................................................................................................... 11

4.4 SAP Solution Manager and SAP Solution Manager Content Add-On .............................. 11



1 Purpose of the Document This document contains all information to:

Validate that key prerequisites such as software products and versions match the customer situation

Check that all prerequisites for a customer implementation are in place

Check that correct content, tools and skills are in place before the project starts

The document lists different kinds of requirements on package level if they are valid for all scope items included in the package. For requirements valid for certain scope items only, these scope items are mentioned.

The document contains pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the configuration guides.

2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start.

Prerequisite Responsibility

Kick off and workshop dates, location and attendees agreed Customer

Customer team allocated with correct skills and training in place Customer

Project sponsors and stakeholder identified Customer

Hardware fully commissioned Customer

Software licenses in place Customer

Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports

Customer

User interfaces agreed e.g. SAPGUI, Netweaver Business Client or Portal

Customer

Remote access is in place for SAP consultants and SAP Active Global Support

Customer

Decision made whether pre-assembled delivery will be used Customer

Decision made whether SAP Best Practices Solution Builder will be used to activate content.

Customer

Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates.

Customer

Tool for project repository and collaboration agreed Customer

Test management tool agreed Customer

3 Scenario Overview The database migration of this rapid-deployment solution offers the following scenarios:

Scenario 1: Upgrade and Database Migration using DMO for SUM



o Scenario 1a: Upgrade and DB Migration using DMO for SUM (One-System Approach)

o Scenario 1b: Upgrade and DB Migration using DMO for SUM (Two-Parallel-Systems Approach) and PCA

Scenario 2: Database Migration using SWPM

o Scenario 2a: DB Migration using SWPM (One-System Approach)

o Scenario 2b: DB Migration using SWPM (Two-Parallel-Systems Approach) and PCA

For SAP only: a third scenario (Scenario 3) is available for a SAP Cloud deployment.

Scenario 3: Upgrade and Database Migration using DMO to SAP Cloud for SUM

o Scenario 3a: Upgrade and DB Migration using DMO to SAP Cloud for SUM (One-System Approach)

o Scenario 3b: Upgrade and DB Migration using DMO to SAP Cloud for SUM (Two-Parallel-Systems Approach) and PCA

4 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided.

4.1 Software Product Versions The following software products and versions are required:

4.1.1 Scenario 1a / Scenario 3a (for SAP Cloud only)

4.1.1.1 Start Release before Migration

Product Product Version

Components SAP Solution Manager Logical Component

Comments Relevance

SAP NetWeaver 7.00

SAP NetWeaver 7.00 SP19 minimum

4.1.1.2 Migration Tools



Comments Relevance

SAP Solution

SAP Solution Manager

For creation of stack XML



Manager 7.0 EHP1 SP23 minimum

or

SAP Solution Manager 7.1 SP01 minimum

SL Toolset Software Logistics Toolset 1.0 SPS12 minimum

Software Update Manager 1.0

Update and DB Migration with DMO for SUM

4.1.1.3 Target Release after Migration



Comments Relevance

SAP NetWeaver 7.40


SAP HANA Platform Edition

SAP HANA Platform Edition 1.0 SPS09 minimum

SAP HANA Studio 2.0

SAP HANA Client 1.0

SAP Host Agent 7.20

4.1.2 Scenario 1b / Scenario 3b (for SAP Cloud only)




Comments Relevance

SAP NetWeaver 7.40


SAP NetWeaver 7.31

SAP NetWeaver 7.31 SP04



minimum

SAP NetWeaver 7.30


SAP NetWeaver 7.11


SAP NetWeaver 7.02


SAP NetWeaver 7.01


SAP NetWeaver 7.00





Comments Relevance

SAP Solution Manager

SAP Solution Manager 7.0 EHP1 SP23 minimum

or

SAP Solution Manager 7.1 SP01 minimum

For creation of stack XML


Software Update Manager 1.0

Update and DB Migration with DMO for SUM

SAP NetWeaver Landscape Virtualization Management, Enterprise

SAP NetWeaver Landscape Virtualization Management 2.0 SP08

PCAI 1.1 ABAP Post Copy Automation (PCA) SAP Business Warehouse



Edition minimum




Comments Relevance

SAP NetWeaver 7.40




SAP HANA Studio 2.0

SAP HANA Client 1.0

SAP Host Agent 7.20

4.1.1 Scenario 2a




Comments Relevance

SAP NetWeaver 7.30





Comments Relevance


Software Provisioning Manager 1.0

DB Migration




Comments Relevance

SAP NetWeaver 7.30

SAP NetWeaver 7.30 SP08

Same as Release before



minimum Migration



SAP HANA Studio 2.0

SAP HANA Client 1.0

SAP Host Agent 7.20

4.1.2 Scenario 2b




Comments Relevance

SAP NetWeaver 7.30





Comments Relevance


Software Provisioning Manager 1.0

DB Migration

SAP NetWeaver Landscape Virtualization Management, Enterprise Edition

SAP NetWeaver Landscape Virtualization Management 2.0 SP08 minimum

PCAI 1.1 ABAP Post Copy Automation (PCA) SAP Business Warehouse




Comments Relevance

SAP NetWeaver 7.30


Same as Release before Migration

SAP HANA SAP SAP HANA



Platform Edition

HANA Platform Edition 1.0 SPS09 minimum

Studio 2.0

SAP HANA Client 1.0

SAP Host Agent 7.20

4.2 Supported Database Releases There are several database platforms, which are supported as source databases for the migration.

Check SAP Note 1600929 SAP BW powered by SAP HANA DB: Information for updates on these restrictions.

4.3 SAP Notes Please check the Quick Guide for the latest SAP Notes.

4.4 SAP Solution Manager and SAP Solution Manager Content Add-On

For the implementation of the solution package, SAP Solution Manager is recommended.

Product Product Version Comments

SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1

SP18 or higher

Or

SAP Solution Manager 7.1

SP01 or higher

Or

SAP Solution Manager 7.1 on HANA (ST 712)

SP00 or higher

If using SAP Solution Manager 7.0 with SP below 24, see SAP Note 1579267.

For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates.

The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc.

For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note 1726649 and SAP Note 1686668 respectively.

In the ST-RDS 100 content add-on, access the template in the following way:

If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below.

If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below.

Template ID RDS_RDBMS_HANA10V4- Rapid database migration of SAP BW to SAP

https://service.sap.com/sap/support/notes/1600929

http://service.sap.com/sap/support/notes/1579267





and Template Name

HANA_V4

Solution Package Name(s)

Rapid database migration of SAP BW to SAP HANA_V4

Date post:	12-Mar-2018
Category:	Documents
Upload:	hakhue
View:	227 times
Download:	4 times

of SAP BW to SAP HANA: Software and Delivery …sapidp/012002523100002085562015E/RDS...of SAP BW to...

Documents