0% found this document useful (0 votes)
31 views263 pages

02 ECC Dev S4HANA Conversion

Uploaded by

Rohit Kushwaha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views263 pages

02 ECC Dev S4HANA Conversion

Uploaded by

Rohit Kushwaha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 263

ABSTRACT

[Draw your reader in with an engaging abstract. It is


typically a short summary of the document. When
you’re ready to add your content, just click here and
start typing.]

Kambli, Meghan
[Course title]

S/4HANA
CONVERSION
S/4HANA 2020 FP02
Table of Contents
1.1 Preparing the Conversion ......................................................................................................... 2
1.1.1 System Requirements ..................................................................................................... 52
1.1.2 What’s the Impact on Your System Landscape? .............................................................. 65
1.1.3 Supported Start Releases ................................................................................................ 66
1.1.4 Data Volume Reduction .................................................................................................. 67
1.1.5 Maintenance Planner ..................................................................................................... 67
1.1.6 Simplification Item-Check .................................................... Error! Bookmark not defined.
1.1.7 Custom Code Analysis..................................................................................................... 88
1.1.8 Cross-Application Preparations ....................................................................................... 88
1.1.9 List of Application-Specific Preparations ......................................................................... 90
1 Planning
1.1 SUM Planning

1.1.1 Initial Dialogs for the Scenario Specification (Get Roadmap)

Downtime optimized
strategy will be used

Standard strategy will be


used as per SAP
Recommendation

Prerequisite check tool will


be used

1.1.2 Unicode Aspects

Unicode Conversion is
already completed
1.1.3 Adaption of Parameters

1.1.3.1 Database Archiving Parameter


Archiving mode will be on

1.1.3.2 Using the near-Zero Downtime Maintenance (nZDM) Feature


We will be using the
standard mode

Informative

1.1.3.3 Using the Record & Replay Technique in nZDM

Informative
Informative on how to use
the tables with larger in
size to include them table
list files

1.1.3.4 Process and Tool Parameters


As per the SAP notes
1616401, 1945399 tuning
the work processes for
R3LOAD calculating based on
Number of CPUs X 1.3 =
R3trans processes to use

For SQL processing it is


calculated as Number of
CPUs X 1.5 = SQL PROCESSES

For R3LOAD processes we


use 3 times the number of
available CPUs

1.1.3.5 Shadow Instance Parameters


Expert mode will be off
1.1.3.6 SGEN Execution Modes
Generate ABAP loads on
shadow system during
uptime and start
asynchronously in post
downtime

1.1.4 Time Frame for Upgrading the Front-End Software

Not Applicable

There is no release upgrade


1.1.5 Database-Specific Aspects

HANA log mode will be


overwrite since beginning
of UC downtime

1.1.6 Planning the Data Management

Not Applicable since this is


no release upgrade

1.1.7 Modification and Enhancement Adjustment Planning


Informative

1.1.8 Import of Additional Languages

Not Applicable since there


will not be import of any
additional languages
1.1.9 Handling Customer-Specific Translations and Languages

Not Applicable since this is


not release upgrade

1.1.10 Excluding Customer-Specific Languages


SE16 >> T002 >> Enter

Execute
SE16 >> T002C >> Enter
No X mark in LAINST
column.

No action needed
1.1.11 Component Levels Contained in the Upgrade Export

Not Applicable since this is


not release upgrade

1.1.12 Updating Distributed and High Availability (HA) Systems

Not applicable since this is


not Distributed System
1.1.13 Importing Support Packages Before an Upgrade

Not Applicable since this is


not release upgrade

1.1.14 Integration of Customer Transports

Informative
1.1.15 ASCS Instance Split

ASCS is already setup

1.1.16 ASCS Instance Move

Not required since current


host OS is supported

1.1.17 Switch to Standalone Enqueue Server 2

Applicable for HA
environment only
1.2 Runtime Optimization

Need to be verify with


Rajesh

Will be followed in case of


error

Asked Functional team to


check

Recommendations from
note 235294 have been
included in downtime
optimization tasks
2 Preparation
2.1 STMS Configuration

STMS route Pending


2.2 SUM Preparation

