S/4HANA On Premise Post System Document

Document Version: 1.0 – December 1, 2017

SAP S/4HANA On Premise Post System Copy Steps

Document History

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.0 December 1, 2017 Initial Version – Gilbert Wong

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.

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

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

Table of Contents

1 Introduction ......................................................................................................................................... 5

2 Documentation Links........................................................................................................................... 6

3 Pre-Requistes .......................................................................................................................................7

4 SAP S/4HANA On Premise Post System Copy Post Steps ................................................................ 8

5 SAP S/4HANA On Premise Optional Steps ...................................................................................... 22

1 Introduction

This document will provide you the required post system copy steps to get your SAP S/4HANA On Premise system up
and running. The document will guide you through the steps required after you have successfully performed a SAP
system copy of both SAP S/4HANA Backend and Frontend system. This document will not cover the SWPM steps for
the target System of a standard System Copy. After completing the post system copy steps, you will have a
functioning SAP Fiori Launchpad connecting to the SAP S/4HANA backend system.

High level post system steps include:

➢ Generate SAP License

➢ Adopt SAP Instance Profiles
➢ Reconfigure SSL
➢ Reconfigure Trusted RFC on both BES and FES
➢ Reconfigure SAP Web Dispatcher Instance Profile
➢ Reconfigure SAP Web Dispatcher SSL
➢ Reconfigure RFC’s
➢ Reconfigure STMS
➢ Reconfigure SAML

Optional Steps, if SID rename is performed:

➢ Update logical system names
➢ Reconfigure Enterprise Search
➢ Reconfigure Alias

SAP S/4HANA On Premise Post System Copy Procedures P a g e |5

2 Documentation Links

Below are the links to various S/4HANA On Premise documentation to be used as reference to the installation.

Documentation

Maintenance Planner User’s Guide

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

Software Provisioning Manager 1.0 (SWPM) and Software Update Manager (SUM) and SPAM/SAINT
https://help.sap.com/sltoolset

SAP HANA Server Installation and Update Guide

http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf

SAP System Copy Guides

https://help.sap.com/doc/30839dda13b2485889466316ce5b39e9/CURRENT_VERSION/en-
US/14678bf6e9a04f4f9dc3a1620e96c0b7.html

SAP S/4HANA On Premise Post System Copy Procedures P a g e |6

3 Pre-Requisites

As a prerequisite for SAP S/4HANA On Premise post system copy document, you will need to perform a homogenous
or heterogenous system copy procedure. To perform a SAP system copy, you will need to follow the standard system
copy procedures. Please refer to the following SAP System Copy procedure for details steps. Both SAP S/4HANA
Backend and Frontend system must be successfully copied and started before use.

We will use the following acronyms in this guide:

BES = SAP S/4HANA Backend System
FES = SAP S/4HANA Frontend System

SAP S/4HANA On Premise Post System Copy Procedures P a g e |7

4 S/4HANA OP System Copy Post Steps

After completing your SAP Heterogenous / Homogenous system copy onto your new environment, follow the steps to
complete the post configuration steps to get your S/4HANA backend and frontend Fiori Frontend system up and
running.
Generate and install new
SAP License Key.

TCODE = /nSLICENSE

System = BES and FES

Configure HTTP security

session management

TCODE = SICF_SESSIONS

System = BES and FES

A list of all of the clients that exist in the system appears.

Select the relevant line and choose Activate.
Maintain Instance Profiles
Adopt Instance profiles for both Backend and Frontend system using transaction
code RZ10 to match source and target systems.
TCODE = RZ10
Here are some sample profile parameters:
login/system_client = 300
System = BES and FES login/accept_sso2_ticket = 1
login/create_sso2_ticket = 2
rdisp/wp_no_dia = 15
rdisp/wp_no_btc = 6
icm/HTTPS/verify_client = 0
icm/HTTPS/trust_client_with_subject = *
icm/HTTPS/trust_client_with_issuer = *
icm/server_port_0 = PROT=HTTP, PORT=8101, TIMEOUT=600, PROCTIMEOUT=600
icm/server_port_1 = PROT=HTTPS, PORT=44301, TIMEOUT=600, PROCTIMEOUT=600
icm/server_port_2 = PROT=SMTP, PORT=25001

