Whitepaper

SAP S/4HANA SCALE OUT AT LENOVO

Lenovo SAP S/4HANA Scale out - Cycle 1

A Whitepaper by Zhe Zhang and Irene Hopf

 Functional Test
 Lessons Learned

VERSION 1.2
10 APRIL 2018

© Lenovo 2018 1 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
1. Introduction
Lenovo is a US$46 billion global Fortune 500 company and a leader in providing innovative consumer,
commercial and enterprise technologies. ECC, core IT system of Lenovo, is playing an important role in
supporting global business, including management of large amount of sales orders fulfillment and supply
chain management.

As a significant step of the Lenovo digital transformation, Lenovo has developed a long-term plan to
gradually migrate the SAP IT systems from non-SAP HANA databases to SAP HANA. Up to now, Lenovo
has successfully executed BW/APO/BPC/CRM/SRM SUS/GTS HANA migration. SAP ECC is the next
system on the Lenovo HANA adoption roadmap. Currently Lenovo ECC is running on any DB with data size
near 40TB, facing a very large volume and high transaction load.
SAP S/4HANA is the next-generation ERP business suite, a real-time enterprise resource management suite
for digital business built on advanced in-memory platform SAP HANA, delivering massive simplifications
(customer adoption, data model, user experience, decision-making, business processes and models) and
innovations to help businesses Run Simple in the digital economy.

For a large-scale ECC system, a single HANA node (scale up) may not meet the data volume size
requirement with continuous data growth. As designed for maximum scalability as a co-innovation of
application and database, SAP S/4HANA can support HANA Scale out or memory & CPU scaling for a
system exceeding a single HANA appliance size limitation. Therefore, SAP S/4HANA Scale out is an
appropriate option for Lenovo ECC HANA migration.

Before the production ECC migration to S/4HANA can start, Lenovo launched S/4HANA Scale out Cycle 1
Project in cooperation with SAP to verify the technical feasibility, ensure a safe handling of the large data
volumes and transactional load, and test the appropriate infrastructure configuration for SAP HANA.
Intentionally, we do not call this a “proof of concept” but rather Cycle 1 because it is the first step in a
journey towards SAP S/4HANA.

Acknowledgements
Thanks to the following people for their contributions to the project:
Lenovo:
Martin Bachmaier, John Donovan, Taggart Robertson, Miao Hui, Song Fei, Wang Weidong, Qiu Shanlin,
Zhao Yan, Wei Na, Chou Jingzheng, Ma Jun, Jin Xing, Barry Cui, Zhao Dan, Yang Qing, Li Ying

SAP:
Dr. Richard Bremer, Susanne Janssen, Cynthia Wang, Eric Liu, Hongkong Sun, Yongchen Xie, Claude
Cheng, Ruth Tian, Michael Hu, Extra Li

Mellanox:
Mike Montgomery, Crystal Zhang

© Lenovo 2018 2 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

Table of Contents
Scope
- Business Scenario
- Functional & Technical Requirement
Project Phases
- Project Setup
- Preparation for SAP S/4HANA Conversion
- Technical SAP S/4HANA Conversion (with SUM)
- Post Activities to Complete SAP S/4HANA Conversion
- SAP S/4HANA Scale out Functional and Performance Testing
Technical Architecture
- Hardware requirements
- Lenovo S/4HANA Scale out Cycle 1 Hardware Architecture
- Software Version
Functional Adjustments
- Simplified Data Model in SAP S/4HANA
- Required Solution Adjustments
- Detailed Adjustment Approach
Technical Adjustments
- SAP Release Requirements
- Preparation before S/4HANA Scale out conversion
- Adjustments during S/4HANA Scale out conversion
- Conversion – Main phases of Standard Approach
- S/4HANA Scale Out table distribution
- S/4HANA Scale Out table redistribution after first cycle performance test
- Reference Documentation
Custom Code Adjustments
- Required Adjustments in Custom Code
- Modification Overview
- Modification Steps
Test Result & Analysis
Summary

© Lenovo 2018 3 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
2. Scope
2.1 Business Scenario
The SAP ECC system is a core application covering the Lenovo digital center, PC and mobile business,
containing multiple application components such as SD (Sales & Distribution), PP (Production Planning),
MM (Materials Mgmt), LE (Logistics Execution) and FI (Finance).
The S/4HANA Scale out Cycle 1 project focuses on the technical feasibility leveraging the business-critical
processes and business processes generating the highest load instead of full functional test. We selected one
end-to-end PC sales outbound scenario and eight key standalone report scenarios.
No external system connected.

Lenovo end-to-end PC Sales Outbound Scenario

Lenovo Key Standalone Reports

2.2 Functional & Technical Requirements

Within the pilot project, we defined and achieved the following KPIs:
 Functional Scenario
- PC Sales outbound process and standalone report scenarios
 Functional Feasibility
- The selected end-end business process work in the new environment of S/4HANA
- Custom code relevant for the business process identified and adjusted
 Technical Feasibility/Performance
- Acquire performance test result data of selected scenarios on S/4HANA scale out system
- Performance optimization within project period
- Not in scope for Cycle 1: The business continuity tests with high availability and disaster recovery.
 Infrastructure Stability/Scalability
- Stability- an unplanned outage occurred. After system adjustment and optimization, the system and
infrastructure remains stable during the later execution of functional tests and no more unplanned
downtime occurred.
- Scalability-S/4HANA scale-out on Lenovo hardware can handle the size of the database

© Lenovo 2018 4 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
3. Project Phases
The project contains the following phases:

3.1 Project Setup

- Sizing and confirmation of the hardware
- Define the technical architecture
- Readiness Check and verify the required functional changes
- Define detailed test scope for business tests
- Define approach for test data, load generation and scripting
- Verify solution landscape for the test
- Align detailed KPIs
- Source SAP ERP system preparation & setup (OS, hardware configuration, ensure sufficient resource)
- Performance baseline measurement in source system

3.2 Preparation for SAP S/4HANA Conversion

- Preparation checks & reports, SAP notes
- Functional preparation (FI/MM/PP/SD/LE)
- Master data BOM migration to production version check & SAP notes
- Analysis of used custom code objects (S/4HANA customer code impact analysis)
- Basis S/4 pre-conversion check (several iterations)
- Basis table analysis, calculate table distribution for scale-out
- Setup the new HANA server + system (including table creation)
- Basis maintenance planner S/4HANA stack calculation

3.3 Technical SAP S/4HANA Conversion (with SUM)

- Technical execution of SUM tool phases: Extraction, Configuration, Checks
- Implement Checks results (missing SAP Notes, etc.)
- Technical execution of SUM tool phase: Preprocessing
- Development adjustment (SPDD)
- Development correction of activation errors
- Development add-on activation issues analysis & resolution
- Build up new tables in target HANA Scale out system
- Technical execution of SUM tool phase Execution
- Technical execution of SUM tool phase Post Processing
- Backup of new SAP S/4HANA Scale out system

