Skip to Content
Technical Articles

New Installation of S/4HANA 1909 FPS0 – Part 2 – Installation

This blog includes installation of S/4HANA 1909 FPS0 and will focus on creating Sandbox type instance with co-deployed (embedded) gateway.

Please find other blogs as follows:

S/4HANA  SQUARE  ONE

NEW INSTALLATION        PART1 – MP PART2 –  Installation
PART3 –  BP Activation
PART4 – Fiori Activation
S/4HANA 1909 fps0 fps0 fps0 fps0
S/4HANA 1809 fps2  fps1  fps0 fps2  fps1  fps0 fps2  fps1  fps0 fps2  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 rc2  rc1 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

STEP 1: OPERATING SYSTEM

It is recommended to install minimum SuSE Linux version 12 SP3 as per Note 2235581 – SAP HANA: Supported Operating Systems.
TIP: Please refer other Notes below:
Note 2399995 – Hardware requirement for SAP HANA 2.0
Note 2620910 – SAP S/4HANA 1511, 1610, 1709 and SAP BW/4HANA 1.0: Recommended Application Server Platforms
Note 2205917 – SAP HANA DB: Recommended OS settings for SLES 12

You can check your operating system version as below:

sid-hdb-s4h:~ # cat /etc/SuSE-release
  SuSE-release SUSE Linux Enterprise Server 12 (x86_64)
  VERSION = 12
  PATCHLEVEL = 3

STEP 2: USE EXISTING HANA DATABASE (OPTION1)

The minimum required is HANA 2.0 Support Package 04 Revision 42 but it is generally recommended to go to the highest revision available. For choosing the release please refer Note 2655761 – Restrictions & recommendations regarding specific revisions of SAP HANA database for use in SAP S/4HANA and Note 2469025 – How-To: Upgrading to SAP HANA 2.0 and also Note 2842859 – Possible Persistence Inconsistencies With SAP HANA 2 SPS04 Revisions 040.00 to 042.00

If you already have a database, please patch the database to HANA 2 and you can create container using command:

CREATE DATABASE HDB SYSTEM USER PASSWORD Xxxxxxxn

It takes about 2 minutes to create database with this command.

STEP 2: NEW HANA DATABASE (OPTION 2)

Please refer notes:
Note 2813364 – SAP HANA 2.0 SPS 04 Database Revision 042
Note 2423367 – Multitenant database containers will become the standard and only operation mode
Note 2842859 – Possible Persistence Inconsistencies With SAP HANA 2 SPS04 Revisions 040.00 to 042.00

Please do not select HANA 2.0 SPS2 rev 42

To install database you can use hdblcmgui. I used hdblcm as below.
minimum is HANA 2 Rev 43 as per 2804060 – SAP S/4HANA 1909 Feature Package Stack 00: Additional Release Information

First unpack the archive to folder HANA2_43 and LCAPPS_43 together if you need integrated LiveCache so it can be installed as a combined install.

sid-hdb:/sapmedia/ #SAPCAR -xvf IMDB_SERVER20_043_0-80002031.SAR
sid-hdb:/sapmedia/ #mv SAP_HANA_DATABASE HANA2_43
sid-hdb:/sapmedia/ #SAPCAR –xvf IMDB_LCAPPS_2043_0-20010426.SAR
sid-hdb:/sapmedia/ #mv SAP_HANA_LCAPPS HANA2_43_LCAPPS
sid-hdb:/sapmedia/HANA2_36 # ./hdblcm


...............
Updating SAP HANA Database Instance Integration on Local Host...
Creating Component List...
SAP HANA Database System installed
You can send feedback to SAP with this form: https://localhost:1129/lmsl/HDBLCM/HDB/feedback/feedback.html
Log file written to '/var/tmp/hdb_HDB_hdblcm_install_2019-08-17_00.12.36/hdblcm.log' on host 'sid-hdb-s4h'.

After installation, logon to HANA Database using HANA Studio and add system
Host Name : <your hostname or ip>
Instance Number: 02
Click Next and in the following screen enter User Name SYSTEM and Password
Click on Finish to exit.

Please refer Note 2600030 – Parameter Recommendations in SAP HANA Environments for parameter recommendations. This note contains check scripts which detect SAP HANA version, SAP product installed, etc. and give specific parameter recommendations.

Also refer Note 2469025 – How-To: Upgrading to SAP HANA 2.0

