Sizing tool for SAP Business One, version for SAP HANA™
The sizing tool can help you quickly determine if your prospect is a fit for SAP Business One, version for SAP HANA™. The two key influencing factors are database size and trans
○ The available RAM space of SAP HANA server hardware must at least be greater than the expected growth of the customer database in 3 years.
○ The number of transactions in the various application components and the data load must be taken into account.
The transactional volume in combination with the number of company databases determines the scalability of the system.
Follow the steps below to determine if your prospect is a fit for SAP Business One, version for SAP HANA™
STEP ONE: Determine database (memory) size
○ Enter the transactional data for all company databases in the yellow cells :
Number of documents per day of all companies (for definition, see cell comment) 2700
Number of lines per document - (select 1 .. 500 lines) 14 Lines
Working days per year 312
Number of company database (HANA database schema) 8
Number of Max Concurrent Users 60
Initial memory used by Linux, HANA and B1ah services (in Gigabytes) 36
Database size required after 1 year (in gigabytes) 89
Minimum server memory required after 3 years (in gigabytes) 177
If the minimum server memory required after 3 years is less than the available hardware memory size, SAP Business One, version for SAP HANA™ can be used by the
Only for existing SAP Business One customers:
STEP TWO: Determine the size of the existing SAP Business One database
Enter all companies database size (in Gigabytes) 60
Result
Minimum server memory required after 3 years (in Gigabytes) 195
Compare the database size of the customer in 3 years in gigabytes with the recommendation in the following Supported Hardware Platforms guide (currently ranging from 64 – 512
Supported Hardware Platform guide (currently range from 64 – 1024 GB RAM).
* If a specific prospect is not a fit for SAP Business One, version for SAP HANA™ according to the sizing tool, contact your Local Product Expert for further investigat
IMPORTANT:
○ Calculate
Determine the maximum the transactional
number throughput
of transactions the company will produce per hour at peak time.
○ Determine the number of company databases on the same server.
* If more than 10,000 transactions per hour at peak time are entered into all company databases, please discuss it with your Local Product Expert.
* Benchmark sheet contains the max throughput result based on internal testing. (For reference only due to enviroment of customer will be different)
* When HANA running in VMs, the throughput might be 10% slower and responding time might be 10% longer.
* VMs memory management, please reference technical papers of different VMs. For HANA itself, the memory consumption is similar to physical machine.
* When sizing multiple companies, the size of each company database should be similar. When big and small database mixed, sizing them separately to get accurate result.
HANA™ For Internal SAP and Partner use only
g factors are database size and transactional volume:
ears.
r SAP HANA™ can be used by the prospect.
uide (currently ranging from 64 – 512 GB RAM) :
oduct Expert for further investigation.
ert.
al machine.
parately to get accurate result.
MAKITA
Diario Lineas
1 Ventas Cotizaciones 120
2 Ventas Orden Venta 60
3 Ventas Entregas 70
4 Ventas Devoluciones 5
5 Ventas Facturas 80
6 Ventas Nota Credito 15
7 Ventas Nota Debito 5
8 Compras Ordenes de compra (Nac./Imp.) 20
9 Compras Ingreso Mercancia Compras 20
10 Compras Devolución Mercancia Compras 1
11 Compras Factura de compra 20
12 Compras Nota Credito Compras 1
13 Compras Nota Debito Compras 1
14 Almacen Transferencia de Stock 10
15 Almacen Ingreso Mercancia Inventario 1
16 Almacen Salida Mercancia Inventario 1
17 Tesoreria Pagos Efectuados 6
18 Tesoreria Pagos Recibidos 40
19 Tesoreria Depositos 40
20 Tesoreria Conciliacion 20
Produccion Ordenes de Fabricacion 0
Produccion Consumos de Materiales (salida) 0
Produccion Ingreso de Producto Terminado 0
Servicios Llamada de Servicio
Servicios Tarjeta de equipo
Servicios Contratos
21 Contabilidad Asientos 296
22 Contabilidad Asientos Manuales 10
TOTAL 842
Addons Terceros/ Interfaces & Otros
E-comerce Orden de Venta/ Fact Reserva.
Solpe
Aumento 30% 1100
Nota Importante:
Los Documentos son un promedio por Dia
Diario Lineas Diario Lineas Diario Lineas
0 0 0
0 0 0
0 0 0
0 0 0
1 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
1 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
0 0 0
2 0 0
4 0 0
846
For reference only due to enviroment of customer will be different
SAP Business One Application Performance Standard is a hardware-independent unit of measurement that describ
Date Technology Number of Average Dialog Response Time
Partner Benchmark (The waiting time after click
Users "Add" button)
18-Mar-14 Fujitsu 96 less than 3 seconds
12-Feb-14 Fujitsu 64 less than 3 seconds
Details Steps of the benchmark
0. Logon
1. Create customer order with 20 items
2. Choose Add
3. Create a delivery based on order
4. Choose add
5. Create invoice based on delivery
6. Choose add
7. Confirm log off
1~6 will be repeated many times.
Order:Delivery:Invoice is 1:1:1.
Each B1 client use different BP and Item
r will be different
pendent unit of measurement that describes the performance of a system configuration in the SAP Business One environment.
TPH Operating RDBMS Release Business One
Trans. per Hour System - Release
(300 TPH means add 100 sales order, 100 Release
delivery based on order and 100 invoice
based on delivery every hour)
29230 SUSE Linux 11 HANA Rev 69 B1 9.0 on HANA
SP2 PL10
48746 SUSE Linux 11 HANA Rev 67 B1 9.0 on HANA
SP2 PL10
SAP Business One environment.
Central Server (*) Additional Specifications Central Server Notes
Memory (GB)
Fujitsu RX300 S6, 2 Processors / 12 Cores / 24 Threads, Intel 128 Using
Xeon Processor X5675, 3.06 MHz documents
with 20 lines
Fujitsu RX300 S6, 2 Processors / 12 Cores / 24 Threads, Intel 128 Using
Xeon Processor X5675, 3.06 MHz documents
with 5 lines
