S/4HANA Greenfield Implementation

Overview

This Roadmap is intended for SAP BASIS team in an implementation project for SAP S/4HANA on premise. This Roadmap is comprised of different Phases and provide high-level details for each phase.

Phases include –

1. SAP Architecture
2. Maintenance Planner
3. Installation Preparation
4. SAP S/4HANA 1909 Installation
5. Best Practices Activation
6. SAP S/4HANA Migration Cockpit

Maintenance Planner

In the Maintenance Planner phase, create stack.xml file by selecting appropriate software components and download all required components.

1. Login into SAP marketplace
2. Select maintenance planner
3. Select the Fiori tile?Plan for SAP S/4HANA
4. Select?Install a new SAP S/4HANA
5. Then enter SID =?S4H;?select Target Version =?SAP S/4HANA 1909; Target Stack =?02
6. Then select choose?Co-deployed with Backend?for FIORI. For different FIORI deployment approach check this?link
7. Then?Continue Planning?–> select?OS/DB dependent files?–> and Click on?Push to Download Basket.

Installation Preparation

In the Installation Preparation phase, perform all pre-requisites for installations.

Consider following pointers –

1. OS recommended settings
2. Users ids, group creation
3. File system creation, mounting and provide appropriate permission
4. Define SID, Instance #
5. Download all software

?

OS recommended settings –

Following settings are applicable for HANA database –

1. Disable SELinux
2. Configure tuned to use profile “sap-hana”
3. Disable?ABRT, Core Dumps and kdump
4. Turn off auto-numa balancing
5. Disable Transparent Hugepages (THP)
6. Cluster-On-Die (COD) / sub-NUMA clustering technology (Intel 64 platform only)
7. Configure CPU Governor for performance?(Intel 64 platform only)
8. Configure Energy Performance Bias (EPB, Intel 64 platform only)
9. Disable?Kernel samepage merging (KSM)
10. Increase kernel.pid_max

?

For detailed steps, please refer SAP note –?2777782 – SAP HANA DB: Recommended OS Settings for RHEL 8

?

Users ids, group –

During the installation, the installer checks all required accounts (users, groups) and services on the local machine. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary.

For distributed installations, you must create the target users automatically using the installer or manually on the operating system, before starting the?installation.

Start the installer and choose?Generic Installation Options?–> HANA Database –>??Preparation?–>?Operating System Users and Groups?.

The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers belonging to an SAP system.

This does not mean that all users and groups have to be installed on all SAP servers.        

For Linux :

You have to set the limits for operating system users root,?<sapsid>adm, and your database-specific operating system users .

Use below command to assign limit :

limit -h datasize unlimited        

Use below command to check limit :

ulimit -a        

The output of command needs to be at least as follows:

OutputPropertiescpu time (seconds)unlimitedfile size (blocks)unlimiteddata seg size (kbytes)unlimitedstack size (kbytes)8192 KBcore file size (blocks)unlimitedopen files8192max memory size (kbytes)unlimited

?

For example purpose,

For SAP ASCS, ERS, Application Server –

User NameUIDPrimary GroupAdditional GroupDescriptionroot0root (0)0(root), 1001(sapinst)Superuser of the UNIX operating systems4hadm9100801(sapsys)801(sapsys), 1001(sapinst)SAP system administratorsapadm9300801(sapsys)801(sapsys), 1001(sapinst)SAP Host Agent administrator

Users s4hadm?and?sapadm?must have the same password on all hosts.        

For SAP HANA Database Server –

User NameUIDPrimary GroupAdditional GroupDescriptionroot0root (0)0(root), 1001(sapinst)Superuser of the UNIX operating systems4hadm9100801(sapsys)801(sapsys), 1001(sapinst), 1002(s4dshm)SAP system administrators4dadm9200801(sapsys)801(sapsys),1001(sapinst), 1002(s4dshm)SAP HANA Database System Administratorsapadm9300801(sapsys)801(sapsys), 1001(sapinst)SAP Host Agent administrator

You should remove the operating system users from the group sapinst?after?the installer has completed        

?

File system –

For Application Server,

PathTypeTo be mounted on/sapmntNFSASCS, ERS, PAS/usr/sap/transNFSASCS, ERS, PAS/usr/sap/S4H/SYSNFSASCS, ERS, PAS/usr/sap/S4H/ASCS20NFSASCS/usr/sap/S4H/ERS29NFSERS/usr/sap/S4H/D21LocalPAS

For Database Server,

PathType/sapmntNFS/rootLocal/usr/sapLocal/hana/sharedLocal/hana/dataLocal/hana/logLocal/hana/logLocal

Linux: Recommended file systems is XFS as long as your hardware or technology partner does not recommend otherwise.        

?

Other –

In this phase, define SID, instance # as per your your organizational compliance, if any.

Some SID are reserved, so choose your SAP system ID (SAPSID) and Database ID (DBSID) carefully. Please refer?1979280 – Reserved SAP System Identifiers (SAPSID)?.

Make sure, you have downloaded all required software.

?

SAP S/4HANA 1909 Installation –

Using software provisioning manager (SWPM) install instances in the following order:

?

ASCS instance

ERS instance

DB instance

PAS instance

AAS instances

?

Before installing S/4HANA application, install HANA database software and create tenant database

