Migrate HW and Upgrade

EHP7 Documentation for

Project Summary
NALCO
Document Title

SAP ECC 6.0 EHP3 to EHP7

Document ID

EHP Upgrade-001

Project Title

Hardware Migration and Version upgrade (EHP3 to EHP7)

Owner

KloudData www.klouddata.com

Author

KloudData Team

Filename

SAP_ECC 6.0 Migrate HW and Upgrade _v1.0

Version

1.1

Date

27th July Prepared

2015

Status

Draft

by

KloudData Inc.
www.klouddata.com
Prepared for

NALCO

Table of Contents:

The contents of this document are the sole and exclusive property of KloudData Inc. They may not be
disclosed to any third party, copied or reproduced in any form or used for any purpose, other than that for
which they were provided, without the express permission of KloudData Inc. All other company, product
names, logos and brands are trademarks of their respective owners.

1. Existing
SAP
.4

Landscape

details:

2. ERP
User
based
5

Sizing:

3. Migrate
to
New
6
4. Upgrade to EHP7:
H/W6

H/W:

Homogenius system copy to new

5. System
landscape
connected
CUA7

SAP_ECC 6.0 Migration & Upgrade Document v1.0

in

Solman

7.1

Page 2 of 14

1. Existing SAP Landscape details:

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 3 of 14

System details: ECC 6.0 EHP3,

Database: DB2 9.5,
OS: AIX 7.1
Kernel version: 700
All the production landscape is in the scenario of High Availability (HA).

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 4 of 14

1- First Upgrade the ECC dual stack till ehp6, then perform Split of the ECC system (ABAP & JAVA), and
then go to separately EHP7 upgrade.
2- First split the system at current level itself (ERP 6.0 EHP3), then go for EHP7 separately for both stack
upgrades.
Which one would be better for us in terms of Fast process/ Safety/ Less effort and last one not the least Less
Solman MOPZ activities while doing split and separate upgrade of both stack?
Separate upgrade for two stacks (now 2 systems after split), If UME still exists in ABAP stack, then make
sure that ABAP is available online while JAVA is upgraded.

First ABAP and then JAVA upgrade.

The target NW version will be 7.4.

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 5 of 14

2. ERP User based Sizing:

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 6 of 14

3. Migrate to New H/W:

Hardware vendor will be setting up new H/W as required.
He is responsible for installing the Operating system as well.

6. Upgrade to EHP7: Homogenius system copy to new H/W

Overview:
A System Copy between two systems running on the same operating system is called a Homogeneous
System Copy and can be performed using the R3load tool or by using the DB2 redirected restore procedure.
A System Copy between two systems running on different operating systems or different DBMS systems is
called a Heterogeneous System Copy. Prior to DB2 Version 8, you could only perform a Heterogeneous
System Copy using the R3load tool provided by SAP.
With DB2 Version 8 and higher, you can use redirected restore to create a Heterogeneous System Copy
between two systems running on different platforms as long as the endianness (big-endian or little-endian) of
each system is the same. Except for the limitations described below, you can take a backup from any bigendian server and restore it to any other big-endian server. For example, you can restore a backup image
from DB2 for HP-UX to DB2 for AIX or Sun Solaris. With Windows you are still limited to the same
platform but you can move from 32bit to IA or AMD 64 bit.

Here are the limitations regarding copying of systems:

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 7 of 14

We can restore a backup image from a lower DB2 version into a higher version, but not the opposite.
For example, you can restore a V8 or V9 backup taken on a Linux system into a 9.5 system running
on AIX. Note that this option is only possible with offline backups and no roll forward is possible.

We can restore a backup image taken on a 32 bit level system into a 64 bit level, but not the opposite.

We can restore a backup image taken from a non-automatic storage database into an automatic
storage database system, but not the opposite.

Software Component Overview of Enhancement Package 7 for

SAP ERP 6.0:
Understanding the architecture of Enhancement Package 7 for SAP ERP 6.0 software is key to
understanding the enhancement package concept.
Enhancement Package 7 for SAP ERP 6.0 is based on SAP Net Weaver 7.4 and consists of
different product instances and software components (see Enhancement Packages and
Software Components: Architecture Overview)
Each of them represents a particular functional component of the software.
The following tables give an overview of the software components included in Enhancement
Package 7 for SAP ERP 6.0. The list of components provided here only represents an excerpt
and is not complete.

ABAP Technology for SAP ERP EHP7

The following table contains the ABAP technology components required to run Enhancement
Package 7 for SAP ERP 6.0:
Table 2
Software Component
MDG FOUNDATION

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Release
747

Page 8 of 14

SAP_BS_FOUNDATION

747

SAP AP

700

SAP WEB UIF

747