2.2.1 Determining the Host for the Preparations

Application host and DB


host same

devadm
hsdadm

2.2.2 Checking the Hardware Requirements

APP

APP
Add swap if not available
(2x RAM)

dd if=/dev/zero
of=/usr/sap/swapfile
bs=1024 count=65536000

chmod 600
/usr/sap/swapfile

mkswap /usr/sap/swapfile

swapon /usr/sap/swapfile

APP - Swap

dd if=/dev/zero
of=/usr/sap/swapfile
bs=1024 count=2000000

chmod 600
/usr/sap/swapfile

mkswap /usr/sap/swapfile

swapon /usr/sap/swapfile
DF - FS
Confirm
2.2.3 Checking the Software Requirements

2.2.3.1 Checking the Source Release of the SAP System


2.2.3.2 Checking the Uninstallation of Software Components
2131368 - Uninstalling SAP
Fiori OData component
GBAPP002 600 using
transaction SAINT

2771798 - S/4HANA
readiness of Fiori Business
Suite Add-Ons

The note is applicable for


add-on installation only
Highlighted add-on will be
uninstalled
Check with Martin for Fiori
roles used for app

SAP_GBAPP_PO_APPROVA
L_MANAGER

No user assigned

SAP_GBAPP_PR_APPROVAL
_MANAGER

No user assigned

SAP_MM_PO_APV_APP

No user assigned

SAP_MM_PR_APV_APP

No user assigned
Deactivate
GBAPP_POAPPROVAL
service

GBAPP_PRAPPROVAL
service did not exist

Prerequisites are met –

000 DDIC password

Start
Start in Background
ABAP Team deleted the
objects

Continue
Finish

Do not send
2.2.3.3 Meeting the Operating System-Specific Requirements
Current Kernel version is
753

Not Applicable

2.2.3.4 Upgrading Operating System and Database


cat /etc/os-release

2.2.3.5 Software Components for SAP HANA Database


2.2.3.6 Saving the Environment Files
Need to be performed
before execution phase

2.2.4 Checking the Central Services Requirements for ABAP


Rdisp/mshost

Rdisp/wp_no_vb2

2.2.5 Configuring OS User Authentication


OSS note is not applicable
for kernel release 753

2.2.6 Setting the Operation Mode for the Update

Not required since system


will not be released to end
users for regular
operations before S4HANA
Conversion downtime
2.2.7 Checking the Number of Background Processes

SM50

2.2.8 Checking the Requirements for the Modification Adjustment

Informative
2.2.9 Releasing and Confirming Open Repairs and Requests

Customer has been


informed about this

2.2.10 Filling the Download Directory

All downloads under the S4


media in APP server.
In jump server:

C:MediaConversion_m
edia

2.2.11 Preparing the Update of High Availability Systems

Not Applicable for non-


production system since
HA setup is not there
2.2.12 Extract SUM

Copy SUM in /usr/sap/DEV


Extract SUM in
usr/sap/DEV with devadm
user

SUM folder Created

2.2.13 Pre-requisite Check Tool (SUM)

Start SUM tool with root


user

**** SUM ABAP:


https://faau1ls4dbd1:1129
/lmsl/sumabap/DEV/slui
****
**** SUM Observer:
https://faau1ls4dbd1:1129
/lmsl/sumobserver/DEV/m
onitor/index.html ****
Place XML in download
directory
Check ELG file.

M_KRED

M_ZREP

M_ZVAR
SE11 >> Runtime check

Table is inactive for all four.

M_KRED

M_ZREP

M_ZVAR

M_KRED

M_ZREP
M_ZVAR

All are matchcode objects


As recommended by SAP in
OSS message 766953
All tables are deleted after execution
of the function module

2.2.14 Finalize Instance Type for S4HANA Conversion

r5.8xlarge App Server


r5.24xlarge For DB Server
2.2.15 Check SAP’s recommendations
2.3 Preparing the Conversion

2.3.1 TR Import

SBXK900088

SBXK900094
SBXK900106

SBXK900100
SBXK900108
SBXK900146
SBXK900092
SBXK900112
SBXK900114
SBXK900116
SBXK900120
SBXK900135

