SAP Sizing in brief

The following is a brief outline of how the SAPs are calculated -

SAP Application Performance Standard (SAPS): hardware independent unit
that describes the performance of a system configuration in the SAP
environment derived from the SD Standard Application benchmark
Time range: 1 hour

100 SAPS = 2.000 fully business processed order line items per hour
(creating the order, creating a delivery note for this order, displaying
 the order, changing the delivery, posting a goods issue, listing orders
, and creating an invoice)

100 SAPS =  6.000 dialog steps (screen changes), 2.000 postings per hour
 in the SD benchmark, or 2.400 SAP transactions

For BW we distinguish roughly between user types according to their
frequency of activity and the reporting they will normally do.
Active User Type  Navigation Steps per Hour  This user will
predominantly ...

- Information Consumer 1 ... view predefined and static reports
- Executive 11 ... navigate within reports, do slicing and dicing, but
  usually hit aggregates
- Power  33 and more ... run ad-hoc queries with a high probability of
  full table scans

A navigation step includes drilling down in the reports and corresponds
to nine dialog steps in the SD benchmark. If you don't know the user
distribution, a typical ratio in the BW environment is 71% : 27% : 3%
(Information Consumer : Executive : Power).

The Sizing Input Parameters which we use are:
- Number of active users (logged on in monitor and performing actions
  within one minute period)
- Number of concurrent users (this is a must entry because we need this
  to determine the memory consumption) (logged on in monitor, not
  necessarily doing anything)
- User information can be retrieved from ST03N.

SAPS = max from:
- Number of concurrent user * 25 SAPS
- Number of active user * 100 SAPS