Database Reference
In-Depth Information
ing live with the new users. The following formula can be used to calculate the needed net-
work bandwidth for additional active users that will be added to the system:
C = X * N * D * 0.25
where:
C = Bandwidth in kbps needed for SAP GUI
X = Amount of data per dialog step in kilobytes
N = Number of active users
D = Average # of dialog steps per minute per user
0.25 = Numerical factor (includes conversion, protocol overhead, and safety factor)
Example:
C = 4.6 * 30 * 4 * 0.25
C = 138 kbps
Pitfalls to Avoid in Sizing SAP Projects
SAP sizing projects could run into some of the common pitfalls listed here. For each of the
pitfalls a mitigation plan is offered so that these can be avoided while running a sizing pro-
ject at your organization.
Customers Do It Themselves
Sizing projects are sometimes performed by customers themselves with inexperienced re-
sources, and this can lead to inaccurate sizing estimates and affect the credibility of the pro-
ject, as the system is either undersized or oversized. Undersized systems could experience
serious performance issues, and oversized systems will make organizations incur unneces-
sary cost up-front and a significant amount of the system resources could be idle. This situ-
ation can be mitigated by assigning this task to an experienced consultant who has experien-
ce helping customers with performing several SAP sizing projects.
Incorrect Understanding of Sizing Elements
The next common pitfall is incorrect understanding of the sizing element by the business
team member. The gathered throughput data is incorrect, and this renders the SAP sizing
project inaccurate. This situation can be mitigated by an experienced SAP sizing consultant
explaining the sizing element in detail using the sizing help document. This way, the
gathered throughput data is correct and will yield more accurate sizing results.