3.4 Post Activities to Complete SAP S/4HANA Conversion

- Customer vendor integration: Preparation, analysis, clean-up and migration
- Functional customizing and migration (FI/SD/MM/PP/LE)
- Master data BOM migration to production version check & SAP note
- Technical Post Activities as per S/4HANA Conversion Guide
- Basis: Analysis of Conversion runtime and downtime
- Adjustment of SPAU and Custom Code Objects

3.5 SAP S/4HANA Scale out Functional and Performance Testing

- Unit test, single user test including PC Sales E2E and standalone report scenarios
- Technical test (system administration test)
- Performance test Cycle 1 for key processes & optimization
- Table re-distribution (table re-group & replicate)
- Performance test cycle 2 for key processes & optimization (after table redistribution)

© Lenovo 2018 5 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
4. Technical Architecture
SAP S/4HANA Scale out architecture introduction, including hardware requirements, hardware architecture
and software versions.

4.1 Hardware requirements

SAP S/4HANA Scale out spreads the database across multiple hosts, reaching a very high CPU and memory
capacity.
The minimum requirements for S/4HANA Scale out:
- Minimal server size: 8 CPUs, 6TB memory
(All nodes must be of the same RAM size and CPU capacity)
- At maximum 4 worker nodes; a standby node is optional
(The number of nodes shall be as small as possible to limit operational effort)
Detailed hardware requirements refer to SAP Note 2408419.

Example of SAP S/4HANA Scale out architecture

4.2 Lenovo S/4HANA Scale out Cycle 1 Hardware Architecture

Server Hardware:
HANA server: Lenovo System x 3950 8 sockets, 8 TB memory, 3 worker nodes + 1 standby node
This is the default setup. For business continuity in a production level setup, we recommend to use a full
stand-by system identical to the production system. This is connected via SAP HANA system replication
(synchronous) in syncmem mode to ensure no data loss (RPO = 0). This enables also short failover times
(small RTO) with an automatic failover capability through SUSE HA extension. Then the “+1 standby” node
can be omitted.

Storage Hardware:
Lenovo DSS-C (Distributed Storage Solution for Ceph)
Software Defined Storage Solution leveraging SUSE Enterprise Storage using 100*3.84TB SSDs (250 TB All
Flash)
The Lenovo DSS-C used in this environment consists of four x3650 M5 servers with each holding 24x 3.84
TB Enterprise Capacity devices. Two x3550 M5 were used as deployment and gateway servers. The Lenovo
DSS-C exports its storage via Ethernet over two different interfaces, as depicted in Figure ‘Software-defined
storage architecture for SAP HANA.
CephFS for /hana/shared and rbd for /hana/data and /hana/log
The storage configuration can be scaled out through additional x3650 M5 storage servers.
This link contains more information on the storage solution.

Software Defined Storage Architecture for SAP HANA

Network:

© Lenovo 2018 6 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
The cluster of SAP HANA server nodes consist of a redundant 100 GbE connection. The connectivity
between the SAP HANA scale-out servers and the DSS-C storage servers is provided via a dedicated
redundant 40 Gbit Ethernet.

Lenovo S/4HANA Scale out Cycle 1 Architecture

When we ran the SAP HANA Hardware Certification Check Tool (HWCCT) with this HW setup, the results
exceeded the required SAP HANA TDI key performance indicators (KPI) by far.

4.3 Software Versions

Source system:
- SAP ERP 6.0 EHP7 SP12 on any DB
- Unicode converted system
- Single stack, ABAP stack only

Target system:
- SAP S/4HANA 1610 FPS 02
- SAP S/4HANA Server (incl. component S4CORE 101)
- SAP NetWeaver 7.51 for S/4HANA, on-premise edition
- SAP HANA 2.0 (rev 2.00.011)
- Operating system SLES for SAP Applications 12 SP2. For system stability and performance, the
operating system parameters of SLES for SAP Applications 12 SP2 need to be configured (OS settings
for SLES 12 for SAP Applications 12 refer to SAP Note 2205917)

Release combination of source and target system

Storage system:
SLES12 SP2 and SUSE Enterprise Storage version 4 with all updates as of April 2017.
Kernel 4.4.49-92.14-default, Ceph version 10.2.5-239 which is a Jewel release with filestore-based OSDs
(object storage device) was used. 6 OSDs per server. System-wide block-level multi-queueing was enabled.

© Lenovo 2018 7 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
5. Functional Adjustments
The data model changes in SAP S/4HANA drive the need for functional and custom code adjustments. Some
functionality available in SAP ERP is not available in SAP S/4HANA while some functionality changed
greatly in S/4HANA. This is the case whenever there was duplicate functionality for the same process. The
section “Required Solution Adjustments” lists all simplification items relevant for Lenovo.
Availability of WM as part of the compatibility scope in SAP S/4HANA will be restricted until the end of
2025. In the future, Lenovo considers a transition to EWM.
In the Cycle 1 project, we made modifications in the source ECC on the legacy any DB system according to
the pre-check report in order to adjust the system into a status able to start the S/4HANA conversion. This is
necessary for any move towards SAP S/4HANA, no matter what system landscape (single node or scale out)
is used for the infrastructure.
When the technical S/4HANA conversion completed, further modifications need to be done on the new
S/4HANA Scale out system to convert data to the S/4HANA data model and complete functional adjustment.
After functional adjustment based on initial HANA scale out table distribution, cross-node joins were
observed. To eliminate cross-node join and optimize performance, HANA scale out table redistribution
needed. Please refer to chapter 6.5 and 6.6 for HANA scale out table distribution/redistribution details.

5.1 Simplified Data Model in SAP S/4HANA

S/4HANA
Description of Data Model Changes Note
Functionality
Merge of status info into document/item tables (from dedicated table)
Simplified
Simplification of document flow table
Sales Order 2267306
Elimination of indices for sales documents and aggregation on the fly
Management
Elimination of rebate index table VBOX
Simplified New table PRCD_ELEMENTS for storing document conditions, with extended field
2267308
Pricing length of several fields and other changes.
Simplified Material document table MATDOC
Inventory Elimination of aggregates/history tables for stock quantities and aggregation on the fly 2267788
Management Inventory valuation via Material Ledger only (with compatibility views)
New accounting based on new G/L concepts, incl. CO, AA, ML with central Financial
Financials document table ACDOCA across G/L, CO, AA, ML.
Universal All cost elements are G/L accounts.
Journal Elimination of aggregates and indices for financial documents and aggregation on the
fly.

- Sales Order Management and Pricing overview:

