The arrangement of a server system is known as the SAP landscape. From a customer perspective, sizing is the translation of business requirements (business throughput and user concurrency requirements) into hardware requirements. From an SAP development perspective, sizing means the creation of a sizing model for product functionality with a reasonable number of input parameters and assumptions.

Note: Sizing is not a configuration. The hardware vendor or ISP performs the system configuration to ensure that the system landscape meets the hardware requirements that are determined by sizing.

Different sizing approaches and tools are available depending on the customer scenario. The SAP HANA Sizing Decision Tree is available online, and sizing per scenario is shown in the following table:

Table 1.      SAP Hana sizing for different scenarios

More steps to reduce the minimum HANA memory requirement are available at SAP HANA Data Aging in SAP S/4HANA.

Note: Sizing SAP HANA with DRAM and persistent memory (NV-DIMM or NV-RAM) follows the same rules as sizing for SAP HANA with a pure-DRAM configuration. For more information, see Sizing SAP HANA with Persistent Memory.

For this comparison, the business suite on HANA and S/4HANA sizing report (also known as the ABAP sizing report) was used for on-premises and AWS environments. Table 2 lists the requirements for memory sizing under the following parameters and assumptions:

• Number of years projection – 3
• Database growth (year on year) – 15%
• Additional database growth (for example, new business units) – 0%
• HANA utilization – 80%
• Extra database requirement (one-time requirement) – 120 GB

Table 2.      SAP S/4HANA landscape memory sizing (in GB)

The following table shows the requirements for storage sizing under these parameters and assumptions:

• Number of years projection – 3
• Operating system – 150
• /usr/sap – 50

Table 3.      SAP/4HANA landscape storage (in GB)