TIP: Please change the log mode if you don’t want to be spend time on log maintenance: 
In HANA studio –> Configuration –> global.ini –> persistence and set the parameter log_mode to overwrite. 
When you change the log mode, you must restart the database system to activate the changes. 
It is also recommended that you perform a full data backup. You can also set the log_mode to ‘overwrite’ 
using the following SQL-Statement:
ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('persistence', 'log_mode') = 'overwrite' WITH RECONFIGURE;

STEP 3: S/4HANA INSTALLATION USING SWPM

TIP: You don’t need to extract the backup zip files S4CORE103_INST_EXPORT_*.zip. SWPM tool will extract them into /usr/sap/HDB/HDB02/backup/data/DB_HDB where the extract will use 80GB from this folder. Also this procedure is for SWPM+SUM combined installation and you don’t need the SYSTEM/DDIC password from backup Database/ABAP instance.

Extract the SWPM SAR file as below

sid-hdb:/ # cd /install 
sid-hdb:/install # /sapmedia/SAPCAR -xvf /sapmedia/download/SWPM20SP04_1-80003424.SAR

You should get message at the end of this that SAPCAR: … files(s) extracted

Start x-Windows software such as Exceed or X-ming and set the DISPLAY variable needed to confirm x-Windows is working.

Execute SWPM to do system copy with backup restore as below:

sid-hdb:/install#./sapinst SAPINST_USE_HOSTNAME=vhcals4hci SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false SAPINST_STACK_XML=/sapmedia/download/MP_Stack_1000543815_20190921_.xml

TIP: At this point if you get the screen below: Please refer Note 2510478 Data unit /xx/xx/xx/SWPM is not signed with an official SAP signature. I started with command:
./sapinst SAPINST_USE_HOSTNAME=vhcals4hci SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false SAPINST_STACK_XML=/sapmedia/download/MP_Stack_2000760120_20190920_.xml
This is ok for sandbox.

I am showing only the important screens as most are self explanatory. Select Standard System from path below:

Click on Next

At the screen Software Integrity click on Next

TIP1: If you select Typical at next parameter, those skipped are shown in Strikethrough. 
Skipping these parameters will save some time and you may be able to change them in the final Parameter Summary.
If you need integrated web dispatcher please select Custom.

TIP2: To take less time for installation I have copied the kernel files into a subdirectory of download so that it takes less time to scan and search for media.

At the screen Parameter Settings select Custom and click on Next

At the screen General SAP System Parameters enter SAP System ID (SAPSID) S4H SAP Mount Directory /sapmnt

At the screen DNS Domain Name (strikethrough font means skipped for Typical) set FQDN for SAP system checked, DNS Domain Name for SAP System dummy.nodomain click on Next

At the screen Master Password specify Master password and confirm password Xxxxxxxn click on Next

At the screen Operating System Users accept master password or enter password Xxxxxxxn

At the screen Database for SAP System enter details
Database Host   vhcalhdbdb
Instance Number   02
Database ID (DBSID)HDB
Password of DBA  Xxxxxxxn  click on Next

At the screen SAP HANA Multitenant Database Containers enter password for HANA Database superuser Xxxxxxxn click on Next

At the screen Software Package Browser enter path for the downloaded media from Maintenance Planner. Package Path: /sapmedia/download click Next
The status will change from “still missing” to “Available”. Click on Next

At the screen Upgrade SAP Host Agent checkmark Upgrade SAP Host Agent with provided version and click on Next , after it is shown as “Available”. Click on Next

At the screen SAP HANA Client Software Installation Path choose radio button Local Client Directory click on Next

At the screen Media Browser enter Package Path /sapmedia/1909_EXP click on Next.

TIP: SWPM takes half hour to verify and check the zip files

Individual Package Location will change to /sapmedia/1909_EXP/S4CORE103_INST_EXPORT_1.zip click onNext

At the screen Software Package Browser accept Individual Package Locations  /sapmedia/1909_EXP/S4CORE103_INST_EXPORT_[2..20].zip

At the screen SAP HANA Multitenant Database Containers accept HANA DB Database Host vhcalhdbdb Instance Number 02 and Password Xxxxxxxn click on Next

At the screen Database Schema accept schema DBACOCKPIT password and confirm Schema password Xxxxxxxn click on Next

At the screen Database Schema accept schema SAPHANADB password and confirm Schema password Xxxxxxxn click on Next

At the screen Secure Storage for Database Connection select HANA Secure User tore (hdbuserstore) click on Next 

At the screen SAP HANA Import Parameters accept parameter values to keep on import and click on Next

