Former Member

May 11, 2017 6 minute read

First contact with S/4HANA 1610 IDES

There is an IDES version of S/4HANA available since april 2017. SAP note 2445594 – IDES S/4 HANA 1610 describes the details about the prerequisites.

I installed IDES S/4 HANA 1610 on this platform

Intel® Xeon® E5-1650 v3 Hexa-Core
2x 960 SATA SDD RAID1
256GB RAM
VMware ESXi 6.0

I ended up with 3 VMs running on this platform

Database instance
Primary application server
IDES S/4HANA frontend-server

Preparations

You have to download the following packages:

RDBMS HANA:
SAP IN-MEMORY (SAP HANA) > HANA PLATFORM EDITION > SAP HANA PLATFORM EDITION > SAP HANA PLATFORM EDITION 2.0
HANA Client, SAP Kernel:
SAP S/4HANA > SAP S/4HANA 1610
IDES export, IDES Frontend export, RDBMS ASE:
SAP S/4HANA > SAP S/4HANA 1610 > IDES VERSION

Copy all archives to 120GB drive installation files to mount into VM and “unzip -x” or “unrar x”. Delete archives after extract, 120GB is not sufficient space.

Installation of Database instance

Step-by-step description:

Create VM with
1. 208GB RAM
2. 8 vCPU (1x socket, 8x core)
3. 70 GB drive OS (Primary partition, EXT4)
4. 32GB drive SWAP
5. 200GB drive DB (Primary partition, EXT4)
6. 120GB drive installation files
Install SLES 12 SP2 as described in
1. SAP note 1984787 – SUSE LINUX Enterprise Server 12: Installation notes
2. SAP note 2205917 – SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12
Mount 200GB drive DB to directory /hana
Mount 120GB drive to directory /mnt/sapnet
Follow HANA_and_ABAP_on_One_Server.pdf in SAP note 1953429 – SAP HANA and SAP NetWeaver AS ABAP on one Server to install HANA database

Installation of Primary application server

Step-by-step description:

Create VM with
1. 16GB RAM
2. 4 vCPU (1x socket, 4x core)
3. 70 GB drive OS (Primary partition, EXT4)
4. 16GB drive SWAP
5. Reuse 120GB drive installation files
Install SLES 12 SP2 like above
Mount 120GB drive to directory /mnt/sapnet
Install Software Provisioning Manager 1.0
Run SPM with SAP S/4HANA 1610 > SAP S/4HANA 1610 Server > SAP HANA Database > SAP Systems > Application Server ABAP > Standard System
1. (o) Typical
2. Use IDES Export

Installation of IDES S/4HANA frontend-server

Step-by-step description:

Create VM with
1. 16GB RAM
2. 4 vCPU (1x socket, 4x core)
3. 70 GB drive OS (Primary partition, EXT4)
4. 16GB drive SWAP
5. 120GB drive DB (Primary partition, EXT4)
6. Reuse 120GB drive installation files
Install SLES 12 SP2 like above
Mount 200GB drive DB to directory /sybase
Mount 120GB drive to directory /mnt/sapnet
Install Software Provisioning Manager 1.0
Run SPM with SAP S/4HANA 1610 > AS ABAP for SAP S/4HANA Frontend > SAP ASE > SAP Systems > Application Server ABAP > Standard system
1. (o) Typical
2. Use IDES Frontend Export

After starting IDES S/4HANA frontend-server the system is hell slow, needs dozen of minutes to compile on SSD. I had to wait about hour after logon the first time. If you open top in shell, you will see the top process DATASERVER with 100 percent CPU.

Go directly after 1st logon to menu System > Services > Jobs > Job Overview and kill jobs

/UIF/LREP_LOAD_CONSISTENCY_CHECK
SAP_CCMS_MONI_BATCH_STARTUP_DP

Maybe someone can mention SAP note 2411647 – /UI5/APP_INDEX_CALCULATE and /UIF/LREP_LOAD_CONSISTENCY_CHECK jobs failing – BS on ASE in SAP note 2445594 under 10. Last minute information