All Imported

SBXK900104
SBXK900098
SBXK900110

Error
SBXK900130
SBXK900122

SBXK900096
SBXK900141
SBXK900144

SBXK900138
2.3.2 Remove Client 066

Login to client 066 and


execute tcode scc5
25 mins
25 mins

2.3.3 Simplification Item-Check

Already covered in Unicode Conversion Cookbook

/sdf/rc_start_check

Login to client 000


Execute

Check Consistency for all

\
2.3.4 System Requirements
Informative

2.3.5 What’s the Impact on Your System Landscape?

No J2EE process
Informative

Informative

2.3.6 Supported Start Releases


2.3.7 Data Volume Reduction

Not Applicable

2.3.8 Maintenance Planner

No such messages
displayed
Add XML from spam when
adding new system
Click Verify
Select Ignore

Select Ignore
Select fiori
Select uninstall
Install add on
Final Target Details
Confirm
2.3.9 CVI Cockpit Implementation

Already covered in Unicode Conversion Cookbook

2.3.10 Custom Code Analysis

Informative

2.3.11 Cross-Application Preparations

2.3.11.1 Prepare the Use of the Maintenance Planner


Already covered in 2.3.5
2.3.11.2 Uninstall SAP Fiori Apps
Not reqd in dev as was
included in xml to uninstall
FIORI APPS

Was also identified in


Maintenance Planner

Uninstallation will be
performed by SUM

2131368 - Uninstalling SAP


Fiori OData component
GBAPP002 600 using
transaction SAINT

2771798 - S/4HANA
readiness of Fiori Business
Suite Add-Ons

2.3.11.3 Prepare the Conversion of Authorizations


This will be covered during
follow up steps
2.3.11.4 Prepare the Conversion for SAP Fiori UX Enablement
Informative

2.3.12 List of Application-Specific Preparations

Asked Functional team to


check
2.4 HANA Backup (after S4HANA Conversion Preparation Steps)

Backup Tenant Database.

Backup completed

3 SUM Execution
3.1 Extraction

DEV: Software Update


Manager
Next.
Standard Strategy

Select customer transport


integration

SKIPPED for NOW


SKIPPED

https://blogs.sap.com/201
7/11/24/integrating-
customer-transport-
requests-in-updates-and-
upgrades/
SKIPPED

SKIPPED
Keep customer transport
integration unchecked

DDIC:
S#1SNgskK$$S

DB: Frucor@123
Downloaded and placed
version 54
Go back and click next
again

Extraction started at 2 Pm
26/11

Extraction finished at 2:15


PM
Config started at 2:17 PM

Frucor@123
Total 50 Min Run.

3.2 Configuration
User created on 15th Nov

Continue
Uncheck and next

lscpu

Default parameter to be
changed
Default parameter to be
changed
ABAP : DEFAULT

CPU : 32
SQL : 32

= CPU count
R3TRANS : 32

= CPU count

R3LOAD : 128

= CPU count * 4

Increase SGEN Process 10


SBXK900157

For DEV system

Enter SPDD TR
Enter SPAU TR (with
missing note)
Add them In DEV import
queue

Yes
Yes, SUM will create user.
Tick and next

Just next
It was 3 earlier changed as
per SBX

ST-API previously 2
Data.csv
Minimum level 2
maintained for STA-PI
Add into import queue
Mail drop Rajesh 28thOct
12.06 AM IST
SI Checks error, Mail sent
to Rajesh Dua.

SUM GUI was not


accessible

Decided to upgrade host


agent
Killed SAPup process

SAPGUI screen is now


visible

Next

Continued at 11:33 IST at 7-


Nov-2021

All BTC work processes


were occuppied

Deleted active BTC


processes
Tick in igonre the
Diffrences of SPDD and
SPAU.
3.3 Checks

08:10 AM IST .5th Dec 2021

Started.
Next
Checked all Information
and Summary at the end of
Check phase and continue.

40 min run

3.4 Preprocessing

Started 9:00 AM 5th Dec


2021

Error encountered: Mail


sent to Deepak and
Bengali.

