Sizing for Transaction, Master Data, AVL, Drilldown, and SyncBack
This chapter provides information on the sizing requirements for SAP Central Finance Master Data Replication by insightsoftware for SAP S/4HANA and its components.
Sizing Guidelines
Sizing refers to identifying the hardware requirements of the Master Data Replication, such as:
- CPU processing power
- Memory
- Disk space
You can use the sizing formula to identify the hardware requirements based on the number of small, medium, and large records that are loaded from the source systems.
The general assumptions that can be considered for sizing are as follows.
Transaction record size |
0.25 KB |
Drilldown record size |
1 KB |
Retention period for data in staging database |
6 months |
The sizing formulas to calculate Daily data load (GB), number of CPU cores, Memory (GB), and Disk space (GB) are as follows.
| Sizing Formula | |
|---|---|
Daily data load (GB) |
(Document size * Monthly transaction volume) / 30 |
CPU cores |
Minimum of 4 cores + 2 cores per GB of dataload |
RAM(GB)per Core |
4GB * Number of CPU cores (calculated in the second row) |
Disk space(GB) |
|
Note: Typically, data retention in the staging database spans 6 months.
The sizing calculations for annual transactions can be performed as follows.
| Data Services Server | Staging Database Server (MSSQL) | Staging Database Server (HANA) | |
|---|---|---|---|
CPU cores/vCPU |
4 core + 2 core per 1 GB daily load |
4 core + 2 core per 1 GB daily load |
4 core + 2 core per 1 GB daily load |
RAM(GB) |
4 GB per core |
4 GB per core |
4 GB per core |
Disk space(GB) |
100 GB minimum + 0.05 GB per GB of data load |
100 GB minimum + (Monthly data volume * Data retention in Staging Database) |
100 GB minimum + (Monthly data volume * Data retention in Staging Database) |
Note: A vCPU, short for Virtual Central Processing Unit, is a virtualized unit of a physical CPU allocated to a virtual machine or cloud environment. It allows multiple VMs to share the host’s physical resources.
Sample Sizing Calculations
In the following illustrative scenario, a monthly transaction volume of 15.5 million is considered.
| Sample Data | |
|---|---|
Monthly transaction volume |
15.5 million |
Daily data load (KB) |
15.5 million / 30 = 5,16,667 KB |
Daily data load (GB): |
5,16,667/1024/1024 = 0.5 GB |
CPU cores |
4 + (2*0.5 GB) = 5 |
RAM(GB) |
64 |
Use the percentage multiplier for Master Data in the Parameters section to update the Master Data volume as a percentage of overall Transaction volume. For example, if the Master data volume is 10% of overall Transaction volume, update Master data in Parameters to 0.1. This helps you assess the overall volumes and other sizing calculations in scenarios which involve Master Data.
| Document Type with indicative size | |
|---|---|
Accounting Document Size (KB) |
1 |
Document Size AVL (KB) |
0.5 |
| Document Size for Drilldown (KB) | 1 |
| Master Data (KB) | 0.25 |
Based on the sizing calculations provided in the previous sections, annual sizing estimates are as follows:
| Data Services Server | Staging Database Server (MSSQL) | Staging Database Server (HANA) | |
|---|---|---|---|
CPU cores / vCPU |
5 |
5 |
5 / 20 |
RAM(GB) |
20 |
20 |
20 |
Disk space(GB) |
101 |
190 |
190 |
Note: For calculating annual estimations, it is important to take into account 15% year-over-year (YoY) growth in transaction volume.
A typical hardware configuration of the SAP Data Services server is as follows.
|
Small enterprise (5 Million line items/Month) |
Medium enterprise (30 Million line items/Month) |
Large enterprise (60 Million line items/Month) |
|
|---|---|---|---|
CPU cores |
4 |
8 |
12 |
RAM(GB) |
16 |
32 |
64 |
Disk space(GB) |
100 |
150 |
200 |
A typical hardware configuration of the staging database server (SQL Server) is as follows.
|
Small enterprise (5 Million line items/Month) |
Medium enterprise (30 Million line items/Month) |
Large enterprise (60 Million line items/Month) |
|---|---|---|---|
CPU cores |
4 |
8 |
12 |
RAM(GB) |
16 |
32 |
64 |
Disk space(GB) |
250 |
500 |
1000 |
A typical hardware configuration of the staging database server (SAP HANA) is as follows.
|
Small enterprise (5 Million line items/Month) |
Medium enterprise (30 Million line items/Month) |
Large enterprise (60 Million line items/Month) |
|---|---|---|---|
CPU Cores/vCPUs |
8/32 |
16/64 |
32/128 |
Disk space(GB) |
256 |
512 |
1024 |
Note: For information on SLT sizing, refer to SAP's HANA-Based Quick Sizer.