Follow SAP Note 2445594 and set parameter rsdb/max_blocking_factor = 5 in RZ11

Lessons learned

Software Provisioning Manager does not install SAP HANA database
I could not foul IDES Frontend Export with MaxDB, setup hangs after 5 failed imports, even database is calculated to 140GB instead of ~80GB SAP ASE

Todos

done. Run SGEN in IDES S/4HANA frontend-server to find out final database size
Check configuration in IDES S/4HANA frontend-server to backend Primary application server
Install JAVA instance
Make backups

Comparision IDES client 400 (HANA) vs. IDES client 800 (non-HANA)

Numbers of Entries from SE16 for same tables.

Table	IDES S/4HANA 1610 client 400	IDES ERP 6.0 EhP7 client 800
LFA1	325	2.427
BKPF	128.591	585.340
BSEG	475.832	1.682.270
EKKO	3.617	18.825
EKPO	22.836	33.545
RBKP	8.263	6.145
RSEG	31.117	15.808

Updates

[2017-MAY-15] After the first weekend job /UIF/LREP_LOAD_CONSISTENCY_CHECK finished its first run with long runtime, 6-9 hours on SSD with 100% CPU for DATASERVER and blocks any other background operation from other standard jobs during runtime and slows down the whole system. But now, it looks ok.
[2017-MAY-15] Directory /hana/data after SGEN: 136GB
[2017-MAY-15] Directory /sybase after SGEN: 86GB
[2017-MAY-31] Start of Fiori Launchpdad on Front-end server ends with
500 SAP Internal Server Error
ERROR: Secure Storage: Entry cannot be decrypted (termination: ERROR_MESSAGE_STATE)
Follow SAP note 1532825 – Deleting SECSTORE entries during system export/system copy
and follow.
[2017-JUN-08] Start of Fiori Launchpad on Front-end server ends with
500 SAP Internal Server Error
ERROR: No more memory available for 5536 bytes in the shared object memory. (termination: RABAX_STATE)
SDN: No memory available for 9632 bytes in the shared object memory
SAP note 1322182 – Memory consumption of ABAP Shared Objects
[2017-JUN-08] Again long runtime of jobs /UI5/APP_INDEX_CALCULATE and /UIF/LREP_LOAD_CONSISTENCY_CHECK im SM37
SAP note 2421705 – Prevent execution of job /UIF/LREP_LOAD_CONSISTENCY_CHECK when job /UI5/APP_INDEX_CALCULATE
SAP Support packages
Update SAP_GWFND 751 from 0000 to 0002
Update SAP_UI 751 from 0000 to 0002 Oh!? 1.21 GB+
[2017-JUN-09] Set RZ10 parameter abap/shared_objects_size_MB = 400 (default 222 with 16GB RAM)
[2017-JUN-09] Set parameter rsdb/max_blocking_factor = 5 in RZ10 (SAP Note 2411647) and restart the system. RZ11 is not a good idea for an automatic running, self-starting job.
[2017-JUN-09] Shortdumps in ST22 with
Runtime Errors OBJECTS_TABLES_NOT_COMPATIBLE
ABAP Program /IWBEP/CL_MGW_ABS_DATA========CP