At the screen Installation Export accept number of parallel jobs and HANA<sid>adm user as hdbadm and enter password as Xxxxxxxn click on Next

At the screen Primary Application Server Instance and ABAP Central Services Instance accept values PAS Instance Number 00, PAS Instance Host vhcals4hci
ASCS Instance Number 01, ASCS Instance Host Name vhcals4hci click on Next

At the screen ABAP Message Server Ports accept values for Ports 3601 and 3901 click on Next

At the screen ICM User Management for the SAP Web Dispatcher accept password for webadm Xxxxxxxn and click on Next

At the screen SLD Destination for the SAP System OS Level leave default radio button at No SLD destination click on Next

At the screen Message Server Access Control List leave default radio button at Do not create Message Server Access Control List click on Next

At the screen Additional Components to be Included in the ASCS Instance enable checkmarks at Install integrated web dispatcher and Install Gateway integrated in ASCS instance and click on Next

At the screen SAP Web Dispatcher Parameters leave default dispatcher parameters HTTPS Port 44300, Encryption Always, Configure HTTP Port Yes, click on Next

At the screen System Security leave default for Add Security Profile Parameters, click on Next

At the screen Configuring Transport Management for Single System select Run TMS config and enter password for TMSADM in Client 000 click on Next

At the screen Import SPAM/SAINT Update for Import SPAM/SAINT Update select radio button Yes
Specify the location of SPAM/SAINT Update Archive as /sapmedia/download/KD75473.SAR click on Next
TIP:
 This will save time later having to do it at the time of SUM installation. Click on Next

At the screen Additional ABAP Transports leave radio button at default No for Import ABAP Transports click on Next

At the screen Import SPAM/SAINT Update At the screen Preparing for the Software Update Manager checkmark Extract SUM, Start Sum Automatically, Click on Next

Enter path for Software Package Browser Package Path  /sapmedia/download/SUM20SP06_0-80002456.SAR
Click on Next

At the screen Software Package Browser accept the Individual package location of SUM file or provide Package Path click on Next

At the screen Additional SAP System Languages click on Next

At the screen Secure Storage Key Generation accept radio button – Individual Key (Recommended for Productive Systems) On the Next

At next screen Warning click OK

At next screen Cleanup of Operating System Users checkmark on Yes cleanup os users and click on Next

Here is the Parameter Summary Click on Next to confirm and begin the installation.

At next screen 96% Information click on OK

TIP: Please click on the url https://vhcals4hci.dummy.nodomain:1129/lmsl/sumabap/S4H/doc/slui and continue with the upgrade in another browser tab. You can then continue in the sapinst tab to complete SWPM. Using the combined SWPM+SUM command with stack.xml many dialog screens are skipped.

On sapinst screen click on OK.

Fill in the Feedback to SAP. and Exit

STEP 4: ADDON INSTALLATION USING SUM

As we executed combined SWPM+SUM you should have filesystem /usr/sap/S4H/SUM and you should directly jump to url https://vhcals4hci:1129/lmsl/sumabap/S4H/doc/slui

If not, don’t worry, please extract it as below 2 commands:

as s4hadm
cd /usr/sap/S4H
SAPCAR -xvf /sapmedia/download/SUM20SP06_0-80002456.SAR
as root
ps –ef | grep –i sapup
/usr/sap/S4H/SUM/abap/SUMSTART confighostagent
TIP: Please check that your /windows/drivers/etc/host file contains entry with IP address mapped to hostname vhcals4hci.
c:\users\mahesh>type c:\windows\system32\drivers\etc\hosts
10.20.130.140  vhcals4hci vhcals4hci.dummy.nodomain vhcals4hcs vhcals4hcs.dummy.nodomain vhcalhdbdb vhcalhdbdb.dummy.nodomain

Open Google Chrome browser (latest version recommended) Enter URL:
https://vhcals4hci:1129/lmsl/sumabap/S4H/doc/slui

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

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

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

PERFORMANCE TIP: When you use the Combined SWPM+SUM procedure, SUM is started bypassing many phases and prompts. When you get to the first screen of SUM, check the Number of processes for ABAP, SQL, R3trans and R3load and adjust in order to take advantage of CPU power and save time.  On the right side, select menu option (1) More, (2) Utilities, (3) SUM Parameters, (4) enter values and (5) Save.

GET ROADMAP

TIP: If you start with combined SWPM+SUM sapinst command you may not be prompted for below screen. Enter the stack.xml file name