Check SAP note 2198647 (custom code check) and 2220005 (Pricing and Condition Technique) for
details.

© Lenovo 2018 8 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

- Materials and Inventory Management – Quantities View.

Check SAP note 2206980 for details.

- Materials and Inventory Management – Valuation View

Check SAP note 2337368 Inventory Valuation (part of Materials Management – Inventory
Management): Change of data model in S/4HANA 1610 for details.
On the fly aggregation and compatibility views for obsolete tables (reading valuation from ML instead)

© Lenovo 2018 9 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

5.2 Required Solution Adjustments

Required solution adjustments due to simplification of functionality, causing conversion/re-implementation
and custom code change.

# S/4HANA Functionality Changed in S/4HANA SAP Notes

2265093
2210486
New business partner approach; customer/vendor 2344034
1 Business Partner
integration (CVI) 2211312
974504
2363892
2267306
2198647
2 Data model changes in SD Simplified data model in Sales & Distribution
2224436
2229342
2267308
Table KONV was replaces in its data persistency role by
3 Data model changes in SD Pricing 2313318
the new table PRCD_ELEMENTS
2220005
Credit management FI-AR-CR Credit Management is not longed supported; it
2270544
4 (only new checking rule tested in is replaced with SAP Credit Management (FIN-FSCM-
2217124
Cycle 1) CR)
SD Rebates will be replaced with SAP Settlement
2267377
Management. SD Rebates will remain available for Trafe
5 Rebate processing 2226380
Promotion Management customers to ensure
2267344
compatibility
2267310
2223144
With SAP S/4HANA, on-premise edition 1610 the
6 Foreign Trade in SD/MM 2213485
Foreign Trade functionality in SD/MM is not available
2205202
2332472
2267342
2227824
Functionality not available in SAP S/4HANA (functional
7 Revenue recognition 2225170
equivalent available)
820417
2254366
Business partner data exchange between SAP CRM and 2285062
Business Partner exchange - SAP
8 S/4HANA,on-premise edition requires BAdI 2283695
CRM and SAP S/4HANA
implementation 2304337
Adoption of new output management (optional). The
NAST based old OM is still available. Customers can 2228611
9 Output management (Optional) decide on business application level which framework 2267376
(new:BRF+ or old NAST) supports their output scenarios 2267444
best
2267140
Material Number Field Length The maximum field length of the material number is able
10 2215424
Extension to extended from 18 to 40 characters
2215852
Functional changes in BOM, The Customizing for date validity is no longer considered
11 2267880
Routing, Production Version for BOM explosion
2267442
Pricing Data Model Simplification On a basic level this is relevant to Data Model Changed
12 2267308
in PUR in SD Pricing
2220005

© Lenovo 2018 10 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
Storage Location MRP is not available in SAP
13 Storage Location MRP S/4HANA. Planning on MRP area level has to be used 2268045
instead
In SAP S/4HANA, all subcontractor demands are
MRP areas for planning of planned in subcontracting MRP areas. The S/4HANA
14 2268044
subcontractor requirements MRP uses default planning parameters if MRP-area-
specific material master records do not exist
In SAP S/4HANA,the Subsequent Settlement (MM-
Subsequent Settlement - Vendor 2267415
15 PUR-VM-SET) application is replaces by the new
Rebate Arrangements 2215220
Contract Settlement (LO-GT-CHB) application
Material Ledger obligatory for 2267834
16 MM based Material valuation
Material Valuation 2194618
Material Valuation - Statistical The parallel statistical moving average valuation is not 2267835
17
Moving Average Price available in SAP S/4HANA, on-premise edition 2277568
The relevant fields in Foreign Trade is supported by GTS
18 Foreign Trade in Material Master from S/4HANA 1610 release onwards and not through 2267225
Material Master
2267138
19 Product Master Table Simplification Product Master Table T130F
2324325
The MRP functionality has been optimized in Material 2267246
20 MRP in Material Master
Master for S/4HANA for simplification purposes 2224371
21 Simplified IM data model Simplified inventory management data model 2206980
Deprecation of MM-PUR WebDynpro Applications.
MM-PUR WebDynpro Web Dynpro Applications of SAP ERP Materials 2267445
22
Applications Management (MM) are not supported with SAP 2228621
S/4HANA any more
Supplier Invoice Authority
23 Change of Authority Concept for Supplier Invoice 2271189
Concept

Material Valuation - no exclusive Goods movements without exclusive locking by material 2338387
24
lock by material valuation valuation 2267835

Performance optimization within Material Document

25 Material Document Processing 2319579
processing - lock behavior and stock underrun protection

© Lenovo 2018 11 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

5.3 Detailed Adjustment Approach

Before the S/4HANA conversion, we executed the SAP S/4HANA pre-check to ensure the source ECC on
any DB system is compatible with the conversion. The results of the pre-check were generated as a list of
items you need to adjust before you can start the conversion process. The overall check result return code
must be lower or equal to 4, return code higher than 4 need to be fixed before migration.
We executed seven pre-checks and more than two hundred errors were fixed in the Cycle 1 Project. The last
pre-check is within migration process.
Detailed pre-check execute method in chapter 6.2.

Part of Lenovo S/4HANA Scale out Cycle 1 Pre-Check Result

Once the S/4HANA Scale out conversion SUM finished, further functional post activities are required. All
after system conversion actions in the following action lists need to be done in the target S/4HANA Scale out
system.

1> Business Partner

- Description:
Business Partner is the leading entity in SAP S/4HANA. Customer and vendor master record creation,
maintenance and display is only possible via the business partner functionality. All transactions to
maintain the classical customer/vendor master data will redirect to BP.
The customer/vendor integration (CVI) functionality enables automatic replication between
customer/vendor master records and business partner master records.
- Cleanup customer/vendor master data; archive data with deletion flag; check and ensure the
consistencies.
- Implement the BP pre-check reports according to SAP Note 2344034 and 2211312.
- Activate the business function and complete configuration of BP CVI according to SAP Note 2265093.
- Generate BP by synchronization cockpit, do the trouble shooting, adjust customizing and master data
check results.
- After the technical system conversion, activate CVI direction from BP to customer/vendor and complete
configuration.
- Check the custom code relevant to customer/vendor master.
- Reference SAP Notes: 2265093, 2210486, 2344034, 2211312, 974504, 2363892

2> SD
- The following data model simplifications have been implemented for SD area:
 Elimination of status tables VBUK/VBUP
 Simplification of document flow table VBFA
 Field length extension of SD document category
 Elimination of redundancies of document index tables
 Elimination of rebate index table VBOX
 Elimination of LIS tables S066, S067
- Adapt custom code in target system according to the custom code check results and refer to SAP note
2198647 for details.
- Reference SAP Notes: 2267306, 2198647, 2224436, 2229342

