Skip to Content
Technical Articles

Conversion to S/4HANA 1809FPS0 – t6m – Software Update Manager from EHP6/mss

The blog is for conversion of source system ERP6/EHP6 to target system S/4HANA 1809FPS0/FPS1 showing the Realize Phase – t5- SUM from EHP6/mss as below:

Please find other blogs as follows:

S/4HANA  SQUARE  ONE

NEW INSTALLATION        PART1 – MP PART2 –  Installation
PART3 –  BP Activation
PART4 – Fiori Activation
S/4HANA 1809 fps1  fps0 fps1  fps0 fps1  fps0 fps1  fps0
S/4HANA 1709
fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0
S/4HANA 1610
fps2  fps0 fps2  fps0 fps2  fps1  fps0
S/4HANA 1511 fps2  fps1
S/4HANA UPGRADE   t2 – MP t3 – SIC
t4 – CCM t5 – SUM
S/4HANA 1809 link link link link
SYSTEM CONVERSION t2 –  RC t3 – MP t4 – SIC
t5 – CCM t6 – SUM 
S/4HANA 1809 link link link link EHP7/hdb
EHP6/db6
EHP5/ora
EHP6/mss
S/4HANA 1610 FPS0 link link link
S/4HANA ON-PREM APPLIANCE INSTALL USING MEDIA ACTIVATE FROM CAL
S/4HANA 1709 FPS1 link link
S/4HANA CLOUD      CPM  MASTER  CONTENT   EMAIL
OUTPUT MANAGEMENT link  link  link link

DISCLAIMER: The purpose of this blog is to provide guidance to fast track your SANDBOX conversion. Tool parameters are for shortest overall run time with maximum downtime. The author will not take over any responsibility of the consequences this may cause. Please use the blog for sequence of the process after going through the latest GUIDES.

The Source System is ECC6/EHP5/mss at below Support pack level:
TIP: If you get error in phase PREP_INPUT_CHECK/SUMCHK! – Source release 731 SP 0 needs at least SP 1 for update scenarios with target ‘753’. The 1809 Release Note 2625407 states that min in NW for EHP3 is EHP3 for SAP NetWeaver 7.0 SP01.

Also note that you will have to create stack.xml after the stack level has been upgraded to the min level.


Please note OS is Windows 2012R2

STEP 1: SOURCE – OPERATING SYSTEM

You can use PAM tool – Product Availability Matrix to determine if OS meets the requirement prior to system conversion.

Alternatively you can do this using the SUM/DMO tool with precheck option as below to quickly arrive at the OS  https://vhcalabaci:1129/lmsl/chktool/E6M/doc/sluigui

Please refer note below for recommended Application Server Platforms:
2620910 – SAP S/4HANA 1511, 1610, 1709 and SAP BW/4HANA 1.0: Recommended Application Server Platforms

TIP: For S/4HANA 1809 FPS1 conversion, customers had to upgrade Operating system from Windows 2012 to Windows 2016, and even though the source system will be decommissioned. This is because the client of HANA 2.0 db needs Windows 2016.

STEP 2: SOURCE – UPGRADE DATABASE

Upgrade database to MS SQL 2012 or higher.
as per Note 2644872 – Database Migration Option (DMO) of SUM 2.0 SP04

Please find Note 1177356 – MS SQL Server: End of Support for SAP Releases
Note 62988 – Service packs for MS SQL Server

1651862 – Release planning for Microsoft SQL Server 2012       <== min SAP Netweaver SPs
1676665 – Setting up Microsoft SQL Server 2012                        <== min SAP Kernel Levels
1684545 – SAP Installation Media and SQL4SAP for SQL Server 2012

Upgrade Guide
Upgrade to and Installation of SQL Server 2012 in an SAP Environment
Upgrading SQL Server Failover Cluster to SQL Server 2012 Failover Cluster

If your SQL Server release is SQL Server 2008 R2, make sure that you apply SP1 to the system before you upgrade to SQL Server2012. Please find the key screenshots of the upgrade process from SQL Server 2008R2 to SQL Server 2012R2.

Stop SAP and then run setup.exe as administrator


Run SWPM to finalize SQL Server upgrade. Use SWPM10SP24_-20009707.SAR or later.
Ref SAP Note 683447 – SAP Tools for MS SQL Server The tool performs post-upgrade steps automatically.

Start SAP system

Connect with dba login to SQL Server 2012 Management Studio. Open Query window and run commands while SAP system is online:

use E6M
go
EXEC sp_updatestats
go

use master
go
alter database E6M SET PAGE_VERIFY CHECKSUM;
go