DB Software Installation –

1. Run?SAP HANA Hardware and Cloud Measurement Tools
2. SAP HANA hardware and cloud measurement tools help customers and partners to optimize their hardware or cloud systems before deploying SAP HANA or applying for SAP HANA certification.
3. Uncar HANA database SAR file and ./hdblcm as root user
4. This will install HANA database and create system and tenant database. This databases having SID as your HANA database. In some case you do not want the default tenant, Add option when call hdblcm
5. –create_initial_tenant=off
6. Create another tenant database, as per your SAP system SID using SQL command :

CREATE DATABASE S4H SYSTEM USER PASSWORD <password>;

ASCS instance

Make sure following file-systems are available –

/usr/sap/S4H/ASCS20

/usr/sap/S4H/SYS

/usr/sap/trans

/sapmnt

Virtual IP for should be enabled on s4node1.

Run the installer using following command using root user :

# ./sapinst SAPINST_USE_HOSTNAME=s4ascs

Select?High-Availability System?option

?

ERS instance

Make sure following file-systems are available –

/usr/sap/S4H/ERS29

/usr/sap/S4H/SYS

/usr/sap/trans

/sapmnt

Virtual IP for should be enabled on s4node2.

Run the installer using following command using root user :

# ./sapinst SAPINST_USE_HOSTNAME=s4ers

Select?High-Availability System?option

Install SAP HANA

Run the installer:

# ./sapinst SAPINST_USE_HOSTNAME=s4db

Install SAP Primary Application Server

The following file systems should be mounted on the host to run the Application Server instance

/usr/sap/S4H/D21

/usr/sap/S4H/SYS

/usr/sap/trans

/sapmnt

Run the installer:

# ./sapinst

Select?High-Availability System?option.

?

?

SAP S/4HANA 1909 Best Practices Activation

In this phase, we will activate best practices for S/4HANA 1909 system.

1. Login into client 000 and activate business function. Also capture it into TR
2. Perform client copy either merged or best practices. For more details, please refer?link
3. Get the Most Recent SAP Best Practices Content
4. import the latest reference content before content activation into your system:
5. BP-S4CONT 190902 (download from software center) –> BPS4CONT190902_0_0-70005217.ZIP
6. Download the zip archive locally.
7. Log on to client 000 in your system.
8. Start transaction?STMS_IMPORT.
9. From the menu, choose?Extras??Other Requests??Add.
10. In the dialog box, enter the transport request that you have imported (Request ID corresponds to the file name: <source system><6 digits>). Choose?Continue
11. Confirm that you want to add the transport request to the import queue.
12. Select a transport that you want to import.
13. Choose?Import Request.
14. Choose target client 000.
15. On the?Options?tab, select the?Ignore Invalid Component Version?flag.
16. Choose?Continue.
17. Pre-requisite steps: Must be performed before starting the Best Practices activation – (Functional Consultant task)
18. Mandatory : Apply all SAP notes provided in the content activation Note?2917623
19. Delete UTX2 and UTX3 in Transaction OVK1
20. Delete all client 000 reference Tax Jurisdiction codes from the activation client:
21. Pre-selecting the best practices Operating concern
22. Define Reasons for Quantity Differences deletion
23. Business Partner – Customer/Vendor settings
24. Deleting Number Range Intervals for Debitor Number Range Object
25. Create BP Interval for DEBITOR Number Range Object
26. Deleting Number Range Intervals for KREDITOR Number Range Object
27. Create BP Interval for KREDITOR Number Range Object
28. Assigning the BP Number Range Interval to All Customer Account Groups
29. Assigning the BP Number Range Interval to All Vendor Account Groups
30. Adapt Numbering Logic in the CVI – for Customers
31. Adapt Numbering Logic in the CVI – for Vendors
32. Carrying out Pre-requisites settings for implementation
33. Provide users for content activation.
34. Create a dialog user for content activation.
35. Prevent out of memory dumps
36. Best Practices IMPLEMENTATION –?
37. Importing Solutions from SAP Best Practices Content
38. Defining the Scope of Your Solution
39. Activating Your Solution
40. Prerequisite Settings for Activation
41. Updating Activation User Settings
42. Pre-Activation Settings for EWM Scope Items
43. Defining RFC Destination
44. Defining Dummy Logical System
45. Determining RFC Destinations for Method Calls
46. Determining RFC Destinations for Method Calls from SAP S/4HANA EWM
47. Defining Queue for Transfer to SAP S/4HANA EWM
48. Setting the QOUT Scheduler
49. Defining the Business System
50. Defining Own Business System
51. Maintaining Business System Group
52. Assigning Logical System and Queue Type
53. Setting Control for RFC Queue
54. Finally, Best Practices Activation and capture in the TR for QA/PROD landscape.
55. You will find some known error. Please refer attached from SAP note?2917623,?2839315

?

Migration Cockpit

From S/4HANA 1909 onwards, you can transfer data directly from SAP system

1. Transfer data from SAP ERP source system to target SAP S/4HANA system
2. Access source system via RFC connection
3. Available for
4. SAP ERP 6.0 to SAP S/4HANA
5. SAP Extended Warehouse management to Decentralized EWM based on SAP S/4HANA
6. SAP CRM to SAP S/4HANA for Customer Management