© Lenovo 2018 12 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

3> SD Pricing
- Description:
Business documents within the SAP Business Suite, such as the sales order and the purchase order, are
used to store the pricing result in database table KONV. In SAP S/4HANA, table KONV has been
replaced in its data persistency role by the new table PRCD_ELEMENTS. However, KONV is and can
still be used for data declaration purposes. It still defines the structure of the pricing result within the
application code. The content of KONV is transferred to PRCO_ELEMENTS by the automatic data
migration when moving to SAP S/4HANA.
- Carefully follow the instructions in SAP Note 2188695, 2189301 and 2220005.
- After the technical system conversion, the post-processing report PRC_MIG_POST_PROCESSING
should be run as soon possible to correct the document currency field WAERK of table
PRCD_ELEMENTS.
- Reference SAP Notes: 2267308, 2313318, 2220005

4> Credit Management

- Descriptions:
The FI-AR-CR credit management is no longer supported with SAP S/4HANA, on-premise edition 1610.
The functional equivalent in SAP S/4HANA is SAP credit management (FIN-FSCM-CR).
Generally, the business process will not change but for some use cases, new transactions need to be used
(old transactions become obsolete).
- After the technical system conversion, migration of credit management data should be done according to
attachment SAP Note 2270544 in target system.
- Complete all documents related to payment guarantee Letter of Credit and the migration of accounting
before credit management migration.
- Check the customizing of the migration result.
- Check, configure and manual migration of user exists.
- Check and adjust the credit master data and credit exposure data migration result.
- Reference SAP Notes: 2270544, 2217124

5> Rebate Processing

- Descriptions:
The Settlement Management Solution provides a single point of entry to maintain and to administrate
contract-related conditions. In general, SD Rebate Processing is not available within SAP S/4HANA. The
functional equivalent of SD Rebate in SAP S/4HANA is Settlement Management.
- Will be replaces with SAP Settlement Management. SD Rebates will remain available for Trade
Promotion Management customers to ensure compatibility. Need check status after the technical system
conversion.
- Analyze rebate processing related business processes and third-party rebate systems.
- Check whether functions of third-party systems, such as GTN and RB, can be replaced by settlement
management.
- Check and redesign the interfaces to third-party rebate systems.
- Implement condition contract functionality in S/4HANA according to attachments SAP Note 2267377.
- Close the existing rebate agreements by final settlement after validity date of agreements.
- Reference SAP Notes: 2267377, 2226380, 2267344

6> Foreign Trade in SD/MM

- Descriptions:
Currently two software services for international trade transactions: Foreign Trade and SAP Global Trade
Services (SAP GTS).
As of SAP S/4HANA, the Foreign Trade functionality will not be available because SAP GTS is the
successor for this business requirement.
For Instrastat, the functions within SAP S/4HANA can be leveraged.
For Letter of Credit, the function is planned to be covered by Treasury and Risk Management. For this
plan, TRM would be integrated with SAP S/4HANA Sales for the processing of Letter of Credit.
- Analyze and re-design the foreign trade related business processes in target S/4HANA Scale out system.
- For the currently version SAP S/4HANA 1610, letter of credit functionality is not available. Consider
LoC functionality in SAP GTS. Consider the future version of S/4HANA which includes the integration
between TRM and S/4HANA Sales for LoC processing.
- Newly implement and configure the Intrastat under ‘Governance, Risk Compliance’ to leverage the
Intrastat functions in S/4HANA.

© Lenovo 2018 13 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
- Consider how to deal with the data in tables EIKP/EIPO, which are eliminated S/4HANA because
foreign trade functionality is not available.
- Adjust the custom code related to the eliminated objects in foreign trade, such as EIKP/EIPO.
- Reference SAP Notes: 2267310, 2223144, 2213485, 2205202, 2332472

7> Revenue Recognition

- Descriptions:
ERP SD Revenue Recognition is not available within SAP S/4HANA. The newly available SAP Revenue
Accounting and Reporting functionality should be used instead.
The new functionality supports the new revenue accounting standard as outlines in IFRS15 and adapted
by local GAAPs. The migration to the new solution is required to comply with IFRS15, even if no
upgrade to SAP S/4HANA is performed.
- Evaluate the current usage of SD Revenue Recognition.
- Start a pre-project of SAP RAR implementation.
- Prior to the conversion SAP S/4HANA, migrate all sales orders processed by SD RR RAR that are: 1)
not fully delivered and invoiced; 2) have deferred and revenue still to be realized; 3) for which you
expect follow-on activities like increase quantity, create credit memo or cancel invoice.
- Reference SAP Notes: 2267342, 2227824, 2225170, 820417, 2254366

8> Business Partner Exchange – SAP CRM and SAP S/4HANA

- Descriptions:
If you have not worked with the CVI beforehand, you need to activate it and generate business partners
before converting your system to SAP S/4HANA, on-premise edition.
A Business Add-in (BAdI) implementation has been provided to ensure that the mass synchronization
does not generate new GUIDs instead of using the existing GUIDs from the CRM mapping tables.
In addition, you have to make settings to set up the business partner data exchange between SAP
S/4HANA, on-premise edition.
- Implement the check reports in SAP Note 2304337.
- Cleanup the BPs with wrong GUIDs according to check results ‘CVI_CRM_MAPPING’.
- Before CVI synchronization, implement SAP Note 2283695 to ensure that the mass synchronization does
not generate new GUIDs instead of using the existing GUIDs from CRM mapping tables CRMKUNNR,
CRMPARNR, and CRMLIFNR.
- Complete the settings described in SAP Note 2285062.
- Reference SAP Notes: 2285062, 2283695, 2304337

9> Material Number Field Length Extension

- Descriptions:
The material number field length has been extended from 18 to 40 characters.
The appropriate related SAP development entities (domains, data elements, structures, table types and
transparent tables, external and internal interfaces, user interfaces, and so on) have been adapted
accordingly. Where required, automated logic is in place and executed automatically in case a customer
converts his current SAP Business Suite system into SAP S/4HANA.
The default setting, both after the move to SAP S/4HANA and for new installations, is that the extended
material number functionality is NOT activated. To use a material number with 40 characters, the
customer needs to activate this functionality.
- Execute the related conversion pre-checks and custom code migration worklist to get the detailed
information about potentially required custom code adaption effort in source ECC on any DB system.
- Reference SAP Notes: 2267140, 2215424, 2215852

10> BOM, Routing, Production Version