Set the configuration for the SQL Server Agent.

STEP 3: SOURCE – CONVERSION USING DMO

Please extract DMO tool as below 2 commands:

Login as e6madm in Powershell Run As Administrator execute:

cd E:\usr\sap\E6M
sapcar -xvf E:\sapmedia\download\SUM20SP03_1-80002483.SAR
cd E:\usr\sap\E6M\SUM\abap
.\SUMSTART.BAT confighostagent

TIP: Please check that your c:\windows\system32\drivers\etc\host file contains entry with IP address mapped to hostname vhcalabaci. c:\users\mahesh>type c:\windows\system32\drivers\etc\hosts 10.20.130.140  vhcalabaci vhcalabaci.dummy.nodomain vhcalabacs vhcalabacs.dummy.nodomain

Open Google Chrome browser (latest version recommended) Enter URL:
https://vhcalabaci:1129/lmsl/sumabap/E6M/doc/sluigui

In case you get screen below please click on Advanced and then “Proceed to vhcalabaci(unsafe)

TIP: If you get message that Page is Unresponsive just click on Wait.

Enter e6madm/(password you used before) in the screen below

TIP: SUM MailNotifier can be used to get notified by eMail/SMS when SUM displays a dialog so you don’t have to frequently check it for long running phases. It can be configured at PREPROCESSING PHASE later when you have a break. You need a sender email account like summan@gmail.com with password, recipient email like john.doe@digiwatch.com or SMS text like 5551234567@vtext.com After this you execute command as root:
vhcals4hci:~ # java -jar MailNotifierApp.jar properties=MailNotifierApp.props  I had to add parameter mail.smtp.starttls.enable=true to the above command for gmail account.  Also I had to login to gmail account and then execute link to allow less secure apps. Refer Boris Rubarth’s blog at end of this blog for more info.

EXTRACTION PHASE

TIP: If you get error manifest signature revoked download latest crlbag.p7s. Do not use old downloaded file crlbag.p7s. Refer SAP Note 2491577 – SUM fails at phase PREP_EXTRACT/SCAN_DOWNLOADDIR with error message “SIGNATURE: manifest signature is revoked”

At 0%) Current Phase PREP_EXTRACT/SCAN_DOWNLOADDIR  enter the Download Directory E:\sapmedia\download and click on Next

SUM will check all the SAR files in the download folder.


At (0%) Current Phase PREP_INPUT/CONFCHK_IMP the tool checks database version, This is deliberately created to show where the check occurs. Upgrade DB.

At (0%) Current Phase PREP_PRE_CHECK/PROFREAD
enter password of DDIC in client 000,
enter password of SAPServiceE6M,
enter password of DB user SYSTEM and   Click on Next


Note: 317096 – Migration Key Generation for ABAP Systems

Note: 1899381 – How to check Migration Key issues – System Copy

At (1%) Current Phase PREP_INPUT/MIG2NDDB_INI  enter the Migration Key, select options and click on NextAt (2%) Current Phase PREP_INIT/DBCHK_INI select values and click on Next

Click on Next

CONFIGURATION PHASE

At (5%) Current Phase PREP_CONFIGURATIN/INITSUBST click on Next

At (5%) Current Phase PREP_CONFIGURATIN/INITSUBST select/enter values and click on Next

At (8%) Current Phase PREP_CONFIGURATION/LANG_SELECT the tool will look for archives as per stack.xml and show if any of them is missing. click on NextApply Missing Notes,

TIP: After applying transports in tCode SE01 ensure you release the pending transports

and Click on Next

At (9%) Current Phase PREP_EXTENSION/IS_INST click on Next

At (9%) Current Phase PREP_EXTENSION/SELSTACKXML_READ click on Next

At (10%) Current Phase PREP_EXTENSION/BIND_PATCH click on Next

At (10%) Current Phase PREP_EXTENSION/BIND_PATCH click on Next

During further processing , among other items , SUM tool will run SI Check at PREP_EXTENSION/RUN_S4H_SIF_CHECK_INIT and will take same amount of time as job RC_NEW_CHECK_IN_JOB run manually at t3 – SI Check.

If the Simplification Item Check inconsistencies are not resolved you get above error. More details are found in file /usr/sap/E5O/SUM/abap/log/S4_SIF_TRANSITION_CHECKS.E5O.

One of the items is as per Simplification Item List, Check the note applicable is 1484142 – MRN1: Incorrect Customizing entries deleted As per the note, run report S4SIC_TNIW5CORR in client 000 once.Once you have fixed inconsistencies as shown in SI-Check, please rerun the job and check Results  and confirm to  continue…

