SAP Best Practices for system conversion for SAP S/4HANA ...sapidp/012002523100003217232016E/BP_BSCON...Business Process Alternative/Decision Choice Typographic Conventions Type Style

SAP S/4HANA

May 2016

English

SAP Best Practices for system conversion for SAP S/4HANA V1.10: 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

© 2016 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

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 1 ....................................................................................................................... 6

4.1.1.1 Start Release before Conversion ............................................................................... 6

4.1.1.2 Conversion Tools ........................................................................................................ 7

4.1.1.3 Target Release after Conversion ............................................................................... 7

4.1.2 Scenario 2 ....................................................................................................................... 8


4.1.2.2 Conversion Tools ........................................................................................................ 8

4.1.2.3 Target Release after Conversion ............................................................................... 9

4.1.3 Scenario 3 ....................................................................................................................... 9


4.1.3.2 Conversion Tools ...................................................................................................... 10

4.1.3.3 Target Release after Conversion ............................................................................. 10

4.2 Further Requirements ....................................................................................................... 11

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



1 Purpose of the Document This document contains 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 system conversion to SAP S/4HANA of this best practice solution offers the following scenarios:

Scenario 1: Conversion of SAP ERP on anyDB to S/4HANA Enterprise Management

Scenario 2: Conversion of SAP ERP on SAP HANA to S/4HANA Enterprise Management



Scenario 3: Conversion of SAP ERP with SAP S/4HANA Finance on SAP HANA to SAP S/4HANA Enterprise Management

Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note for updated information.

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 1

4.1.1.1 Start Release before Conversion

Product Product Version

Components SAP Solution Manager Logical Component

Comments Relevance

SAP ERP ERP 6.0 minimum

ABAP only. System needs

to be on Unicode. Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note for updates.

Mandatory

SAP NetWeaver 7.5

SAP NetWeaver 7.5

Required for analyzing of

the custom code. For more information see SAP Note 2241080 Custom code check content for SAP S/4HANA on-premise edition.

Optional

SAP NetWeaver 7.5

SAP NetWeaver 7.5 - Frontend

SAP Business Client 6.0 minimum

Check SAP Note 2227396 SAP Business Client 6.0: Prerequisites and restrictions.

Mandatory in case no SAP Fiori coverage in the Target Release after Conversion

https://launchpad.support.sap.com/#/notes/2189824






4.1.1.2 Conversion Tools



Comments Relevance

SAP Solution Manager

Solution Manager Release 7.1 SP05 minimum

For connection to For connection to SAP Service Marketplace

Mandatory

SAP Maintenance Planner

Please check Maintenance Planner User Guide for more information.

Mandatory

SL Toolset SL Toolset 1.0 SPS16 minimum

Software Update Manager 1.0

Conversion with DMO for SUM. Please see Software Logistic Toolset 1.0 on SAP Service Marketplace for details.

Mandatory

4.1.1.3 Target Release after Conversion



Comments Relevance

SAP S/4HANA

SAP S/4HANA ON-PREMISE 1511 FPS01 minimum

Mandatory

SAP HANA Platform Edition

SAP HANA Platform Edition 1.0 SPS11 minimum

Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note for the SAP HANA revision.

Mandatory

http://wiki.scn.sap.com/wiki/download/attachments/187337812/Maintenance_Planner_User_Guide.pdf


https://help.sap.com/sltoolset





4.1.2 Scenario 2



Components

SAP Solution Manager Logical Component

Comments Relevance

SAP ERP EHP7 for SAP ERP 6.0 minimum

ABAP only

Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note for updates.

Mandatory

SAP NetWeaver 7.5

SAP NetWeaver 7.5


the Custom Code. For more information see SAP Note 2241080 Custom code check content for SAP S/4HANA on-premise edition.

Optional

SAP NetWeaver 7.5







Components


Comments Relevance



For connection to SAP Service Marketplace

Mandatory



Mandatory



Upgrade with SUM. Please see Software Logistic Toolset 1.0 on SAP

Mandatory










Service Marketplace for details.




Comments Relevance

SAP S/4HANA


Mandatory

SAP HANA Platform Edition

SAP HANA Platform Edition 1.0 SPS11 minimum

Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note for the SAP HANA revision.

Mandatory

4.1.3 Scenario 3



Components


Comments Relevance

SAP ERP EHP7 for SAP ERP 6.0 minimum

ABAP only

Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note for updates.

Mandatory

SAP SFINANCIALS

SAP SFINANCIALS 1503 minimum

Mandatory

SAP NetWeaver 7.5

SAP NetWeaver 7.5


the Custom Code. For more information see SAP Note 2241080 Custom code check content for

Optional






SAP S/4HANA on-premise edition.

SAP NetWeaver 7.5







Components


Comments Relevance



For connection to SAP Service Marketplace.

Mandatory



Mandatory



Upgrade with SUM. Please see Software Logistic Toolset 1.0 on SAP Service Marketplace for details.

Mandatory




Comments Relevance

SAP S/4HANA


Mandatory

SAP HANA

SAP HANA Platform Edition 1.0

Check SAP Note 2189824 SAP S/4HANA, on-premise edition 1511: Release Information Note

Mandatory









Platform Edition

SPS11 minimum

for the SAP HANA revision.

4.2 Further Requirements Hardware:

The operating system platform must be 64-bit.

Operating System Version:

For a comprehensive list of supported operating system releases, see the Product Availability Matrix (PAM).

Database Software:

For the minimum supported database releases, please check the SAP Notes listed on Software Logistics Toolset 1.0.

SAP Host Agent:

Use at least the following version: SAP Host Agent 7.21. We recommend updating to the most recent version. Please check SAP Note 1031096 Installing Package SAPHOSTAGENT.

4.3 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 https://support.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.

https://apps.support.sap.com/sap/support/pam

https://apps.support.sap.com/sap/support/pam





https://support.sap.com/swdc





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 and Template Name

BP_BSCON_S4HANAXV1 - SAP Best Practices for system conversion for SAP S/4HANA_V1

Solution Package Name(s)

SAP Best Practices for system conversion for SAP S/4HANA_V1

Documents

SAP Best Practices for system conversion for SAP S/4HANA ...sapidp/012002523100003217232016E/BP_BSCON...Business Process Alternative/Decision Choice Typographic Conventions Type Style