- Descriptions:
The Customizing for data validity is no longer considered for BOM explosion. Instead, only BOMs with
valid production version are considered during BOM explosion. Therefore, it is now mandatory for
Manufacturing BOMs to maintain the product version for correct BOM explosion.
- Additional test effort for data migration and testing required. More details are available in SAP Note
2267880.
- It is recommended to maintain product versions using the report Product Version Migration for BOM
(transaction code CS_BOM_PRODVER_ER_MIGRATION), as for more compatible for the Lenovo it is
recommended to improve standard report CS_BOM_PRODVER_MIGRATION.
- he customizing that determines the items valid for BOM explosion now has default value ‘2’ (Version
with latest The customizing that determines the items valid for BOM explosion now has default value ‘2’

© Lenovo 2018 14 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
(Version with latest valid-from date). This customizing is available in Define Modification Parameters
under Production -> Basic Data -> Bill of Material -> Control Data for Bills of Material.
- Reference SAP Notes: 2267880

11> Pricing Data Model Simplification in PUR

- Descriptions:
In SAP S/4HANA, table KONV has been replaced in its data persistency role by the new table
PRCD_ELEMENTS. However, KONV is and can still be used for data declaration purposes. It still
defines the structure of the pricing result within the application code.
Several data elements have been extended, especially the key field ZARHK in table KONV with the data
element DZAEHK.
The maximum number of possible accesses in an access sequence (DTEL KOLNR) has been increased
from 99 to 999.
- In Lenovo customer execute conversion pre-check class CL_S4_CHECK_PRICING (Note 2188735)
after check system show the table KONV has been enhanced and follow the instruction in SAP note
2189301.
- Lenovo also follow the instruction in “how to guide” included SAP note 2220005 adapt object and code.
- Run report PRC_MIG_POST_PROCESSING (more detail see Note 2267308 and 2220005).
- Reference SAP Notes: 2267442, 2267308, 2220005

12> Storage Location MRP

- Descriptions:
In SAP ERP, storage locations can be excluded from MRP planning or they can be planned separately
from other storage locations. In the latter case a reorder point procedure with maximum lot size is used
which triggers transport reservations to fill up the storage location.
MRP areas cover the very same business requirements. Materials with MRP-area-specific MRP type
‘ND’ (no MRP) can be used instead of materials with a storage location excluded from MRP. Materials
with MRP-area-specific MRP type ‘VB’ (reorder point planning) can be used instead of materials with
separately planned storage locations. The storage location functionality is a subset of the MRP areas
capabilities.
- During Lenovo conversion Pre-Checks system raise an error because storage location MRP is used in the
source ERP system. Then run report MRP_AREA_STORAGE_LOC_MIGRATION if the pre-checks
detect that storage location MRP is used. The report first some prerequisites like MRP types, lot-sizing
procedures, and MRP area in customizing. Then the report generates material master records for planning
on MRP area level using the storage location material records. After the report was performed, planning
is done on MRP area level, also if performed on the start release.
- After testing the report MRP_AREA_STORAGE_LOC_MIGRATION, Lenovo create a new report to
improve MRP_AREA_STORAGE_LOC_MIGRATION’s selection screen and performance.
- Reference SAP Notes: 2268045

13> PP-MRP-Subcontracting
- Descriptions:
In SAP S/4HANA on-premise edition 1610, the 4.0 logic (separating subcontracting demand and stock
into single subcontracting planning sections and planning uncovered subcontracting demand together
with internal demand in the make-to-stock planning section in ERP) was removed while the 4.5 logic
(Planning separately the demand of every subcontractor by means of subcontracting MRP areas,
available from SAP ERP release 4.5) was simplified. The SAP S/4HANA MRP uses default planning
parameters if MRP-area-specific material master records do not exist. You only have to create an MRP
area for every subcontractor. It is still possible to create MRP area/supplier-specific material master data
if required.
- If have several subcontractors requiring the same component materials and if do not yet use MRP areas to
plan the required components then proceed as follows:
1> Create MRP areas for every subcontractor (can be done before or after upgrade)
2> Run regenerative MRP after the upgrade
- Reference SAP Notes: 2268044

14> Subsequent Settlement – Vendor Rebate Arrangements

- Descriptions:
In SAP S/4HANA, the Subsequent Settlement (MM-PUR-VM-SET) application is replaced by the new
Contract Settlement (LO-GT-CHB) application. For this reason, the functional scope of subsequent
settlement has been restricted, which means in SAP S/4HANA it is no longer possible to create new

© Lenovo 2018 15 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
rebate arrangements using transactionMEB1 and extend existing rebate arrangements using transactions
MEBV/MEB7/MEBH.
In SAP S/4HANA, Contract Settlement replaces Subsequent Settlement, which means that existing
rebate agreements can only be processed up until the end of the validity date of the agreement and must
then be closed by a final settlement. Afterwards new agreements can only be created based on condition
contracts.
- In Lenovo there are no direct activities required for continuing the business process subsequent
settlement, with the only exception that the agreements have to be closed after the end of the validity
period.
- Reference SAP Notes: 2267415, 2215220

15> Material Valuation in Material Ledger

- Descriptions:
In SAP S/4HANA, material valuation in ML is obligatorily, which can valuate material with multiple
currencies and parallel valuations. In addition Material Ledger is a base prerequisite for the use of Actual
Costing. Even though Material Ledger is become obligatorily active, Activation of Actual Costing is still
optional. See SAP Notes 2267843.
- Conversion pre-check 2194618 and 2129306.
- Customer code changed, see SAP Notes 1804812.

16> Material Valuation – Statistical Moving Average Price

- Descriptions:
The parallel statistical moving average valuation is not available in SAP S/4HANA, on-premise edition.
Deactivation of the statistical moving average is not mandatory in SAP S/4HANA.
- If within custom code the fields mentioned above under “Description” are evaluated for materials with
price control “Standard”, then this usage should be removed. One possible reaction to this change could
be use instead of the V-Price (VERPR) either the S-Price (STPRS) or the V-Price (VERPR) depending
on the configured price control for the respective material.
- To identify such locations, it is required to make use of the where-used functionality of transaction code
SE11 to consider other techniques like transaction code CODE_SCANNER to find locations which SE11
cannot handle - such as dynamic programming or native SQL statements.
- Finally, the report SAPRCKM_NO_EXCLUSIVELY_LOCKING can be used to deactivate the statistical
moving average price. This can be done for converted systems running the S/4HANA on-premise edition.
In the S/4HANA cloud edition or new installs of the SAP S/4HANA on-premise edition, the statistical
moving average price is disabled by default.
- Reference SAP Notes: 2267835, 2277568

17> Foreign Trade fields in Material Master

- Descriptions:
The following mentioned fields for Letter of Credit/Legal control/Export control/Preference management
in Foreign Trade is supported by GTS from S/4HANA 1610 release onwards and not through Material
Master.
 CAP product list no. (MARC-MOWNR)
 CAP prod. Group (MARC-MOGRU)
 Preference status (MARC-PREFE)
 Vendor decl.status (MARC-PRENE)
 Exemption Certificate (MARC-PRENC)
 Exemption Cert No.9 (MARC-PRENO)
 Iss.date of ex.cert (MARC-PREND)
 Military goods (MARC-ITARK)
- In future need to consider the fields migration corresponding in GTS.
- In future need to adapt the customer code relevant fields.

18> Product Master

- Descriptions:
Table T130F (Table of Field attributes) does not have delivery class E (E=control table, SAP and
customer have separate key areas). In SAP Business Suite the delivery class of table T130F is G
(G=Customizing table, protected against SAP Update, only INS all).
- Implement note 2324325 to generate the table T130F_C.
- Implement note 2323185 to run report RMMT130F_CPY.

© Lenovo 2018 16 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
19> Supplier Invoice Authority Concept
- Descriptions:
The previous concept was based on checking header data against the item authorization object for all
items. The system checked for all items if a user was allowed to complete certain activities in the plants.
With the new concept, it introduces a header authorization object that enables the system to perform the
following authorization checks.
- Check header data against the header authorization object (M_RECH_BUK). This authorization object
checks the common activities a user performs for the header company code.
- Check item data against the item authorization object (M_RECH_WRK). This authorization object
checks the common activities a user performs for the plant for the respective item.

© Lenovo 2018 17 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
6. Technical Adjustments
6.1 SAP Release Requirements
For the Cycle 1 test, we used the following SAP software components and release levels:
- SAP S/4HANA 1610 FPS 02
- SAP S/4HANA Server (incl. component S4CORE 101)
- SAP NetWeaver 7.51 for S/4HANA, on-premise edition
- SAP HANA 2.0 (rev 2.00.011)

6.2 Preparation before S/4HANA Scale out conversion

The following steps need to be done before the conversion:
- Check source system according to S4H Conversion Guide Chapter 3.6 Preparing Conversion.
- Apply SAP Note 2182725 – S4TC Delivery of the SAP S4HANA System Conversion Checks.
- Check whether third-party add-ons are not supported by S/4HANA.
Refer to SAP Notes 2308014, 2214409, 2302601, 2392527.
- Execute Maintenance Planner generating stack. Download all patch packages and upload to source
system server.
- HANA check referring to SAP Note 2329005.
- Check whether HANA installed LCAPP and APL correctly.

6.3 Adjustments during S/4HANA Scale out conversion

1> Implement and run the latest sizing report in source system. Depending on results, perform the scale-out
landscape planning.
2> Apply SAP Note 2182725 – S4TC Delivery of the SAP S4HANA System Conversion Checks and all
attached related notes.
3> Execute report R_S4_PRE_TRANSITION_CHECKS and fix issues. The overall check result return code
must be lower or equal to 4. Otherwise the Software Update Manager (SUM) will not be able to perform
the conversion of your system.
4> During conversion the report R_S4_PRE_TRANSITION_CHECKS will also run twice which takes
around 40 hours based on current data volume. Note 2330063 should be checked and T130F must be
processed in Client 000 and Client 001 as well or as well or it will fail during SUM and rerun the check
take another 40 hours.
5> In the Extraction step, make sure you deselect the Execute Landscape Reorg option.
6> Set a breakpoint at the SUM phase EU_CLONE_MIG_UT_RUN and continue executing SUM until the
breakpoint is reached.
7> Create a table from HDB_ESTIMATES.TXT according to note 2408419, and HDB_ESTIMATES.TXT
is located in the <dir_put>/tmp directory. The default is /usr/sap/<SID>/SUM/abap/tmp.

6.4 Conversion – Main phases of Standard Approach

The following graphic depicts the sequence of the project phases.

© Lenovo 2018 18 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
First test runs usually require more time for execution and downtime than final runs. The main reasons are:
customer specific data, configuration or developments, SAP errors that required note corrections. Secondly,
outline areas to optimize and estimate the size of required efforts.

6.5 S/4HANA Scale out table redistribution

The SAP Note 2408419 defines the initial grouping, some tables are grouped according to the S/4HANA
design, and some master tables are defined as a synchronous replication (STR) group, which will be
replicated to all nodes to avoid cross-node joins in SQL statements.
Steps for performing HANA scale out table distribution:
a) The Software Update Manager (SUM) automatically stops in phase REQ_SCALEUP_PREREQ.
b) Create table placement rules using TABLE_PLACEMENT_SQLSCRIPT.TXT attached in
2408419.
c) Continue executing SUM until reach the breakpoint in SUM phase EU_CLONE_MIG_UT_RUN.
d) Create a table for importing data from HDB_ESTIMATES.TXT as SAP Note 2408419.