SAP S/4HANA On Premise Post System Copy Procedures P a g e |8

Reconfigure SSL on both
Backend and Frontend
Servers

TCODE = STRUST

System = BES and FES

Regenerate CSR request and

have it signed by public or
internal Certificate Authority.

Delete old SSL Server

Standard and recreate it.

Create new SSL Server

Standard

SAP S/4HANA On Premise Post System Copy Procedures P a g e |9

Enter valid SSL PSE
information.

Valid entries and click on the

Green check.

Once SSL Server is created,

import the certificate to BES
and Web Dispatcher trust
store.

Repeat for SSL Server, SSL

Client (Anonymous and
Standard)

Complete SSL configuration

for both FES, BES, and Web
Dispatcher.

Validate SSL Configuration

TCODE = STC01

Task List =
SAP_BASIS_SSL_CHECK

Click on “Generate Task List Run” or Execute button.

System = BES and FES

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 10

Verify Results. You can
ignore “Certificate is self-
signed” if this is a sandbox
system and you do not
require signed certificate.

Reconfigure Trusted RFC on

both BES and FES

TCODE = STC01

Task List =
SAP_SAP2GATEWAY_TRUSTED_CO Click on “Generate Task List Run” or Execute button.
NFIG

System = BES and FES

Click on the Parameter

button for “Create / Select
ABAP RFC Destination to
SAP System (SM59)

Click on Select RFC

Connection and select RFC
Destination.

Click on the Save Icon.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 11

Click on Start/Resume Task
List Run in Dialog.

Review logs.

Adjust Web Dispatcher Ensure all parameters from old web dispatcher is maintained in the new web
instance profiles. dispatcher instance profile.

System = Web Dispatcher

Example:
ssl/ssl_lib = /usr/sap/WEB/SYS/exe/uc/linuxx86_64/libsapcrypto.so
ssl/server_pse = /usr/sap/WEB/W05/sec/SAPSSLS.pse
icm/HTTPS/verify_client = 0
ssl/client_pse = /usr/sap/WEB/W05/sec/SAPSSLC.pse
wdisp/ssl_encrypt = 1
wdisp/ssl_auth = 2
wdisp/ssl_cred = /usr/sap/WEB/W05/sec/SAPSSLC.pse
icm/HTTPS/forward_ccert_as_header = true
icm/server_port_0 = PROT=HTTPS,PORT=44300, TIMEOUT=120
icm/server_port_1 = PROT=HTTP, PORT=8005, TIMEOUT=120
icm/server_port_2 = PROT=HTTPS,PORT=44800, TIMEOUT=120
wdisp/system_conflict_resolution = 1
wdisp/add_clientprotocol_header = 1
wdisp/handle_webdisp_ap_header = 1
wdisp/add_xforwardedfor_header = true
icm/HTTP/mod_0 = PREFIX=/, FILE=$(DIR_GLOBAL)/security/data/icm_filter_rules.txt
wdisp/system_0 = SID=FES, MSHOST=s4hana.cloud.sap, MSPORT=8102, SSL_ENCRYPT=1,
SRCSRV=*:44300,
SRCURL=/sap/bc/bsp/;/sap/bc/ui5_ui5/;/sap/bc/ui2/;/sap/bc/lrep;/sap/opu/odata;/sap/public/;/sa
p/bc/nwbc/
wdisp/system_1 = SID=BES, MSHOST=s4hana.cloud.sap, MSPORT=8104, SSL_ENCRYPT=1,
SRCSRV=*:44300,
SRCURL=/sap/bc/webdynpro/;/sap/es/;/sap/bc/gui/;/sap/bc/apc;/sap/bw/ina;/sap/bw/Mime/DS/C
ontent/

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 12

Log onto web dispatcher
admin page to configure SSL

System = Web Dispatcher

Select PSE Management

Click Recreate PSE

Enter valid Distinguished

Name

Click on Create.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 13

Now export the
SAPSSLS.pse and save to
desktop. You will import this
into the FES and BES trust
store.

Import FES and BES into

SAPSSLC

Click on Import Certificates

Copy and paste Certificate

information.

Click on Import.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 14

Repeat steps for both FES
and BES.

Update RFC ABAP

destinations with new
hostname.

TCODE = SM59

System = BES and FES