The following table contains the components of SAP NETWEAVER 7.4 Application Server
ABAP required to run Enhancement Package 7 for SAP ERP 6.0:
Table 3
Software Component

Release

PI_BASIS

7.40

SAP_ABA

7.40

SAP_BASIS

7.40

SAP_BW

7.40

SAP HOST AGENT

7.20 EXT

SAP IGS

7.20_EXT

SAP IGS HELPER

SAP KERNEL 64-BIT und alternative SCV

7.40

SAP NW GATEWAY FOUNDATION

7.40

SAP VIRUS SCAN INTERFACE

7.20

ST-PI
SCV
USER INTERFACE TECHNOLOGY

2008_1_700 and as an alternative

7.40

Single software components can remain on release 6.00. The following table gives

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 9 of 14

Examples of component versions provided by Enhancement Package 7 for SAP ERP 6.0; the list
of components is not complete:
Table 4
Software Component

Release

Central Applications

EA-APPL

617

SAP_APPL

6.17

EA_IPPE

617

SEM-BW

747

FINBASIS

747

Human Capital Management

EA-HR

607

SAP_HR

6.04

Caution: While SAP HR remains on release 6.04 when you install

Enhancement package 7 for SAP ERP 6.0, EA-HR is
Upgraded to release 6.07.
Enterprise Extensions
Financial Services
EA-FINSERV

617

Retail
EA-RETAIL

617

Industry Solutions
Oil & Gas

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 10 of 14

IS-OIL

617

IS-PRA

617

Catch Weight Management

IS-CWM

617

Utilities/Waste & Recycle/Telco

FI-CA

617

IS-UT

617

Java Technology for SAP ERP EHP7

The following table contains the Java components of the SAP ERP Central Component required
to run
Enhancement Package 7 for SAP ERP 6.0:
Table 5
Java Components
Java Web Applications
SAP FSCM Biller Direct
Content for ERP)

Portal Content
BP* (Business Packages for ERP)

XI Content
XI CONTENT* (XI

SAP Learning-Sol Frontend CP

SAP XSS (Self Services)
SAP XECO
To run these Java applications, SAP NETWEAVER 7.3 or higher is required.

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 11 of 14

Java components include the general Java Web applications such as SAP XSS on the one hand,
and content packages on the other hand. The content packages are available for the product
instances SAP NetWeaver - EP Core/Enterprise Portal. The content is installed in addition to
product instance SAP NetWeaver - EP Core.
If you want to install one or more Java components, you need the Application Server Java,
which is installed by SAPinst.
The software components of SAP ERP Central Component (SAP ECC 6.0, product instance SAP
ECC Server) cannot be installed individually, they are always installed as one instance. For
more information, see SAP Service Marketplace at service.sap.com/sp-stacks
.
The SAP ERP Central Component 6.0 comprises the following components:
SAP ECC Server
SAP XSS (Self Service)
SAP XECO
XI Content
With SAP ERP you also receive a series of industry business solutions that were formerly
delivered as Industry Solution add-ons. With release 6.00 these add-ons were integrated into
the product instance SAP ECC Server.
The following industry business solutions are available with SAP ECC 6.0:
SAP Catch Weight Management
Defense Forces & Public Security
SAP Discrete Industries and Mill Products
SAP Healthcare/SAP Ambulatory Care Management/i.s.h.med
SAP for Insurance
SAP Enhancement Package 7 for SAP ERP 6.0 Powered by SAP NetWeaver

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 12 of 14

SAP Enhancement Packages for SAP ERP6.0

SAP Media
SAP for Mining
SAP Oil & Gas
SAP for Professional Services
SAP Public Sector Collection and Disbursement
SAP Retail
Student Lifecycle Management
SAP Telecommunications
SAP Utilities
Contract Accounts Receivable and Payable
We can use many of the industry business solutions by activating the corresponding business
functions and business function sets. You use them to configure your ECC system to the
requirements of the industry business solution.
To find out which industry business solutions you can use, refer to the Product Availability
Matrix at
service.sap.com/pam.
Enhancement Packages and Software Components:
Architecture Overview:
Prior to the availability of the enhancement package delivery architecture, it was necessary to
upgrade the complete SAP system instance to a new release, for example, from SAP R/3 4.6C
to SAP ERP 6.0. With enhancement packages, it is now possible to update individual software
components of your SAP ERP system or to install new software components, always based on
your choice of technical usage.

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 13 of 14

Note: Update only software components that are related to the functions you want to use.
Note: Make sure to check the SAP NetWeaver Upgrade Master Guide of the SAP NW upgrade
target release if you are planning a NetWeaver upgrade. It contains specific information about
SAP NetWeaver prerequisites, upgrade.

SAP_ECC 6.0 Migration & Upgrade Document v1.0

Page 14 of 14