e) Create predefined table groups and write metadata to tables by running the SQL script
TABLE_GROUP_SQLSCRIPT.TXT in 2408419.
f) Run table redistribution. _SYS_RT.TABLE_PLACEMENT and
_SYS_REPO.SCHEMAVERSION privilege required for table distribution.
g) CALL REORG_GENERATE(8, ‘<SCHEMA>.HDB_ESTIMATES’);
h) CALL REORG_EXECUTE(?)
i) Check table distribution result:
SELECT * FROM M_TABLE_LOCATIONS; -- for table distribution
SELECT LOCATION, SUM(ESTIMATED_SIZE)/1024/1024/1024 AS GB_SIZE
FROM (SELECT DISTINCT(TABLE_NAME), LOCATION
FROM M_TABLE_LOCATIONS) A,
“<SCHEMA>”.”HDB_ESTIMATES” B
WHERE A.TABLE_NAME=B.TABLE GROUP BY LOCATION; -- for data size distribution
SELECT * FROM SYS.REORG_OVERVIEW -- for reorg result
SELECT * FROM REORG_STEPS -- for reorg details
j) Continue to run SUM.
First round landscape reorg is based on table created according to the SAP note 2408419, landscape reorg will
based on the size of each table to ensure installation and migration can be done successfully. After that step,
we still observed cross node joins and we did not see the best performance.

-
- Principle of SAP S/4HANA Scale out Table Distribution

© Lenovo 2018 19 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

Cross-Node Joins Observed in first Round Performance Test

6.6 SAP S/4HANA Scale Out table redistribution after first cycle performance test
After the first cycle performance test, we perform the S/4HANA scale out table redistribution and replication
to eliminate cross-node join according to SQL plan cache of the performance test.
The steps for performing HANA scale out table redistribution are:

a) Set the table redistribution parameter with the script TABLE_REORG_PARAMETERS.TXT in

