SAP Business Suite support ends in 2025, and because of this, businesses are slowly starting to realize that they need to move over to SAP S/4HANA. Conversions from SAP Business Suite to S/4HANA are already occurring, and the most significant concern for companies moving their data over is application sizing. Without proper consideration for application sizing, the efficiencies, and benefits that SAP S/4HANA offers to a business may never be fully realized. Therefore, it is of utmost importance that the company take the time and effort needed to size their installations correctly.
Speed And Responsivity Comparisons
When Hard Drive speeds had only just gotten to speeds of 7200 RPM from 5400 RPM, the speed increase was only marginal. However, as computers started running SSD drives, the responsiveness was apparent, with up to 300% speed increase. A similar situation exists with sizing an SAP installation. Business-critical functionality is a crucial concern, and having a properly sized SAP installation means faster access to data and applications as well as a more responsive system all around.
Correctly sizing for an SAP HANA installation is slightly different to traditional sizing. Businesses investing in SAP HANA need to consider the system’s need for memory, as it is a more crucial factor in sizing than CPU performance (which is what most traditional databases focus on). However, because the database results that SAP HANA delivers are in a compressed format, it can be difficult to securely tell the size of memory needed for any given SAP HANA database. Each HANA deployment has a different requirement when it comes to sizing.
Determining Sizing using the Quick Sizer Tool
SAP offers a handy utility called the SAP Quick Sizer Tool, which enables companies to get a general idea of the size their selected deployment of HANA may require. This point should be remembered by developers learning how to blog about SAP Quick Sizer Tool. The Quick Sizer can calculate CPU, I/O resources, disk, and memory requirements for a given installation. It uses throughput numbers as a basis for its calculations and can help convert business requirements into technical specifications which can be used within the SAP install. The Quick Sizer process for greenfield sizing can be completed as follows:
1) Access the Quick Sizer utility (Using the SAP HANA version).
2) Create a new sizing project – using customer scenario data for the company, we can input the details into the sizer.
3) Check available sample configurations, and come up with comparable hardware configurations based on the SAP Standard Application Benchmarks.
4) Give the project Name to the hardware vendor of choice so that they can propose the best options for hardware for the installation.
5) If the company is unable to get a sizing determination, then they can follow up with the sizing guidelines and SAP notes to get a more in-depth overview of the requirements.
Sizing a Business Suite Migration
If a company is intending to migrate its SAP Business Suite into HANA, two SAP notes provide valuable insight into the sizing process:
SAP Note 1793345 – Sizing for SAP Suite on HANA
SAP Note 1872170 – Business Suite on HANA and S/4HANA sizing report
As a bonus, these notes come with a sizing script and guidelines for its usage attached to these notes.
Approaching Sizing for a Migration
Sizing is by and large the most important aspect of any SAP S/4 HANA installation. Getting it right the first time is essential, and tools like Quick Sizer offer insights that personnel can follow up on and implement. However, if all else fails, delving into the SAP notes should allow a business to resolve its problems with sizing and approach the installation with a proper understanding of what HANA requires to perform at peak efficiency.