At (11%) Current Phase PREP_INTEGRATION/ADJUSTPRP click on Next

At (12%) Current Phase PREP_INSTALL/INITSHD enter SHADOW DB USER PASSWORD and click on Next

At (12%) Current Phase PREP_INSTALL/SHDINST_CPY select No to use profiles click on Next

CHECKS PHASE

At (15%) Current Phase PREP_GENCHECKS/SPAU_FILL_LEVEL_DEC please confirm all obsolete notes, and reset all non-adjusted objects with active SAP-version to SAP-Standard and click on Next

At (15%) Current Phase PREP_PREPROC/SAVE_VAR_CHK select No to Read Note 1696821 carefully. Do you want to run the JOB_RASUVAR(2) ? click on Next

Click on Next

PREPROCESSING PHASE

At (17%) Current Phase MAIN_INIT/RUN_RSBO230 – resolve updates in SM13 as per Note 1705774

At (17%) Current Phase MAIN_INIT/LOCKEU_PRE – Lock the development environment now click on Next

TIP: From this point the resource consumption is high.

At (31%) Current Phase MAIN_SHDRUN/ACT_UPG shows modified objects that you need to adjust, follow the steps to adjust repository:and click on Next

TIP: From this point SUM continues to process and there is a long break. You could start preparing the Target host as per steps 3 , 4 and 5

At (55%) Current Phase MAIN_SHDIMP/REQ_PARTITIONING_MATDOC please partition MATDOC table as per Note 2259038 if needed and click on Next

At this point you need to transfer the content of SUM to target host.

TIP: if the target hostname is same, SUM cannot determine, whether it is running on the source or the target host. Having the same host name for source and target is not supported.

At (55%) Current Phase MAIN_MIGSERIALSETUP/HOSTCHANGE_MOVE enter TARGET HOSTNAME vhcals4hci and click on Next


At (60%) Current Phase MAIN_DTTRANSSHD/DOWNCONF_DTTRANS accept selected radio button Actions completed click on Next

At (61%) Current Phase MAIN_DTTRANSSHD/DOWNCONF_DTTRANS_BCK accept selected radio button Backup completed click on Next

At (61%) Current Phase MAIN_BRISETUP/RUN_RSVBCHCK_BRI_SETUP click on Next

EXECUTION PHASE

At (61%) Current Phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/SUBMOD_MIG_DOWNTIME_EXP/EU_CLONE_MIG_DT_EXP click on Next

At (67%) Current Phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/HOSTCHANGE_STOP click on Next

At (100%) Current Phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW/SUBMOD_MIG_SER_IMP/SETEXECSTAT_UTMIG_SERIAL click on Next

=====SWITCH TO TARGET HOST======

STEP 4: TARGET – PREPARE TARGET SYSTEM

Please prepare target system as per blog in New Installation of S/4HANA 1809 FPS0 – Part 2 – Installation

STEP 1: OPERATING SYSTEM
STEP 2: NEW HANA DATABASE (OPTION 2)
STEP 3: S/4HANA INSTALLATION USING SWPM

TIP: In step 3 or the blog, it is not necessary to create a stack file in Maintenace planner and install addon using STEP 4: ADDON INSTALLATION USING SUM, just the base install of S/4HANA 1809 is enough as the schema content will be replaced by DMO tool.

You can download media from Software Downloads => INSTALLATION AND UPGRADES => SAP S/4HANA 1809 => INSTALLATION => S4CORE103_INST_EXPORT_*.zip

Download media from Software Downloads => SUPPORT PACKAGES AND PATCHES => SAP HANA PLATFORM EDITION => SAP HANA CLIENT 2.0
HANA Client IMDB_CLIENT20_003*.SAR

Download kernel files:
SAPEXEDB_28-80003385.SAR – Kernel Part II (773)
SAPEXE_28-80003386.SAR      – Kernel Part I (773)
SAPHOSTAGENT41_41-20009394.SAR – SAP HOST AGENT 7.21 SP41
igsexe_7-80003187.sar – SAP IGS integrated in SAP Kernel
igshelper_17-10010245.sar – SAP IGS Fonts and Textures

Install using command below:

./sapinst SAPINST_USE_HOSTNAME=vhcals4hci  SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false

STEP 5: TARGET – CONTINUE DMO

First copy the entire SUM directory structure from Source to Target, doesn’t matter the platform.

Since SUM is copied from Windows platform to Linux, there is an additional step to be done. After copying all the files, extract the SUM SAR file of the Linux platform over the source files. The same is applicable if you move SUM files other than Linux as source so linux files overlay the Source platform files.