At Additional Parameters for “Update on SAP S/4HANA (Single System)”
Check archive authenticity and checkmark Switch expert mode on.

EXTRACTION PHASE

No prompts here ….

If you are asked whether to import SPAM version 73 select Import SPAM version 73.

TIP: If you get error manifest signature revoked download new crlbag.p7s as per SAP Note 2491577 – SUM fails at phase PREP_EXTRACT/SCAN_DOWNLOADDIR with error message “SIGNATURE: manifest signature is revoked”

CONFIGURATION PHASE

Select Next at  (5%) Current Phase PREP_CONFIGURATIN/INITSUBST

TIP: if you start with combined SWPM+SUM sapinst command you may not be prompted for below screen)

At (9%) Current Phase PREP_EXTENSION/IS_SELECT Click on Next

At (9%) Current Phase PREP_EXTENSION/BIND_PATCH Click on Next
(NOTE: in the screen below BI_CONT and BI_CONT_XT will appear only if you selected at Maintenance Planner)

At (9%) Current Phase PREP_EXTENSION/BIND_PATCH
Include Transport Request – Click on Next

At (10%) Current Phase PREP_INTEGRATION/ADJUSTPRP Click on Next

CHECKS PHASE

PREPROCESSING PHASE

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


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

Click on Next

EXECUTION PHASE


(above wait time is assuming process parameters changed as per above performance tip)

At (90%) Current Phase: MAIN_UPTRANS/UPCONF
End of technical Downtime, click Next

At (95%) Current Phase: MAIN_POSTPROC/REQUPFINAL
Start of Cleanup Processing, click Next

At (99%) Current Phase: MAIN_POSTCLEAN/REQ_FINISH_IMPORT
Confirmation Required for Imports, check and select checkmark for I confirm that no more imports are running, click Next

SUM is completed.

Please login to the system and check the Installed product version as:Please find Installed Software Component version:

TIP: Schedule complete SGEN if it is not completed so far. This will help reduce time needed for Best Practices Content Activation.

STEP 5: S/4HANA RELEASE INFORMATION NOTE

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

NOTE DESCRIPTION MANUAL
2801166 CDS: Search in CDS connector can end with runtime error CX_SY_CONVERSION_NO_NUMBER No
2804162 CD: Dump GETWA_NOT_ASSIGNED in FB CHANGEDOCUMENT_PREPARE_TABLES No
2810687 SAP HANA error 2617 – DAF migration … failed – during freestyle search No
2812346 ALV list: Incorrect texts in top-of-page area No
2809538 OQ: dimF4-M remove assocation No
2832781 Manufacturing Substitute Version Specific Changes No

COMPONENT FOR INCIDENTS:

You can open OSS messages using component: for SWPM – BC-INS-SWPM
for SUM – BC-UPG-TLS-TLA

OTHER REFERENCES:

Installation Guide
Administration Guide for Implementation

Your system installation is complete. Congratulations !!!

Mahesh Sardesai
Product Expert – S/4HANA

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

     

    Thank you very much your article.

    I have also implement S4HANA 1909.

    Have you planned to implement the following SAP notes :

    2834069 – Solution Builder: Disable Language Selection during OP Activation

    2823473 – ABAP programming error due to missing class method

    If you don’t do it, /SMB/BBI will generate a dump. How were these behavior missed during validation phase? I’m fed up to be a beta tester 🙁

    I have also checked Admin Guide https://help.sap.com/doc/b4447b6727684f13917622cf63e1eb98/1909%20000/en-US/AdminGuideS4HANAImpl_HELP_EN.pdf

    They are a lot of errors and imprecisions : some chapters have not been updated (reference 1809), some steps are not necessary anymore because already done in standard.

    In addition to that, the behavior when i launched SCCL transaction is different between 000 and working client and i have lost a lot of time to shutdown the system and connect with SAP* for nothing… it would be nice to say that it’s 10 times faster than before with a new transaction.

    Do you know why we still need to perform SGEN ? SAP could include it directly in the backup

     

    • Hi Dora,

      This blog is only for installation of S/4HANA to get the system up and running, the best practice content activation is always covered in separate blog and this will be available in the next few days.

      Thanks for your suggestion and I would appreciate if you can send the errors to my email address mahesh.sardesai@sap.com. The client copy is covered in the content activation blog which is under progress. When doing the client copy , a question is asked if you want to go the new transaction and one can always reply No and go the old way of doing client copy. This has already been mentioned in the upcoming blog for BP activation.

      – Mahesh Sardesai