It is an exercise carried out by Basis consultant with the help of the customer business process owners, Project Manager and Hardware vendors (IBM, HP, SUN, DELL). It is used to determine the CPU's, Storage (Hard disks) and Memory.
SAP Provides quick sizing toll (http://service.sap.com/sizing)
Goto> Sizing tool > Click on Quick sizer
It will be opened on new window
Provide customer number, Provide Project name and create a Project for sizing.
1. Provide Customer details to SAP
(Name of the contact, Email Id, FAX)
2. Platform and communications
3. OS, DB, Mirroring, RAID, CLUSTERING
Standby server or do you need any suggestions.
Note: Legacy database size (get the details from customer what amount of data they are planning to migrate into SAP, Example Customer Database size is 400GB but they want to migrate 250GB into SAP (Customer, Vendor, Supplier, Material, Address, FI Transactions)
High Availability options (Time of Availability)
These are the general details that are required for sizing.
Load On the System:
Users work on the system on various modules
MM - Logistics
SD - Sales
FI - Financial
40% More to the sizing result.
SAP's - SAP Application Benchmark for Performance Standards)
It is calculated in terms of Hardware vendors provide CPU in terms of the CPU's
Eg. IBM P Series generates 800 SAP's/ CPU.
IBM - DB2 [AIX O/s - DB2 Database]; I Series V5R4 - DB2]
SAP - MAXDB
SQL Server - Microsoft
P Series, X Series (I Series V5R4) is the O/s
Clustering (Mechanism : PING PONG)
DD02L - ALL Sap tables will be stored
SQL>Select bname, mandt from SAPSR3.USR02;
SAPSR3 - Database schema owner
SAPSR3DB - JAVA
Sizing is performed by quick sizer which is proprietary by quick sizer which is proprietary tool of SAP. Sizing is based on the following.
1. High Availability
2. Type of Users
3. Modules used
1. High Availability
1. RAID1 - Mirroring (1:1) on disk goes down other should take over.
2. RAID5 - (5 Disks---- Util -4; 1 Spare/ Parity)
3. SAN - Storage Area Network
4. Backup - SAN
5. If disaster occurs ------ Setup DR Server in a different geographical location
6. If the connectivity fails ...... buy more leased lines from different vendors
7. If the existing server collapses -- due to power cable --- multicables -- UPS -- etc -- Generator
Network Cable --- More than one cable
CPU's -- Multiple CPUS
Memory - Hosted on Multiple slots
DISK - RAID and SAN
8. If the complete system collapses due to hardware failure use clustering -- Two Parallel systems (Used for failover or Load balancing)
Eg. IBM P-Series
Unless unlocked by IBM we cannot make use of the additional Hard Disks
Note: For Upgrade - Sizing
Capacity - Sizing
Module Selection: Select the modules that are going to be implemented like
Logistics, Financials, Product life cycle Management (Currently HR is not going to be implemented but, there is a plan to implement in future, If it before three years consider HR in sizing if not.
1. User - 480 Dialogue Steps with the system
- 40 HRS * 60 Mins
1Dialogue Step - 40*60/480 = 5 Min = 300 Sec
2. 480 - 4800 Dialogue Steps - 40 Hrs - 30 Sec
3. 480 - 14400 - 40 Hrs - 10 Secs
Eg. Purchase Order / Week - 200 * 10 Dialogue Steps = 2000.
Service Desk >
1.Need to activate some services
4. Default Host
- htmlb RT Click > Activate Service
Note: This should be done as Post Installation Steps
SPRO > SAP Solution Manager
> General Configuration
Activating BC Sets (BC- Business Configuration)
> From End user system
If any one stuck @ point executing a command SM59 > Help
> Create Mssg.
Test -- TKT No: 008000000001
The Strategy is to migrate/ upgrade the hardware for every three years. The sizing is based on
1. High Availability
2. Modules and
3. No of users
Along with legacy database and future growth of users
User Low Medium High
FI 50 250 250
CO 50 250 250
The sizing is also called as T-Shirt sizing which determines your servers as (S, XS, M, L, XL, XXL) Sizing output determines the memory, storage and CPU in terms of Saps'.
SAPS is ( SAP APPLICATION BENCHMARK FOR PERFORMANCE STANDARDS)
SAPS are calculated based on Sales module. SAP assumes that a sales order/ Purchase order consumes around 8-12 Dialogue steps. For every 2000 sales documents that are generated per hour requires 100 SAPS.
CPU cannot be arrived directly because the process speed depends upon the hardware vendor. (The hardware vendor determines the CPU Size based on SAPS example an ISeries machine single CPU generates 800 SAPS.
If the sizing output requires 3200 SAPS then we need 4 CPU's.
The Hardware resources are required for the following which needs to be considered while sizing
3. Interfaces (Like Fax, Email, SMS, Pager etc.)
5. Third party communication (Batch processing etc)
So we can consider adding 30-50% to the sizing results.
You can view more tutorials about SAP BASIS