vhcals4hci:e6madm > cd /usr/sap/E6M
vhcals4hci:e6madm > SAPCAR -xvf /sapmedia/download/SUM20SP04_0-80002456.SAR

Check that entire filesystem under SUM is owned by e6madm:sapsys

Upgrade hostagent to latest:

vhcals4hci:# /usr/sap/hostctrl/exe/saphostexec -upgrade -archive /usr/sap/DMS/SAPHOSTAGENT190_190-20005731.SAR

TIP: Target hostname has to be different – DMO does not support having the same host name for source and target.  Check that command hostname gives the target hostname which has to be different form source. SUM does not use virtual hostname.

Start DMO. SUM will detect that there is hostname change and will continue:

At (55%) Current Phase MAIN_MIGSERIALSETUP/HOSTCHAGE_MOVE click on Next

Enter Host name as vhcals4hci and Instance number as 00 and click on Next
Enter INSTANCE PROFILE as E6M_D00_vhcals4hci and click on Next
Enter Target DB hostname, Target DB SID, Target DB instance number, Target System License and click on Next
Enter SYSTEM password and click on Next
Enter SYSTEMDB password and click on Next

At (55%) Current Phase MAIN_MIGSERIALSETUP/HOSTCHAGE_MOVE select Use existing tenant and click on Next
Enter Target DB SCHEMA SAPABAP1 and click on Next

At (55%) Current Phase MAIN_MIGSERIALSETUP/HOSTCHAGE_MOVE enter download directory and click on Next

At (55%) Current Phase MAIN_MIGSERIALSETUP/SUBMOD_MIG_CONFIG/HDB_MIGCONFIG refer Note 1899817 to decide  and  click on Next

At (55%) Current Phase MAIN_MIGSERIALSETUP/SUBMOD_MIG_CONFIG/HDB_PREPARE enter SCHEMA password and click on Next

Click on Next


At (55%) Current Phase MAIN_MIGOPT/SUBMOD_MIG_CRR_CONFIGURE/SHDINST_CRE_CRR please check file CHECKS.TXT and click on Next

EXECUTION PHASE


At (68%) Current Phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_NEW/SUBMOD_MIG_SER_IMP/EU_CLONE_MIG_DT_IMP select option and click  on Next

At (89%) Current Phase MAIN_UPTRANS/STARTSAP_PUPG there is issue with system start.

TIP: Ref Note 2312315 – SUM fails to start an instance in phase MAIN_UPTRANS/STARTUP_PUPG – INTERNAL Resolve the issue after checking profiles and then start

At (89%) Current Phase MAIN_UPTRANS/UPCONF click on Next

At (89%) Current Phase MAIN_UPTRANS/SETUPGPAR_UPG_POST click on Next

POSTPROCESSING PHASE

At (91%) Current Phase MAIN_POSTPROC/SUBMOD_SPAU_INFO/SPAUINFO 

Login client 000 and Adjust
Go back to SUM and click on Next


At (95%) Current Phase MAIN_POSTPROC/REQUPFINAL click on Next

SUM is completed. Please login to the system and check the Installed product version as:Please find Installed Software Component version:

You can schedule complete SGEN if it is not been scheduled.

STEP 6: S/4HANA RELEASE INFORMATION NOTE

Please apply the 4 notes below to the installed instance as per SAP Note 2659828 – SAP S/4HANA 1809 Feature Package Stack 00: Additional Release Information these notes are only for 1809 FPS0

NOTE DESCRIPTION MANUAL
2658745 Register internal scenarios (FINCF_AV_SO,FINCF_AV_CI)1880321990 No
2660883 BP_EOP: Success Message is not displayed properly No
2661055 NS Registration /CMMFD (1880344774) No
2666655 Undo changes of central BUPA search help exit No
2441447 Authorization check enablement in Business Partner F4 search help
(Seems like the note is already applied)
Yes
2653874 Client copy fails in exit 0SFW_CC_SYNCH_SWITCH_STATES_ADD No
2653909 BRF+: Performance improvement while opening Ruleset No
2656251 Performance and memory improvements for cl_ci_test_no_order_by No
2658952 ESH – initial authorization index filling – error: “Feature not supported”/OLAP VIEW on HANA 3.1 No
2662538 Dump occurs on changing the query No
2665431 Cursor Position is not correctly being displayed after selecting the record in SM30 No
2656623 Delivered version of AO Workbook (AAOE) is not created in the content system No
2694011 WTY: Dump “CALL_FUNCTION_CONFLICT_LENG” occurs on account document posting No
2697405 TrexViaDbsl: wrong schema name is set to temporary objects in TREX_EXT_AGGREGATE Yes
2722552 Runtime error SYSTEM_DATA_ALREADY_FREE during update of classifications No
2724147 Termination in the update of the classification No
2726975 Support of CLSD in SNOTE: Ignore all Changed by and Changed on data in the CI No

