S/4HANA Greenfield Implementation

kundangandhi · ‎09-18-2020

This blog post will give quick overview for S/4HANA 1909 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 -

SAP Architecture

Maintenance Planner

Installation Preparation

SAP S/4HANA 1909 Installation

Best Practices Activation

SAP S/4HANA Migration Cockpit

SAP Architecture

In the SAP Architecture phase, define overall designing for SAP S/4HANA system. This based on different factors such as - on-premise / hyperscaler (AWS, Azure), OS version (RHEL, SUSE), HANA replication strategy (based on RPO/RTO requirement), backup-strategy.

Here in this example, SAP is deployed on on-premise data center, operating system RHEL 8.1 with PACEMAKER (for ASCS and HANA), HANA replication strategy SYNCMEM.

Maintenance Planner

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

Login into SAP marketplace

Select maintenance planner

Select the Fiori tile Plan for SAP S/4HANA

Select Install a new SAP S/4HANA

Then enter SID = S4H; select Target Version = SAP S/4HANA 1909; Target Stack = 02

Then select choose Co-deployed with Backend for FIORI. For different FIORI deployment approach check this link

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 -

OS recommended settings

Users ids, group creation

File system creation, mounting and provide appropriate permission

Define SID, Instance #

Download all software

OS recommended settings -

Following settings are applicable for HANA database -

Disable SELinux

Configure tuned to use profile "sap-hana"

Disable ABRT, Core Dumps and kdump

Turn off auto-numa balancing

Disable Transparent Hugepages (THP)

Cluster-On-Die (COD) / sub-NUMA clustering technology (Intel 64 platform only)

Configure CPU Governor for performance (Intel 64 platform only)

Configure Energy Performance Bias (EPB, Intel 64 platform only)

Disable Kernel samepage merging (KSM)

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:

Output	Properties
cpu time (seconds)	unlimited
file size (blocks)	unlimited
data seg size (kbytes)	unlimited
stack size (kbytes)	8192 KB
core file size (blocks)	unlimited
open files	8192
max memory size (kbytes)	unlimited

For example purpose,

For SAP ASCS, ERS, Application Server -

User Name	UID	Primary Group	Additional Group	Description
root	0	root (0)	0(root), 1001(sapinst)	Superuser of the UNIX operating system
s4hadm	9100	801(sapsys)	801(sapsys), 1001(sapinst)	SAP system administrator
sapadm	9300	801(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 Name	UID	Primary Group	Additional Group	Description
root	0	root (0)	0(root), 1001(sapinst)	Superuser of the UNIX operating system
s4hadm	9100	801(sapsys)	801(sapsys), 1001(sapinst), 1002(s4dshm)	SAP system administrator
s4dadm	9200	801(sapsys)	801(sapsys),1001(sapinst), 1002(s4dshm)	SAP HANA Database System Administrator
sapadm	9300	801(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,

Path	Type	To be mounted on
/sapmnt	NFS	ASCS, ERS, PAS
/usr/sap/trans	NFS	ASCS, ERS, PAS
/usr/sap/S4H/SYS	NFS	ASCS, ERS, PAS
/usr/sap/S4H/ASCS20	NFS	ASCS
/usr/sap/S4H/ERS29	NFS	ERS
/usr/sap/S4H/D21	Local	PAS

For Database Server,

Path	Type
/sapmnt	NFS
/root	Local
/usr/sap	Local
/hana/shared	Local
/hana/data	Local
/hana/log	Local
/hana/log	Local

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 -

Run SAP HANA Hardware and Cloud Measurement Tools
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.

Uncar HANA database SAR file and ./hdblcm as root user

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
--create_initial_tenant=off

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.

Login into client 000 and activate business function. Also capture it into TR

Perform client copy either merged or best practices. For more details, please refer link

Get the Most Recent SAP Best Practices Content
1. import the latest reference content before content activation into your system:
  BP-S4CONT 190902 (download from software center) --> BPS4CONT190902_0_0-70005217.ZIP
2. Download the zip archive locally.
3. Log on to client 000 in your system.
4. Start transaction STMS_IMPORT.
5. From the menu, choose Extras Other Requests Add.
6. 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
7. Confirm that you want to add the transport request to the import queue.
8. Select a transport that you want to import.
9. Choose Import Request.
10. Choose target client 000.
11. On the Options tab, select the Ignore Invalid Component Version flag.
12. Choose Continue.

Pre-requisite steps: Must be performed before starting the Best Practices activation - (Functional Consultant task)
1. Mandatory : Apply all SAP notes provided in the content activation Note 2917623
2. Delete UTX2 and UTX3 in Transaction OVK1
3. Delete all client 000 reference Tax Jurisdiction codes from the activation client:
4. Pre-selecting the best practices Operating concern
5. Define Reasons for Quantity Differences deletion
6. Business Partner - Customer/Vendor settings
  1. Deleting Number Range Intervals for Debitor Number Range Object
  2. Create BP Interval for DEBITOR Number Range Object
  3. Deleting Number Range Intervals for KREDITOR Number Range Object
  4. Create BP Interval for KREDITOR Number Range Object
  5. Assigning the BP Number Range Interval to All Customer Account Groups
  6. Assigning the BP Number Range Interval to All Vendor Account Groups
  7. Adapt Numbering Logic in the CVI – for Customers
  8. Adapt Numbering Logic in the CVI – for Vendors

Carrying out Pre-requisites settings for implementation
1. Provide users for content activation.
2. Create a dialog user for content activation.
3. Prevent out of memory dumps

Best Practices IMPLEMENTATION -
1. Importing Solutions from SAP Best Practices Content
2. Defining the Scope of Your Solution
3. Activating Your Solution
  1. Prerequisite Settings for Activation
    1. Updating Activation User Settings
    2. Pre-Activation Settings for EWM Scope Items
    3. Finally, Best Practices Activation and capture in the TR for QA/PROD landscape.
      1. 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

Transfer data from SAP ERP source system to target SAP S/4HANA system

Access source system via RFC connection

Available for
1. SAP ERP 6.0 to SAP S/4HANA
2. SAP Extended Warehouse management to Decentralized EWM based on SAP S/4HANA
3. SAP CRM to SAP S/4HANA for Customer Management