SAP note 2479680 – Runtime Error OBJECTS_TABLES_NOT_COMPATIBLE
SAP note 2435153 – Response SubNode empty for deep insert #2
[2017-JUN-09] Set RZ10 parameter abap/shared_objects_size_MB = 500 (default 222 with 16GB RAM)
[2017-AUG-08] Install HANA license, helpful links
SAP HANA License Management
Hardware Key for the HANA Database
https://blogs.sap.com/2016/06/21/convert-hana-single-db-system-to-support-multitenant-database-containers-mdc-on-aws-part-2/
2504121 – SAP DBTech JDBC: [7]: feature not supported: License commands are not available on tenant databases
[2017-AUG-08]
cd /usr/sap/HD1/HDB00/exe
./hdbsql
hdbsql=> \c -i 00 -u SYSTEM -d SYSTEMDB
SELECT * FROM M_LICENSE
SAP Marketplace
hdbsql=> \mu ON
hdbsql=> set system license ‘ (paste license.txt from Marketplace ) ‘ ;
hdbsql=> 0 rows affected (overall time 27.114 msec; server time 24.962 msec)
[2017-AUG-14] Check installed languages and configure available logon languages
Transaction SMLT > Goto > Other Tools (SE38 RSTLAN_TOOLS)
Tools for Language Administration and Transport > System Configuration > NLS installation tool
Remove parameter zcsa/installed_languages from RZ11, because it is dynamic parameter in NW 7.50 and later
[2017-AUG-30] Used memory by HANA database after some runtime
Transaction DB12 > System Information > License
System measurement:
Memory Allocation (GB): 149GB
[2017-NOV-01] Installed Add-Ons in IDES Fiori Front-end server from transaction SAINT
[2017-DEC-27] OS upgrade to SLES 12 SP3
Error message at end of SLES upgrade:
— quote —
Execution of command “[[“/usr/sbin/grub2-install”, ‘–target=i386-pc’, ‘–force’, ‘–skip-fs-probe’, ‘/dev/sda1’]]” failed.
Exit code: 1
Error output: Installing for i386-pc platform.
/usr/sbin/grub2-install: error: the drive hd0 is defined multiple times in the device map /boot/grub2/device.map
— quote —
Upgrade generates duplicate entries in /boot/grub2/device.map for whatever reason.
After upgrade:
— /boot/grub2/device.map —
(hd0) /dev/sda
(hd0) /dev/sda
(hd1) /dev/sdb
— quote —
Remove duplicates and restore former mapping:
— /boot/grub2/device.map —
(hd0) /dev/sda
(hd1) /dev/sdb
— quote —
[2017-DEC-27] Update HANA database
Download media from
Support Packages & Patches > By Category > SAP In-Memory (SAP HANA) > HANA Platform Edition > SAP HANA Platform Edition > SAP HANA Platform Edition 2.0 > SAP HANA Databse 2.0 > IMDB_SERVER20_023_0-80002031.SAR
Run ./SAP_HANA_DATABASE/hdbupd
Current: 0 | HD1 | version: 2.00.010.00.1491294693
Updated: 0 | HD1 | version: 2.00.023.00.1513691289
[2017-DEC-27]Update SAP Kernel on s4hana1610as
Download media from
Support Packages & Patches > By Category > Additional Components > SAP Kernel > SAP Kernel 64-bit Unicode > SAP Kernel 7.49 64-bit Unicode
LINUX ON X86_64 64BIT / #DATABASE INDEPENDENT : SAPEXE_401-70001625.SAR (Kernel Part I)
LINUX ON X86_64 64BIT / SAP HANA DATABASE : SAPEXEDB_401-70001624.SAR (Kernel Part II)
Current Patch Level: 17
Updated Patch Level: 401
Run, SGEN, run…

23 Comments

You must be Logged on to comment or reply to a post.

Bilal Ilyas

June 1, 2017 at 6:56 am

Hello Sir,

I have installed SAP IDES 1610. Your tutorial was extremely helpful for installation. Please help me in one query. I am trying to activate FM / GM Module EA-PS in SFW5 but I am unable to activate it. Could you guide me on activating FM / GM module EA-PS in SFW5 as I can not activate IS-PS in BF11.

Could you please provide an email or skype ID for getting in contact with you sir.

Regards.

Former Member

Blog Post Author

June 8, 2017 at 2:56 pm

Does this help?

Activation of EA-PS component

Luong Doan Khac

April 12, 2018 at 10:39 am

SAP Note 2445594

10. Last minute information

Switch Framework is disabled. In order to enable SFW5, please import attached transport-request (SFW5.zip)

Franco Samà

June 12, 2017 at 4:42 pm

Hello Sir,

Does it possible to install FES embedded?

Regards.

Former Member

June 13, 2017 at 1:02 am

Hello Sir,

Thanks a lot for the wonderful blog. we were able to successfully Install S4HANA IDES & Frontend Server. However we are facing issues with SMT1 when connecting via Front end server.