REFERENCES:

OS:

Updating SAP ABAP System on Windows: SAP HANA DB – SUM 2.0 SP04             <==pdf
Updating SAP ABAP Systems on UNIX and Linux: SAP HANA DB – SUM 2.0 SP04 <==pdf

DB:

2378962 – SAP HANA 2.0 Revision and Maintenance Strategy
https://help.sap.com/hana20_rev_strat/SAP_HANA_20_Revision_Strategy.pdf <==pdf

TOOL:

Converting SAP Systems to S/4HANA Using Software Update Manager 2.0   <==pdf
SUM 2.0 Guide

S/4HANA 1809 FPS0 Conversion Guide         <==pdf
S/4HANA 1809 FPS1 Conversion Guide         <==pdf
DMO Guide      <==pdf

Your system installation is complete. Congratulations !!!

Mahesh Sardesai
Product Expert – S/4HANA

10 Comments
You must be Logged on to comment or reply to a post.
  • Hi Mahesh,

    Happy New Year!

     

    Thanks for the step by step guide! I have a question regarding Phase MAIN_SWITCH/SUBMOD_MIG_SWITCH_ORG/HOSTCHANGE_STOP

    At this stage..

    Can I still continue to use my existing ASCS instead of going for a new host ?? Or do I need to reset the upgrade and start again by de-selecting /disabling option migration with system move?

    Thanks for your input

     

     

    •  

      Hi Vidyut,

      The target hostname has to be different as I mentioned. DMO does not support having the same host name for source and target. 

       

      • Hi Mahesh,

        Thats right, however I restarted the SUM and removed the tick – (Enable migration with system move) and could proceed on the same host.

        Finally, as expected Database was migrated to HDB and app remained on same host.

         

        Thanks a lot again for detailed steps!

         

        Best Regards,

        Vidyut Kichambare

  • Hello Mahesh,

    First, thank you for the blog. I think is a great job and very useful for the ones that are taking the first steps with S/4, or the ones just keep learning the new versions.  Just wanted to add a comment because i think it could help others.

    I´ve Just finished a conversion from ehp7/oracle to S/4 1809. I didn´t use the move instance option, as i decided to install the instances with SWPM. I installed ASCS without problem, but when installing PAS, it doesn´t allow to change the schema name were the s/4 is installed.I found note (2568783 – Release Note for Software Provisioning Manager 2.0) that states that in swpm 2.0 The ABAP database schema is named SAPHANADB and this name cannot be changed. After SUM upgrade to S/4 1809 the schema is SAPABAP1 in the Hana DB, so i´m not able to install the PAS in a new host.  I think it could be useful to add a note in the blog to advise that the new schema name should be SAPHANADB to avoid problems with swpm.

    An added problem is that the only option to copy S/4 1809 systems is the backup/restore method (R3load method seems not to be available), so copy the system to another schema is not an option, and rename of SAPABAP1 schema is not to supported (2362492 – How to rename a user schema in SAP HANA).

     

    • Hi Carlos Castrol,

      When you install the new target instance the schema is SAPHANADB since the new method for a new install, is Restore from backup which has a fixed schema.

      After move to target, you can choose to define the new schema as SAPABAP1 or any other name like SAPPRD. at the below prompts

      At (55%) Current Phase MAIN_MIGSERIALSETUP/HOSTCHAGE_MOVE select Use existing tenant and click on Next
      Enter Target DB SCHEMA SAPABAP1 and click on Next

  • Hi Mahesh,

    thank you for this blog. You say that “For S/4HANA 1809 FPS1 conversion, customers had to upgrade the source Operating system from Windows 2012 to Windows 2016”. Is this true even if you want to move the ASCS instance towards a Windows 2016 system ?

    Thank you in advance and best regards,

    Nicola

     

    • Hi Nicola,

      Please use the SUM check tool to find out if you need the OS. It takes few minutes to check if you have tool setup. 
      https://vhcalabaci:1129/lmsl/chktool/E6M/doc/sluigui

      If you have ASCS on Windows 2016 it should be sufficient I think, let us know what was the result. In the scenario I mentioned the db and ascs was on Windows 2012.

      • Mahesh
  • Thank you Mahesh. I do not have tool setup. I am just studying the prerequisites for converting a system which is very similar to what you describe in your blog. I have everything (ascs and ASE db) on one windows 2012 system.

    Nicola