2408419
b) Execute the latest report SHDBSO_TABLE_GROUPING in 2447004:
Using S/4HANA variant
For OSTR: maximum size = 500.000.000 (ignore the (MB) in the screen, size is given in byte in the
HANA Plan Cache).
Set Flag at “Save groups/info to file”, so that we can analyse the Grouping after execution
c) Add ALTER TABLE “MARD” ADD SYNCHRONOUS REPLICA AT ALL LOCATIONS to the
script generated
d) CALL REORG_GENERATE(6,’’);
e) CALL REORG_EXECUTE(?);
f) Execute SELECT STATUS FROM REORG_OVERVIEW WHERE REORG_ID = (SELECT
MAX(REORG_ID)FROM REORG_OVERVIEW) to check whether the reorganization is finished.
we execute the report SHDBSO_TABLE_GROUPING in 2447004 to generate table regroup and the
synchronous replication statement. We apply the latest note version.

After table regrouping, within selected scenarios, we saw no more cross node joins.
After the final performance test, we save the table grouping and distribution as reference for future production
migration.

This is the part of table regroup / replication script:

© Lenovo 2018 20 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

Main functional table location before and after redistribution

* Most table location node
The split of the general ledger and workflow between node02 and node01 is subject to further investigation in
the future.

6.7 Reference Documentation

2328543 - Add. Info on converting to SAP S/4HANA using SUM SP19
2381765 - SAP HANA: Additional information - Software Update Manager 1.0 SP19
2328517 - Database Migration Option (DMO) of SUM 1.0 SP19
2328500 - Central Note - Software Update Manager 1.0 SP19 [lmt_005]
2197259 - Add. Info on the update/upgrade to SAP NetWeaver 7.5
2389794 - SAP S/4HANA 1610 - application specific notes in system conversion preparation phase
2389807 - SAP S/4HANA 1610 - application specific notes in system conversion follow-on phase
S/4 Conversion Guide: https://websmp109.sap-ag.de/~sapidb/012002523100003738842016E
DMO Guide: https://websmp102.sap-ag.de/~sapidb/011000358700000950402013E

© Lenovo 2018 21 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
7. Custom Code Adjustments
7.1 Required Adjustments in Custom Code
Mandatory changes in custom code include:
- Changes driven by Lenovo
- Changes driven by data model conversion or / re-implementation of functionality used.
- Changes driven by usage of obsolete objects in functionality not used.
- Function Specification of changes to be provided by Lenovo.
Readiness Check and additional Code Inspector Checks need run to refine the results for data model
conversion, in particular the effect of the long material number. (See SAP Notes 2271900, 2272014 and
2275317)
In the Lenovo S/4HANA Scale out Cycle 1 project, only custom objects mandatory for the test scope changed
to drive down the effort for custom code adjustments significantly.
This can be done by performing a SCMON recording for the test scope in SAP Solution Manager, resulting in
a list of all custom (and partner objects) touched by the test scope. This list then would be matched against the
list of affected objects from the custom code analysis for S/4HANA (results of Readiness Check and
additional checks mentioned above).

7.2 Modification Overview

The SAP System provides a comprehensive infrastructure for business computing. To streamline business
processes, however, it may be required to make changes to the standard. It can enhance, modify or reduce the
functions provided for a specific environment.
When making changes to the SAP standard, the first step is to determine which type of change best suits your
needs.
There are several ways of how you can change the behavior of the standard system:
- Customizing & Configuration
- Personalization & Adaptions
- Enhancements & Extension & Integration
- Modification
- Customer Developments & Compositions

Customizing, Personalization and Enhancements are features to implement changes on the SAP standard
getting the full support of SAP tools. Modifications and Custom Development are changes in the SAP
standard with minimal SAP tool support. This minimal tool support leads to higher costs for maintenance and
may be a deterrent for technological changes.

© Lenovo 2018 22 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

7.3 Modification Steps

Modification required by HANA migration and S/4HANA data model simplification. Multiple dimension
checks needed to find out all the impact objects, which were not all adjusted within this project since only one
PC end-to-end scenario and eight key report scenarios are in validation scope, but definitely needed in future
production implementation.
- Multiple dimension checks before migration to determine system overall modify list.
- SPDD/SPAU identified objects listed in the table below need to be modified for the HANA migration
and the S/4HANA data model simplification.
- Need to develop tools for large number object modification (25 tools for data objects adjustment).
- Analyze the massive program for debugging and modification due to model simplification, interface
change and standard functionality adjustment.
- Investigate the performance issue due to DB access difference between row and column, table join.

SPAU/SPDD Identified Objects

© Lenovo 2018 23 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
8. Performance Test Result & Analysis
8.1 Testing Scope
- 1 end to end PC Sales outbound scenario (OLTP)
- 8 key standalone report scenarios (OLAP)
- 2 performance tests:
Any DB: Response time of ECC on any DB copied from ECC production system
HANA: Response time for S/4HANA Scale out (HANA migration + functional adjustment + HANA
table regroup)
- For S/4HANA Scale out, the defined objective is that the business transactions run similar or faster than
on the legacy system landscape.

8.2 Data Volume

Compared to the data volume of ECC on any DB, S/4HANA Scale out data volume was reduced by 77.5%.
- Source ECC on any DB: 38TB
- S/4HANA Scale out after migration: 5.75TB
- S/4HANA Scale out after function post activity: 6.09TB
- S/4HANA after HANA table redistribution & replication: 8.54TB
The HANA data volume size were collected as backup files size.
- Node01: 3.24TB Node02: 5.09TB Node03: 0.17TB
For the future distribution, we need to investigate, whether we can move to two nodes, because the third node
only contained 170 GB of data. Obviously, a comparison of row versus column data is needed and other
aspects like table joins or functional requirements.
Also, Node02 carries roughly 5 TB. This violates the generic rule of SAP to utilize the SAP HANA nodes to a
maximum of 50% memory space. The other 50 % is supposed to be available as work space. In a production
setup this needs thorough attention under actual workload conditions and possibly adjustments.

-
- Data Volume before and after

8.3 System Performance

In the project, one end-to-end PC sales outbound scenario and eight key report scenarios are verified. All
selected scenarios work with S/4HANA Scale out on current infrastructure and data. We would like to have
further test on an extended scope in the future.

We observed HANA Node02 to be higher utilized than the other nodes. The detailed data from the SAP
HANA node to the filesystem on DSS-C is as follows:
a. Average read I/O: 80 MB/s, max read 2.63 GB/s
b. Average write I/O: 22 MB/s, max write 840 MB/s
c. CPU utilization: max 80%
d. Memory high watermark during the test cycles 2.9 TB
Since this was a functional test rather than a stress test, the system performance data only indicates the
resource usage, not the system capability. In a project step “cycle 2” the real workload has to be tested and
investigated on a larger scale.

© Lenovo 2018 24 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

8.4 Functional Test Results for transactional use cases

While we cannot disclose the detailed test results, the overall impression was positive.
- 43% (6 of 14) transactions better than any DB
- 36% (5 of 14) transactions close to any DB.
- 21% (3 of 14) transactions worse than any DB
- Improved = (any DB response time – HANA response time) / HANA response time