Could you please provide some updates on this configuration. We followed the standards,with respect to Users/Roles & RFC creation. however we are receiving INFORMATION FAILURE when SAP Frontend Gateway to Trusted systems check list is run.

Appreciate your response. Thanks in advance.

Regards

Irfan

Former Member

July 2, 2017 at 8:11 am

Hello,

Is it possible to install both the DB and the AS server of this on 140gb of rams?

I attempted one installation on the same machine i had a regular S/4 Hana 1610 server on but after 50 hours it stayed stuck on the create DDL Views phase. The installation did not generate any errors neither the logs.

I tried opening an OSS ticket but it took over 3 weeks and at the end i did not receive any solution.

Best Regards,

Ashraf

Former Member

Blog Post Author

August 30, 2017 at 3:40 pm

Used memory by HANA database after some runtime
Transaction DB12 > System Information > License
System measurement:
Memory Allocation (GB): 149GB

So 140GB seems to be not enough memory for stable environment.

Nageswararao Seemakurty

July 9, 2017 at 4:49 am

Hello

I am little confused with the above instructions. Are the above instructions meant for installing S/4 Hana IDES on Hana Database ? or Sybase (ASE) database ? Why do we need IDES export and Frontend Export DVDs for RDBMS ASE ? Why there was mention about /sybase filesystem usage after SGEN unless the installation is done on sybase database? Can we do this IDES installation on Hana database instead of Sybase database and can the DB and Appserver be installed on one single Linux server ? Please suggest.

Former Member

Blog Post Author

July 10, 2017 at 11:19 am

Best is to start with reading SAP note 2445594 – IDES S/4 HANA 1610

Solution > 3. Hardware Requirements describes the requirements for two systems, which are provided as IDES Export.

S/4HANA 1610 System on HANA database
Fiori Frond-end Server on SAP ASE database

The 2nd part is optional, only required if you want to use the Fiori Apps in this IDES installation.

Jesse Leal

October 31, 2017 at 5:34 am

Hi Former Member ,

Is the Fiori front-end ready with working apps for all the components in the S/4 system (such as MDG, EPPM, PP, MM, PLM, etc.) or a).- all apps need to be installed separately, b).- all apps exist, but not connected to S/4, c).- some apps exist and connected to S/4 or d).- some apps exist but not connected to S/4?

Thanks and regards,

J.L.

Former Member

Blog Post Author

November 1, 2017 at 10:17 am

I have added a screenshot of transaction SAINT at end of the blog.

I did not investigate more time than installing the Front-end server yet. A collegue did the configuration to back-end, but we ended up in install our own NW 7.51 Fiori Frond-end server with the same database like our other systems.

So I can give no answer to a/b/c/d).

Russ Wagner

August 9, 2017 at 7:05 pm

Great blog Tibor.

I am just about to kick-off the same (S/4HANA 1610 / IDES) on AWS (Amazon). Please continue to update the blog as you have. It's been a great resource for me.

Russ

Ken Chen

March 21, 2018 at 9:23 pm

Hi Russ, I am attempting the same thing - how did it go for you? Thanks.

Jayson Parker

August 28, 2017 at 6:37 pm

Hi Tibor,

Is the Front End server only necessary for Fiori functionality?

-Jayson

Former Member

Blog Post Author

August 30, 2017 at 3:28 pm

Yes, Front End server (IDES S/4HANA frontend-server) is only necessary for Fiori functionality.

Jayson Parker

August 30, 2017 at 3:29 pm

Thought so, thanks for the response!

Jayson Parker

September 12, 2017 at 4:57 pm

Hi Tibor,

For the OData services already configured on the FrontEnd, did you update the system alias of all of the services to point to the new backend instance? I'm trying to find a way to do a mass update to all the active OData services to set the system alias to my backend. I would prefer to not go through them one-by-one 🙂

Russ Wagner

November 26, 2017 at 5:28 pm

Hello Tibor:

Quick question if you don't mind.

Do you know what the uncompressed database size was when you got your system up and running? Unfortunately I had to break away from setting up my own instance and I won't be able to resume until mid-December.

Thanks in advance.

Russ

Former Member

Blog Post Author

