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/db6 as below:
Please find other blogs as follows at S/4HANA SQUARE ONE
S/4HANA SQUARE ONE
|NEW INSTALLATION||PART1 – MP||PART2 – Installation
||PART3 – BP Activation
||PART4 – Fiori Activation||PART5 – DATA MIGRATION|
|S/4HANA 1909||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0||fps0|
|S/4HANA 1809||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0|
||fps2 fps1 fps0||fps2 fps1 fps0||fps2 fps1 fps0|
|SYSTEM CONVERSION||t2 – RC||t3 – MP||t4 – SIC
||t5 – CCM||t6 – SUM|
|SAP S/4HANA ON-PREM APPLIANCE||INSTALL USING MEDIA||ACTIVATE FROM CAL|
|S/4HANA 1909||link custom link standard||link|
|SAP S/4HANA CERTIFICATION|
|S/4HANA Certification Exams through SAP Certification Hub||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/EHP6/db6
STEP 1: SOURCE – OPERATING SYSTEM
You can use PAM tool – Product Availability Matrix to determine if OS meets the requirement prior to system conversion.
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
STEP 2: SOURCE – UPGRADE DATABASE
Upgrade database to DB6 version 10.5 FP8 or higher.
Please note DB6 versions 10.5.0000 to 10.5.0003 are not supported.
as per 2644872 – Database Migration Option (DMO) of SUM 2.0 SP04
Refer 101809 – DB6: Supported Db2 Versions and Fix Pack Levels
For End of Support Dates of IBM Db2 LUW, please refer SAP Note 1168456 – DB6: Support Process and End of Support Dates for IBM Db2 LUW
Please check current version of above notes.
STEP 3: SOURCE – CONVERSION USING DMO
Please note that in this blog we are covering scenario of DMO with System Move as shown below. The scenario of DMO with System move is used when you move from one host to another for hardware change, TDI or VM within same data canter. It is also used to move from one data center to another or from On-Prem to Cloud (IAAS). This scenario requires New installation of S/4HANA on target prior to SUM.
This option allows to switch database host only, while keeping the same application server host. It requires HANA DB install on Target host prior to starting SUM tool.Please extract DMO tool as below 2 commands:
as e6dadm cd /usr/sap/E6D SAPCAR -xvf /sapmedia/download/SUM20SP03_1-80002456.SAR as root ps –ef | grep –i sapup /usr/sap/E6D/SUM/abap/SUMSTART confighostagent
TIP: Please check that your /windows/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:
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 e6dadm/(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 email@example.com with password, recipient email like firstname.lastname@example.org or SMS text like email@example.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 for more info.
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”
SUM will check all the SAR files in the download folder.
At (0%) Current Phase PREP_PRE_CHECK/PROFREAD
enter password of DDIC in client 000,
enter password of DB user SYSTEM and Click on Next
At (1%) Current Phase PREP_INPUT/MIG2NDDB_INI enter the Migration Key, select options and click on Next
TIP: if you get error above, first apply support packs using Maintenance Planner option Plan a Minimum Software Change. After applying support packs you have to download new stack.xml in Maintenance Planner.
At (2%) Current Phase PREP_INIT/INIT_CNTRANS_PRE correct the inconsistencies and click on NextAt (2%) Current Phase PREP_INIT/DBCHK_INI select values and click on Next
Click on Next
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 Next
Apply 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/E6D/SUM/abap/log/S4_SIF_TRANSITION_CHECKS.E6D.
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
ERROR: Got error – A2EESUPG_STRESS 111 Report “RSUPG_STRESS4UPGRADE” with action “START” finished with error
RESOLUTION: vi /usr/sap/E6D/SUM/abap/bin/SAPup.par /fa/stress_maker = OFF then continued SUM. For sandbox this is ok but for production landscape please fix/open OSS message.
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
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
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 vhcalabaci 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
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
Start DMO. SUM will detect that there is hostname change and will continue as below:
TIP: Target hostname has to be different – DMO does not support having the same host name for source and target.
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 E6D_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
TIP: Please note that for the default installation of S/4HANA 1809 FPS1 is with restore database method and is installed with schema SYSTEMDB. You may want to change this to install using different schema name.
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
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.
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
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
|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)
|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|
Your system installation is complete. Congratulations !!!
Product Expert – S/4HANA