Runtime comparison for online transactions

8.5 Functional Test Results for analytical use case

While we cannot disclose the detailed test results, the overall impression was positive.
- 75% (6 of 8) reports better than any DB
- 25% (2 of 8) reports worse than any DB
- Improved = (any DB response time – HANA response time) / HANA response time

Runtime comparison for reporting transactions

© Lenovo 2018 25 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO

8.6 Lessons learned regarding Networking and Converged Storage Setup

Especially important for transactional scale-out systems is the networking performance as this directly
translates to overall transaction performance on HANA application level. We carried out proper tuning of the
network with separate validation. This comprises both Linux networking kernel and driver level tuning. On
kernel level the well-known tuning for high-speed networks were implemented (enable window scaling,
increase send and receive buffer size, increase the number of listening sockets for incoming connection
requests from its default value of 128, enable fast recycling of TCP sockets). In addition, SAP HANA can be
tuned for a higher network throughput. They are set in the communications section of the global.ini file.
Starting with HANA 2.0 SPS01, these parameters should be included by default. To reduce latency, we set
‘maxchannels=30000’ and ‘maxendpoints=30000’. Those two parameters should be set to the same value
because they match the sender to the receiver side. Additionally, ‘tcp_backlog’ was increased to 2048, the
maximum value, in order to serve more parallel requests than the default of 128 connections. Nevertheless,
the widely known Linux TCP/IP stack has its limitations and thus it will be inevitable for SAP HANA to
evaluate alternative modern networking stacks that offer lower latency and higher throughput that bypass the
kernel and/or reduce the number of the context switches per transfer.

We can gain a lot of performance on the DSS-C storage nodes by enabling the newly introduced multi-
queueing feature of the Linux SCSI subsystem. This was especially beneficial since SSDs support a highly
parallel access and can sustain higher random IO than spinning disks (for NVMe-based environments this
tuning will not be required because the Linux NVMe subsystem has inherent support for parallel I/O to be
able to drive all 64K I/O queues that NVMe devices offer by design).
The enablement of jumbo frames is essential to achieve close-to-wire speed throughput. The setup used an
OS-level frame size of 9000 bytes across both, the 40 Gbit/s and 100 Gbit/s networks. Depending on the
switch, jumbo frames need to be enabled manually there as well. Additional network performance was gained
through several network-related sysctl tunings and pinning of the Mellanox driver threads onto the right CPU
cores to ensure efficient handling of network interrupts. To validate a proper behavior of each subsystem,
several performance benchmarks were executed that stressed each component separately (iperf for
networking, fio on block devices and file system level, stream for memory performance).
The shared file system used by HANA to store binaries, log, traces, and so on, should not be used for
additional elements outside of production scope. Not storing extra files in this very same CephFS directory
reduces the performance requirements towards this shared directory, which in turn is beneficial for the overall
system performance. We recommend instead to create a separate, additional storage pool that would host
another CephFS shared file systems. This additional file system can then be managed according to its own
rules and requirements. It clearly separates HANA production data from other elements.

With the updates to SUSE Enterprise Storage version 5, which is based on the Ceph Luminous release, SUSE
provides several new features that exploit the underlying hardware even better. The bluestore feature is a key
element for Ceph internal metadata handling and brings improvements, especially for flash-based
environments, of up to and more than 100% (as seen in the Lenovo lab). All new Lenovo DSS-C
implementations require SES v5.0 and are tuned for optimal performance with the minimum amount of
storage devices in order to provide TCO values that are better than those of legacy storage infrastructures.

© Lenovo 2018 26 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
9. Summary
Lenovo continues to follow the SAP HANA adoption journey. One big step is the potential move to
S/4HANA for the central ECC system, which covers all Lenovo business transactions as a system of record.
Due to the large database size of the current system running on any DB and a legacy hardware technology, it
is necessary to design the target SAP S/4HANA system in a Scale out configuration. The Cycle 1 test
contained three major steps:

1. Migrate the data out of any DB into SAP S/4HANA

2. Distribute the data across the worker nodes, to avoid cross node joins
3. Test selected transactional and analytical business processes from a functional perspective

The result of the project is promising. The database size was reduced from 38 TB to 8.5 TB. The runtime for
the transactional business processes ran mostly faster or at the same speed than before. A few transactions are
running slower. The runtime for ¾ of analytical reports was better on S/4HANA the other ¼ still has
challenges.

With the next hardware generation on the horizon and SAP loosening the strict binding of the memory to core
ratio for SAP HANA even a smaller cluster with –for example- 2 nodes with 8 CPU sockets each and 12 TB
of main memory could provide an even easier setup and better potential of distributing the data and achieve
better performance.

© Lenovo 2018 27 Status : 10.04.2018

Whitepaper
SAP S/4HANA SCALE OUT AT LENOVO
10. Trademarks / Copyright
© Lenovo Corporation 2018. All rights reserved. References in this document to Lenovo products or services
do not imply that Lenovo intends to make them available in every country.
No part of this publication may be reproduced or transmitted in any form for purpose without the express
permission of Lenovo.

The following terms are registered trademarks of International Business Machines Corporation in the United
States and/or other countries: IBM, IBM(logo).
IBM Spectrum Scale is a trademark of International Business Machines Corporation in the United States
and/or other countries.
A full list of U.S. trademarks owned by Lenovo may be found at:
http://www.lenovo.com/legal/copytrade.html .
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
SAP, the SAP Logo, R/3 are trademarks or registered trademarks of SAP SE in Germany and many other
countries.
Other company, product or service names may be trademarks or service marks of others.
Information is provided "AS IS" without warranty of any kind.
Information concerning non-Lenovo products was obtained from a supplier of these products, published
announcement material, or other publicly available sources and does not constitute an endorsement of such
products by Lenovo. Sources for non-Lenovo list prices and performance numbers are taken from publicly
available information, including vendor announcements and vendor worldwide homepages. Lenovo has not
tested these products and cannot confirm the accuracy of performance, capability, or any other claims related
to non-Lenovo products. Questions on the capability of non-Lenovo products should be addressed to the
supplier of those products.

Lenovo, the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other
countries, or both. These and other Lenovo trademarked terms are marked on their first occurrence in this
information with the appropriate symbol (® or ™), indicating US registered or common law trademarks
owned by Lenovo at the time this information was published. Such trademarks may also be registered or
common law trademarks in other countries. A current list of Lenovo trademarks is available on the Web at
http://www.lenovo.com/legal/copytrade.html .

SAP and other SAP products services mentioned herein as well their respective logos are trademarks or
registered trade SAP.

© Lenovo 2018 28 Status : 10.04.2018