Mail sent 9:10 5th dec


Ignore error and continue.
Ignore suggested by
AMANDA.
There is no update record
found.

Delete from SM13


Then continue with SUM

Running.

SUM resumed 1.30 PM 6th


DEC 2021

And running
In shadow instance profile

abap/heap_area_total
abap/heap_area_dia
abap/heap_area_non_dia

.../abap/bin/SAPup stopshd

rdisp/wp_no_dia = 15

.../abap/bin/SAPup
startshd
Lock the Dev

Inform the team

Proceed.
Issue resolved by Bangali.

Had discussion with


Realtech and Frucor

Decided to import SNP


installation TR into DEV
system.
User is created copy of
DDIC in shadow system.

ABAP_SPDD is created
shadow system with
password: Welcome@123

System will handover to


ABAP team:
Bengali/Deepak.

SPDD activity is finished.

SUM continue: 7th Dec


6.50 PM 2021
Shared ACTUPG.ELG with
Deepak

Continued after
confirmation from Carola

At 8:15 AM IST 12-Nov-


2021

Next
At 9:00 AM IST 12-Nov-
2021

Asked Deepak to check

These 2 views are not being


used any more

Accept errors and continue

At 9:15 AM IST 12-Nov-


2021
Log mode change to
overwrite in HANA Studio.

Received at 14:40 IST 12-


Nov-2021
Login to shadow instance

Copy user

Login with copied user


SAPOSS RFC failed

Download and upload the


note for SNOTE
Implement
Next

Taking long

Decided to cancel the job


Error at 16:15 IST 12-Nov-
2021

Continued at 19:15 IST 12-


Nov-2021
Reached at 8.30 PM 8th Dec
2021

Not recommended by SAP .

NR.
3.5 Pre-Downtime Steps

3.5.1 Backup

3.5.1.1 SUM and Kernel Backup


20 mins

3.5.1.2 HANA Backup


COMPLETE_DATA_BACKUP
_Pre_S4H_SUM_Downtime
3.5.2 Saving the Environment Files

3.5.2.1 Downtime Optimization


Refer DowntimeOptimizationSteps.xlsx in Planning folder
3.5.2.2 SAP Profile Parameter Change
Increase DIA and BTC work
processes

DIAG = 80
BGD = 40

Restart reqd

Normal utilization found

3.5.2.3 HANA SQL commands


Choose column C from
Spread sheet .
3.5.2.4 HANA Parameter Changes

Lscpu on Db server

32 cpus
Adding parameter:-
parallel_merge_part_threa
ds

Right click on indexing then


add parameter.

added
3.5.3 Isolation

SM12

Ignore and Proceed

SM13

Make sure to keep date


blank and check

Entries were ignored which


in turn resulted in sum
execution error
Delete all entries

SU10

Excluded users

Users locked
BTCTRNS1

SMQ1
3.6 Execution

Get the confirmation from


Subhash and Rajesh

Continued at 01:20 AM
Stopped Instance manually
Backup was already taken

Click next
Again manually stop

Approx execution started


at 2:00 AM IST
There were entries in sm13

Deleted them
Stop manually again

Breakpoint added
Break point reached at 3:30
am
Already 80 wp there

Os level no change
Updated at OS level and
took restart

Started again at 4:00 am


IST
Active work processes

Resolution:

Stop sap system


4.5 HR run Excution
Received at 11:30 AM IST
13-Nov-2021

Killed old ASCS sapstartsrv


process
Copied executables from
PAS exe to ASCS exe
Started sapstartsrv for
ASCS profile

Manually started PAS

Continued at 12:30 AM IST


13-Nov-2021
Completed at 12:30 AM IST
13-Nov-2021
3.7 Postprocessing
Move SUM folder to
filesystem with enough
empty space (20 mins)
cd /usr/sap

df -h .

cd /usr/sap/DEV

du -sh *

cp -rp SUM SUM_post_execution

Next
Next

Close
Do not
continue or
cleanup SUM

LONGPOST.LOG

Share
LONGPOST.LOG
details with Rajesh

SE38 >> Execute in