Modify all RFC with new hostnames and ports and save.
Update all SM59 RFC for
classic UI apps.

TCODE = SM59

System = FES

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 15

Update all SM59 HTTP(s) for
classic UI apps.

TCODE = SM59

System = FES

Post SYSTEM copy steps

(SE06 and STMS)

TCODE = SE06 and STMS

System = BES and FES

Select Database Copy or Database Migration.

Click on Perform Post-Installation Actions.
Click on Yes.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 16

Enter Source system of
database copy.

Click on Green check.

Click on Green check.

Click on Yes

Click on Yes.

Click on Yes.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 17

Click on Yes.

Run STMS

System = BES and FES

Enter Password.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 18

Activities at Operating This section includes the adaptations that you have to make at operating system
System Level level in your target system.

System = BES and FES - Adapt the configuration files at operating system level to meet network and
SAP requirements.
- Adapt additional SAP software components (for example, RFC, CPIC, SAP
ArchiveLink) if required.
- Adapt additional non-SAP software components (for example, archiving
systems, monitoring tools, job schedulers) if required.
- Adapt backup programs (for example, BRBACKUP, BRARCHIVE, BACKINT) if
required.
- Adapt non-SAP directories, file systems, NFS mounts, and so on, if required.
- Check the SAP parameters of the default and instance profiles.
- Check your UNIX shell files for special entries.
- Check crontab or AT jobs.
- Check operating system files (for example, .netrc, .rhosts).
- Check operating system printers.
- If the spool requests are stored at file system level, you must copy the
subdirectories with the spool files to the new global directory.
Activities at Database Level This section includes the adaptations that you have to make at database level in
your target system.
System = BES and FES
- Before starting the SAP system, make sure that the logging mechanism of the
database is active.
- Check the parameters in the database profiles.
- Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP,
MONI, OSMON, PAHI, SDBAD, SDBAP, SDBAR.
- Delete entries in the table DDLOG for buffer synchronization.
- If your source database was SAP MaxDB, run report RSSDBTICMCLEANUP on
the target system. This will delete data that is related to the source system.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 19

Update Operation modes.

TCODE = RZ04 / SM63

System = BES and FES

Update SAP Logon Groups.

TCODE = SMLG

System = BES and FES

Check SPAD config in case

for server name requires
adjustments.

TCODE = SPAD

System = BES and FES

Run spool consistency

check.

TCODE = SP12

System = BES and FES

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 20

Adjust RFC server groups.

TCODE = RZ12

System = BES and FES

Reconfigure SAML
configuration if required.

TCODE = SAML

System = FES

Replicate App Descriptors

from Back-End System

TCODE = /UI2/APPDESC_GET

System = FES

In the Catalog ID field, enter SAP_*_BC_*

Then click on Execute.
Recommendation is to schedule this report
/UI2/GET_APP_DESCR_REMOTE to run daily and after every system upgrade.

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 21

5 S/4HANA On Premise Optional Steps

The following steps are required if you perform a SID rename.

Update Logical System

Names

TCODE = BDLS

SYSTEM = BES and FES

Regenerate ESH indexes

after system copy

TCODE = STC01

Task Lisk =
SAP_ESH_ADJUST_AFTER_COPY Click on “Generate Task List Run”

SYSTEM = BES

Click on Fill Parameter for

“Set Parameters for
Adjusting Data after a
System Copy”

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 22

Click on Use SAP HANA
Primary DB Connection:
DEFAULT
Enter Source System ID
Update database and
indexes checkbox

Click on Save.

Click on Start/Resume Task

List Run in Dialog.

Click on “Background”.

Reconfigure System Alias for

Please refer to the following SAP blog for more information on how to update the
SAP OData services if Alias
name need to be changed. System alias for the new SAP SID.
https://blogs.sap.com/2017/11/30/fiori-for-s4hana-mass-odata-unassign/
SYSTEM = FES

SAP S/4HANA On Premise Post System Copy Procedures P a g e | 23

www.sap.com/contactsap

© 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.
The information contained herein may be changed without prior
notice. 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 or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP 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.
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. All other product and service names mentioned are the
trademarks of their respective companies. Please see
www.sap.com/corporate-en/legal/copyright/index.epx for
additional trademark information and notices.

Material Number: