Complete checklist of converting SAP ECC to SAP S/4HANA.
Overview of SAP S/4HANA Conversion.
Rise with SAP S/4 Conversion refers to the process of technically and functionally transforming an existing SAP ECC System into SAP S/4HANA, SAP’s next‑generation ERP platform. This approach is also known as System Conversion.
Why i am creating this Blog?
When I first received the S/4HANA Conversion project, I did not know where to start because I did not have a proper checklist. At that time, it was challenging to understand the complete starting point and sequence of activities for an S/4HANA Conversion.
Then i decided that after completing this S/4HANA Conversion project, I would create a detailed, step‑by‑step checklist covering all phases and activities. The objective of this checklist is to ensure that, in the future, no one faces confusion about where and how to begin an S/4HANA Conversion project.
We can do Conversion with two methods.
DMO with System Move and DMOVE2S4.
Key Differences between DMO with System Move and dmove2s4.
DMO with System Move
1 Downtime Optimization Limited downtime optimization
2 Data Transfer Method File-based transfer (slower)
3 SUM Run Location Starts on the source system and completes on the target system.
4 Network Intermediate network connectivity
5 Architecture Operates largely as a two-part move. The first part runs on the source primary application server (PAS), exporting data, while the final part runs on the target.
6 Use Suitable for cases where the strict network prerequisites of DMOVE2S4 cannot be fulfilled.
.
DMOVE2S4 (Newer Method)
1 Downtime Optimization Supports downtime‑optimized DMO (doDMO)
2 Data Transfer Method R3load pipe mode (direct memory transfer)
3 SUM Run Location Triggered from the target system’s Additional Application Server (AAS)
4 Network High‑performance network required (Latency < 20 ms, bandwidth > 400 Mbps)
5 Architecture An additional application server is installed in the target environment and connected to the source database. The Software Update Manager is executed from this target AAS.
6 Use DMOVE2S4 is used for fast migration to SAP S/4HANA in cloud environments such as Azure or AWS with minimal system downtime..
Step1 .
The S/4HANA conversion journey is shown below.
Step2 .
Source System Landscape Details. (Platform is on Premise)
Operating Systems—–> HP UX B.11.31 Uia640225047834.
Application———–> EHP8 for SAP ERP 6.0 SPS level is 10.
SAP NETWEAVER———->7.5 SPS level is 11.
Database——————>Oracle 12.1.0.2.0
Kernel—————–>753 Patch Level 201
SAP_BASIS————–>750 SP is 20.
Unicode—————->Yes.
Single Stack Only——>ABAP.
Number of CPU is——->8
Physical Memory——–32
Step3 .
Target System Landscape Details. (Platform is RISE with SAP.)
Operating Systems——->Linux SUSE SP5.
Application————->SAP S/4HANA 2023 SPS level 03.
Database—————–>HANA 2.00.083.00.174064
HANA Client————–>2.0
SAP_BASIS—————-> Release 758 SP level 03.
SAP_ABA——————->Release 75I SP level 03.
Kernel——————–>793 Patch level 300.
Unicode——————->Yes
Step4 .
Migration Server Details.
Default Migration Server SID is LT1.
Port Number 22, 1128 , 1129 and 4237 need to opened and Telnet Should be completed Successfully.
On Migration Server (LT1). We need to install SAP AS ABAP Stub Installation.
Step5 .
These Ports need to open in Migration Server.
Port 22 is used for secure access via PuTTY (SSH).
Ports 1128 (HTTP) and 1129 (HTTPS) are utilized for SUM (Software Update Manager) execution.
Port 4237 is required for SWPM during AS ABAP Stub installation.
Step6 .
What is Migration Server?
Migration Server used to move the data from SAP ECC to SAP S/4HANA Cloud.
The system performs data transfer as part of the SUM DMO migration process.
In Migration Server Default SID is LT1.
Step7 .
Below are the team details required during the conversion process.
Infra Team—–Responsible for Build the Hardware and Operating System and File System.
Network Team–Responsible for Port opening and Firewall and DNS Configuration.
Basis Team——Responsible for Technical S/4 Conversion , S/4HANA Installation ,Upgradation , Unicode Conversion, System Refresh SID Change , Backup Configuration , PRE and Post Steps.
Security Team—–Responsible for Users, Roles and Authorization and PRE and Post Steps.
Functional Team–Responsible for Functional Conversion PRE and Post Steps.
PS Team————-Responsible for Fund Management.
Step8 .
Below is Architecture of Source and Target Server.
Step9 .
These checks help to determine the mandatory activities required before initiating the SAP S/4HANA system conversion.
System Requirement.
Maintenance Planner.
SI-Check / Readiness Check
Custom-code analysis.
Step10 .
Basis Steps.
The system must be running SAP ERP ECC 6.0 with Enhancement Package levels ranging from EHP 0 to EHP 8.
Your system must be an AS ABAP-only system. If your system is as dual-stack system, you have to split it before
doing the conversion.
Verify the current database size.
Source and target Server timings should be the same for both the database and application layers.
Ensure host file entries are updated on both source and target systems, and increase tablespaces and datafiles as required.
Verify that hardware requirements, including CPU, RAM, and file system space, are adequate and properly sized.
Execute a full System backup and create a sandbox environment by copying the latest Production System Data.
Post step in Sandbox system Like BDLS,SGEN, SMLG,SM61,RZ10.
Ensure Password Availability of all standard users.
SAP_COLLECTOR_FOR_PERFMONITOR Job should be running and Latest Data should be Sync and reflective in ST03N.
Update the DB Statistics before starting the to avoid the issue.
Complete TCI Enablement activity on Source Sandbox system.
SAP Backbone Configuration in Sandbox for Download the SAP Notes.
Upgrade SAP Host Agent and SAPOSCOL should be running.
066 and 001 Client Deletion as per SAP note 1749142.
SDBI_CLUSTER_CHECK report needs to be run.
SDBI_POOL_CHECK report needs to be run.
SDBI_CHECK_BCD_NUMBERS report needs to be run.
Check and clear inconsistencies (missing tables & indexes) reported in DB02/DBACOCKPIT.
Ensure that all add‑ons and patch levels are consistent across the entire system landscape.
Make sure there are no invalid temp tables exists in SE14.
Process the pending update records and clear obsolete update records – SM13.
Clear invalid lock entries in SM12.
Process pending queues and clear obsolete queues SMQ1, SMQ2 and transactional RFCs SM58.
Check & Update correct hostname in SMLG, RZ12, STRUSTSSO2,SM59.
“Ensure the settings are correct for installed languages and code pages via / RSCPINST report /
se38 > rscpinst > select both and check.”
Verify the current number of background processes and increase them based on hardware capacity and system workload.
Remove any unused profile or old profiles from the profile directory. RZ10
Before you start add the SAPSYSTEM ( and env. variable SAPSYSTEMNAME) parameter to the DEFAULT/INSTANCE profile of your System.
The entry should look like: SAPSYSTEM = <instance number> (if already you can skip this step.)
Run TEMSE Consistency check and make sure that there are no error messages in SP12 transaction.
Check that there are no unconfirmed Support Packages in your SAP system. SPAM
Check and configure Transport Management System – STMS . Do STMS Test in all app servers.
Delete the parameter AUTOSTART = 1, if it is set, in the start profile.
Check & Update the Profile parameters – DIR_TRANS, DIR_PUT & DIR_EPS_ROOT.
Make sure that parameter rdisp/bufrefmode has the following values in the DEFAULT.PFL (sendon,exeauto for multiple apps and sendoff, exeauto for single app).
Make sure that parameter rdisp/bufrefmode is not set in the instance profile.
Run the command “”sapcontrol -nr <instance Number> -function GetProcessList {Stop/Start/Restart}.
The output should show all in green. Else need to be corrected on all app servers.
Change parameter value rdisp/max_wprun_time to your desire value.
Configure the RFC FINBTR@<system>CLNT<client> with DDIC user if only we have the FINBASIS Component in ECC.
Delete Expired Application Logs in System.
As per this Note 3589635 latency of under 20 ms and a bandwidth exceeding 400 Mbps between Source and Target Servers. Please read this Note.
Telnet should be working from Source System to LT1 Server.
VPN Tunnel should be open from SAP to Customer Firewall system.
Time Zone Should be same from LT1 to Source system.
Creating a backup of T512W table in Every Client of system.
Check whether any third‑party components are present in the system. If third‑party components exist, analyze the system with respect to those components.
Slicense should be applied in system.
Uninstall SAP Fiori Apps and Prepare the Conversion of Authorizations & for SAP Fiori UX Enablement.
Check the current database version, kernel version, and patch level. If they do not meet the required level, upgrade them according to the target system requirements.
Check the APP and DB platforms and verify whether they are deployed on the same hardware or on different hardware.
Verify the number of application servers in the system. If only one is installed, install another APP Server to enhance system performance. (Optional)
Ensure system is Unicode (if Non Unicode you need to convert Non-Unicode to Unicode.)
Data collection Job Should be Finished.
Step11 .
Download the Simplification Database.
Open the SAP Software Download Center.
Choose Types of Software Installations & Upgrades Access downloads and search for CCMSIDB.
Choose the relevant ZIP file and choose Download Basket.
Import the Simplification Database into the System.
Step12 .
Readiness & Simplification Item Check Prerequisite.
ST-PI and ST/API components need to upgrade as per requirement to the latest version.
SPAM/SAINT patch 71 (or higher) is required. – Version Upgrade.
Implement Note Analyzer (Optional) .
Implement the current version of SAP note 1668882 to update the Note Assistant.
Implement SAP Note 3200109 or upgrade to the corresponding Support Package for Note Analyzer.
Implement 2758146 – SAP Readiness Check for SAP S/4HANA & SAP Signavio Process Insights, Discovery Edition.
Implement 2913617 – SAP Readiness Check for SAP S/4HANA.
Implement 2399707 – Simplification Item Check.
Implement 2502552 – S4TC – SAP S/4HANA Conversion & Upgrade new Simplification Item Checks.
Step13 .
Execute Readiness Check.
Before executing Readiness Check report RTCCTOOL should be in Green Status. Otherwise some Jobs will cancel.
Update Simplification Item catalog.
go to se38 and run RC_COLLECT_ANALYSIS_DATA.
Check the Target S/4 HANA Version and select mandatory check box and schedule job.
There is some FDQ and TMW related job running in system. These all jobs is IMP and should be finished.
SE38 -> and /SDF/RC_START_CHECK
All Jobs should be finished properly.
Step14 .
Launch SAP Readiness Check application.
Run this URL —> https://me.sap.com/readinesscheck/home
Click on the Start new Analysis.
Upload zip files to readiness check application.
Enter the name of the Analysis and upload the Zip file obtained from the Execution.
Open the analysis once it is ready (take couple of minutes).
Custom Code section is empty. You need to upload Custom Code zip file to get result.
Upload the zip file.
Click on the refresh and you will see Readiness Check report on Portal.
Step15 .
Run Simplification Item checks in 000 Client.
Login to 000 client.
SE38 -> /SDF/RC_START_CHECK.
Update the catalog if required.
Click on “New Relevance & Consistency Check as background job.
Click on execute.
Monitor the job from sm37.
Select the target version of S/4 HANA.
Click on “Display Last check Result”
Click on execute.
Anything under “Generic” & “Red” take action accordingly.
Rerun the consistency check once all cleanups are complete.
Step16 .
ABAPER Steps.
Custom Code Correction (ATC)-Setup
Central Check System should be on or above Basis release 7.52
Need to check how many SPDDs are in the current system.
Step17 .
SD/MM Steps.
Customer Vendor Integration (CVI) Steps
Mandatory Conversion of Customers/Vendors to Business Partners.
For the CVI implementation, it is required to identify and implement all CVI‑related SAP Notes.
CVI Must implemented in System before doing SI-Check. Otherwise report will not come proper.
Step18 .
Security Steps.
Landscape & Access Review.
Identify all systems (DEV, QAS, PRD, Sandbox).
Validate security access to: SU01,PFCG,SU24,SU25 and SAP_ALL.
Ensure Basis & Security admin roles are updated.
Step19 .
User Cleanup.
Lock/delete inactive users (last login > 90 days).
Remove SAP_ALL / SAP_NEW from dialog users.
Validate service, batch, RFC users.
Step20 .
Role Cleanup.
Remove obsolete roles.
Identify unused roles (via SUIM / AGR_USAGE).
Remove composite role redundancies.
The Security Team’s role is important, as they are responsible for verifying which transaction codes and authorizations are assigned to source system users.
Analyze Current Roles: Evaluate existing roles (single, composite, derived) using SUIM to identify active vs. dormant roles.
It is required to review and validate the transaction codes and authorizations in the source system.
Step21 .
FI Steps.
Finance Preparations: Run inconsistency Report , SI Analysis , Delta configuration
Prepare system for S/4HANA-specific settings (e.g., New GL, Asset Accounting).
Step22 .
Maintenance Planner (Basis Steps)
Generate the Latest xml file from SPAM and Upload in Maintenance Planner.
The system must be correctly maintained in the SAP Product License. Otherwise, errors may occur while creating the stack file in Maintenance Planner.
Check the third-Party add-on’s and business functions and generate the Stack XML. Carefully create Stack file because your Conversation depends on this Stack file.
Step23 .
Operating System Step / File system requirement (Infra Steps.)
Validate Operating System Compatibility.
Update the SAP Host Agent to the latest version.
Migration Key Generate 317096 – Migration Key Generation for ABAP Systems.
Provide minimum 25GB under DIR_EXE.
Make sure scp command should be work properly to Transfer the file from Source to Target system. ( DMO with system move).
Create /media file system with enough Space.
Save the sidadm environment variables before starting the S/4 conversion.
Provide minimum 100GB of free space in /usr/sap/trans.
Add Hostfile entry and Server should be ping with IP and Hostname and Ping between from Source and Target Server.
Nslookup should be work properly
DNS Should be Configure Properly in Servers (Network Step.)
Step24 .
Database Specific Requirements (Basis Steps.)
Run DB statistics for all the tables and Dictionary.
“Database User Password validity check (SYSTEM and SAPSR3 and Schema).
Make sure that your database password will not expire during the migration process.”
Make sure that there is no schema/user mismatch of your SAP ABAP system. Please proceed as described in note 1086375 to repair this mismatch. If your DB is SQL.
Step25 .
Migration Server Step. (LT1)
22, 1128 , 1129 and 4237 Port need to opened and Telnet Should be completed Successfully. (Network Team.).
On Migration Server we need to install SAP AS ABAP Stub Installation.
Telnet should be working from LT1 Server to Source system.
Step26 . Target Host S/4HANA App and Database Server Steps.
Target Servers Should be ready. S/4 Hana Vanilla Installation and Database Installation on Target.
Target Tenant DB System User Password must be available.
Target DB SYSTEMDB SYSTEM User Password must be available.
Target DB Schema Password must be available.
Target DB DBACOCKPIT User Password must be available.
Import DU HANAUMML128-70001054.ZIP on the target DB as per the on‑screen instructions. SAP Notes 2928582.
Target DB log_mode Parameter value should be overwrite in System and Tenant DB.
Step27 .
SUM Specific Requirements on Source and Target Server.
1128 and 1129 Port need to opened and Telnet Should be completed Successfully.
Create sapmedia File System with minimum 200 GB Space.
Keep all the Software in sapmedia File System.
Provide 777 Permission of sapmedia File System.
Take Full DB Backup and VM Snapshot of System before start the SUM. (VM Snapshot Backup is Optional)
Uncar the SUM.
Register the SUM.
Before starting SUM, run the SI Check report once again. The result must be Green.
If any errors appear in the SI Check report, do not launch SUM—first analyze and fix the errors.
Only proceed with SUM after the SI Check report is completely clean and Green.”
Launch the SUM with SIDADM User.
Provide the Stack file in SUM.
Provide Migration Key.
DDIC of 000 and Password must be available.
You can choose here which Scenario you want to go DMO with System move.
Kindly follow and monitor the standard SUM screen for ongoing status and updates.
Conclusion:
SAP ECC to S/4HANA Conversion Checklist.
The SAP ECC to S/4HANA conversion is a very difficult that requires strong planning and system readiness.
This checklist highlights all the steps that need to be completed before starting the S/4HANA conversion.
Thanks.
#abap