December 27, 2017 at 3:30 pm

Hi Russ,

No, sorry. I did not record the file size after installation, because I crashed MaxDB too often with "Database full" after 1st SGEN run.

[2017-MAY-15] Directory /hana/data after SGEN: 136GB

My minimum "stable" database size for development: Installation + SGEN load + 5-10GB

Tibor

Tasnim Shakir

November 30, 2017 at 7:15 pm

Can someone tell me how big is the IDES data on 1610. Does it have a lot of data or just little data.

Is the IDES data more for finance related areas or for logistics?

Former Member

Blog Post Author

December 27, 2017 at 3:23 pm

I added a table with "Comparision IDES client 400 (HANA) vs. IDES client 800 (non-HANA)".

Tobias Topyla

March 16, 2018 at 8:29 am

Thank You Tibor!

vinod vaddi

July 30, 2018 at 7:49 am

Hi..I'm installing S4HANA IDES 1610. at around 81% of the installation (ABAP load is completed), I'm getting the error:

"An error occurred during table depooling: Immediate start not currently possible. Check the log file /usr/sap/trans/log/RUTPOADAPT.S4I or run report RUTPOADAPT again manually."

At this stage, the above mentioned file is not even created in ../trans/log

Installation logs contain below message:

"Executing BAPI_XBP_JOB_START_IMMEDIATELY returns '066': Immediate start not currently possible
Could not start job SWPM_RUTPOADAPT, trying 5 times, giving up."

I could login into the system and found that ST22 dumps (DBSQL_TABLE_UNKNOWN) are generated continuously.

Ran the report RUTDDLSCREATE as per note 2565383 to fix the dumps. It ran for 9 hrs. and dumps stopped after that.

For the first issue of de-pooling, I've ran the report mentioned in the error message, RUTPOADAPT manually. The job finished immediately. Now the log file is created in ../trans/log directory and contains below messages:

Directory: /usr/sap/trans/log
Name: RUTPOADAPT.S4I
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 EAD525 Start of XPRA program: "RUTPOADAPT" time stamp "20180720" "001102"
1 EAD526XFunction: "Convert Pool tables to transparent" " " " " " "
4 EAD010X"Table" "GLP1" "will be converted to transparent" " "
4WEAD010 "Table" "GLP1" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLP2" "will be converted to transparent" " "
4WEAD010 "Table" "GLP2" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLPPC" "will be converted to transparent" " "
4WEAD010 "Table" "GLPPC" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLS1" "will be converted to transparent" " "
4WEAD010 "Table" "GLS1" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLS2" "will be converted to transparent" " "
4WEAD010 "Table" "GLS2" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLSPC" "will be converted to transparent" " "
4WEAD010 "Table" "GLSPC" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLT1" "will be converted to transparent" " "
4WEAD010 "Table" "GLT1" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "GLT2" "will be converted to transparent" " "
4WEAD010 "Table" "GLT2" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "JVS1" "will be converted to transparent" " "
4WEAD010 "Table" "JVS1" "cannot be converted to transparent." "There are Pool specific properties"
4 EAD010X"Table" "SCIPT" "will be converted to transparent" " "
1 EAD010X"'Conversion Pool -> transparent executed for" "1" "tables from" "10"
1 EAD010X"1" "tables successful handled" " " " "
1 EAD010X"0" "tables with conversion with warning" " " " "
1 EAD010X"0" "tables with failed conversion" " " " "
1 EAD010X"For conversion log for special table" "see conversion log in SE14" " " " "
1 EAD527XEnd of XPRA program "RUTPOADAPT" "20180720" "001112"
1 EAD528 XPRA program ends with return code "0"

I've checked notes 2227432 and 1892354 that talk about depooling issues but the solution given is for non-HANA DB.

Anyone faced this issue during IDES installation?

First contact with S/4HANA 1610 IDES

Preparations

Installation of Database instance

Installation of Primary application server

Installation of IDES S/4HANA frontend-server

Lessons learned

Todos

Comparision IDES client 400 (HANA) vs. IDES client 800 (non-HANA)

Updates

Assigned Tags