background for reports
listed in LONGPOST.LOG
4 Follow-up Steps
4.1 HANA Backup (after S4HANA Conversion SUM Execution)

Not required

Already taken after


Execution phase

4.2 SUM Follow-up Steps

4.2.1 Generating Loads

Generate All objects of


selected components

Components
Select All

Continue

Continue

Select job >> Start job

4 hours
4.2.2 Updating the Where-Used List in the ABAP Workbench

SE38 >> SAPRSEUB

Run now

Job is finished:

30,538 sec.
4.2.3 Solving P-Errors

CHECKS.LOG

Check CHECKS.LOG if any


action is needed

4.2.4 Performing Follow-Up Activities for SAP Profiles


All instance are Configured
properly.
4.2.5 Performing Follow-Up Activities for User root

Run folder having all


permission.

# cd /usr/sap/DEV/SYS/exe

# ls -ltr

# cd uc/linuxx86_64/
# cp -p ./icmbnd.new
./icmbnd

# chown root:sapsys
icmbnd

# chmod 4750 icmbnd

# ls -ltr icmbnd
4.2.6 SAP HANA DB: Backing Up the Database

Not required

Log mode is normal and


backup will be taken after
s/4hana conversion follow-
up steps

4.2.7 Performing Follow-Up Activities in the Monitoring Area

N/A

4.2.8 Performing Follow-Up Activities for the SAP Kernel


Kernel is latest no need to
take any action.

4.2.9 Reimporting Additional Programs

N/A

# cd
/usr/sap/DEV/SYS/exe/run

# ls -ltr | grep -i protect


No protect.lst file is there
for additional Program.
4.2.10 Adjusting Repository Objects

SPAU. System will be


handed over to ABAP team

4.2.11 Adjusting Customizing Settings

Need to check with Rajesh

4.2.12 Adjusting Customer Developments

Not Applicable.
4.2.13 Performing Follow-Up Activities for SAP Solution Manager

Realtech will do this task

4.2.14 Adjusting the User and Role Administration

Not required in Non- Prd


system.

4.2.15 Checking the System Time Zone Settings

Time zone is correct

Timezone should be NZDT


STZAC

User’s default time zone


changed to NZST

4.2.16 Performing Follow-Up Activities for Application Link Enabling (ALE)


RBDCPMIG_ALL_WITHOUT
_MIG_FLAG
4.2.17 Upgrading Additional Application Server Instances

Not Applicable

4.2.18 Checking for Indexes Unknown to the SAP System

No Missing Object
4.2.19 Importing Support Packages After the Update

Support package is not


planned

4.2.20 Transport Management System: Distributing the Configuration

STMS >> System Overview


4.2.21 Performing Follow-Up Activities for the Language Transport

N/A
4.2.22 Saving Files for Subsequent Updates

4.2.23 Deleting Log Files

To be skipped

4.2.24 Remove Old RZ10 Profiles

Rz10
4.2.25 Remove old entries from SMLG

Goto SMLG

Delete assignments

4.2.26 BW Follow Up Steps

Maintain RSA1

4.3 S/4HANA Conversion Steps


4.3.1 Cross-Application Follow-On Activities

4.3.1.1 Adapting Database Extensions to SAP S/4HANA


Details to be shared with
ABAP team

No action needed from


Basis

Talked to Milan. Since no


errors were reported, no
action is needed.

4.3.1.2 Output Management


Screenshot update
ADS is not being used as
confirmed by Realtech in
daily meeting held on 16-
Nov-2021

NA, Informative
4.3.1.3 Follow-On Activities for the Conversion of Authorizations
Will be performed by
Security Team

4.3.1.4 Follow-On Activities for SAP Fiori UX Enablement (incl. Authorizations)


Reference - Automatic Activation of Embedded-Deployed SAP Fiori - SAP Help Portal

4.3.1.4.1 Fiori Activation

SAP_GW_FIORI_ERP_ONE_
CLNT_SETUP

Run STC01
Just save
CONV : BC :
SAP_GW_FIORI_ERP_ONE_
CLNT_SETUP

CONV : BC :
SAP_GW_FIORI_ERP_ONE_
CLNT_SETUP

Package needs to be
created with ABAP help

Package name: ZBAS001


Start in background
Ended successfully

Download logs

SAP_ESH_INITIAL_SETUP_
WRK_CLIENT
Error

/UIF/SCHEDULE_LREP_JOB
/UI2/FLP_HEALTH_CHECKS
4.3.1.4.2 SAP Fiori - Initial Setup for SAP Fiori Applications in SAP S/4HANA
SAP_FIORI_FOUNDATION_
S4
CONV : BC :
SAP_FIORI_FOUNDATION_
S4

CONV : BC :
SAP_FIORI_FOUNDATION_
S4
Run in background

Duration 20 mins

Log screenshots pending


Resume trask list execution

skip
4.3.1.4.3 Activating SAP Fiori Apps for SAP Business Roles Via Task List
SAP_FIORI_CONTENT_ACTIVATION

Default prefix

User creation to be skipped

SAP_FIORI_CONTENT_ACTI
VATION
Execute in background
4.3.1.4.4 Configure Fiori Custom Code Migration App
App Configuration: Custom Code Migration - SAP Help Portal
4.3.1.4.5 Error while accessing launchpad
Issue resolved after
activating services

URL works only in EDGE


browser

4.3.1.5 Adapting the User Interface


4.3.2 List of Application-Specific Follow-On Activities

Functional Tasks

4.3.3 Cleaning Up Obsolete Data After the Conversion

4.4 Credit Management Migration Activities

4.4.1 Configure SOAP Runtime

Configure SOAP Runtime -


SAP Help Portal
Login to client 000

SRT_TOOLS

Technical Configuration of
SOAP Runtime.
Check Technical Setings
Login to client 800

And repeat same steps


Provide required
authorization to user
SAP_WSRT

t-code SBGRFCCONF

Change
CL_SOAP_QUEUE_BGRFC_
MON_CB

Tick Active/Inactive

Save
Repeat the check

4.4.2 Activate HTTPS Port

SMICM >> Services


icm/server_port_1
PROT=SMTP,PORT=25000,T
IMEOUT=120,PROCTIMEOU
T=120

icm/server_port_2
PROT=HTTP,PORT=8443,TI
MEOUT=60,PROCTIMEOUT
=600

icm/server_port_0
PROT=HTTP,PORT=8080,TI
MEOUT=60,PROCTIMEOUT
=600

4.4.3 Maintain Logical System

Check logical system for all


clients except 000 and 001

SCC4
4.4.4 Set up Webservice Configuration

4.4.5 Pre-requisite settings for Documented Credit Decision

4.5 SAP GUI for HTML

Request came via Julian. Document saved in References folder. These are redundant steps. All steps are
performed during Fiori Activation. No action needed
Already Activated.
Test not possible because
port is not maintained.

Port not configured.

Previous Config.

Adding Parameter
Tested again it worked

4.6 TR Import

Copy data and cofiles to


/home/ec2-user folder

chmod -R 777 data cofiles

Copy to jump server

Copy from jump server to


target application server in
/home/ec2-user folder

Add TRs with status


“Downtime” and “Post-
conversion” to import
queue with commands in
DowntimeOptimization
spreadsheet

Duration 1 hour

4.7 Integration between S4HANA and BW

Post processing steps for SAP BW system copy or db copy | SAP Blogs
4.7.1 Action in S4HANA system

Pending
Create LS
Add outbound port

RSINFO

Add inbound port


4.7.2 Action in BW system

There is no change in
source system (S4HANA)
SID and client number.
Thus, BDLS execution is not
required.

RSLOGSYSDEST
RSBASIDOC

Pending

RSAP_BIW_DISCONNECT
Since BW is not copy of any
other BW system (different
SID or client), this change is
not required
Will be performed by BW
team

right –> restore


User administrator

Continue

Use

also replicate

Dialog

execute evaluation

4.8 Revert HANA parameters


Work Process change.

4.9 Scale Down Instance

4.10 HANA Backup (after S4HANA Conversion Follow-up Steps)

4.11 Rescheduling Background Jobs

Can be done after SPAU


completion
4.12 Handover system to functional team

Addon installation:

You might also like