1. Early watch report
Hi,
I found the following items in red in the early watch report
Database Administration
1.
Backup Frequency
2.
Free space in tables
Security
1.
Security related SAP notes
Service preparation of YBP
1.
BW statistics
2.
Weekly workload missing
What should be my response to each item from BW perspective. And do i need to consider the items
in yellow too.
response
Freeing Table space is not exactly what you are supposed to do, but deleting PSA & the Change Log
should be done by you. This also frees up some space.
With the help of BW statistics, you can see which Query is taking long to execute. So you may have
to fine tune it to improve the query performance.
Here you can also see the loads where maximum time is taken. You may have to investigate why this
is happening. See if you can improve the load performance.
If there are some DSO which are not required for reporting, remove the BEx flag from the settings &
improve the load timing.
D/b maintenance should be taken care by the BASIS. So you will have to communicate that to the
concerned team.
Similarly, security related issues should be communicated to the Security team (if its different from
the Basis team).

2. Response Times: Rough Guide
Definition
The following times provide you with an overview of the optimal response times in your SAP system. You
can display the current workload overview for your system with the workload monitor.
Proportions of the Response Time
Performance Data
Time
Average response time
Around 1 second (dialog), < 1 second (update)
Average CPU time
Around 40% of the average response time
Average wait time
< 1% of the average response time
Average load time
< 10% of the average response time
Average database time per dialog step
Around 40% of the average response time
1.
The operating system can affect these values by up to around 10%.
2.
The ratio of the CPU time to the total time should not fall under 5%. A smaller proportion
could mean that there is an input/output bottleneck or that a database overload has
caused long wait times.
3.
The average response times for dialog transactions (online transactions) should not be
more than a second, since a higher value would strain the patience of the user too much.
Times for Database Access
Database Access
Time
Direct read
< 10 ms
Sequential read
< 40 ms
Changes
> 25 ms
Possible Causes of Bad Response Times
High Value For
Possible Causes
DB request (Change/Comm.)
Problems with database or index
Load time
Buffer too small
Transports to the productive system
Wait time
Insufficient work processes
Inactive update
Incorrect operation mode
Locked tasks
Long-running transactions

3. 1.
In a database system that is functioning properly, the times for direct reads and changes
should not be more than 10 milliseconds.
2.
The time for sequential reads should not be more than 30-40 milliseconds.
Workload Monitor start page
Workload Monitor
Purpose
You can use the workload monitor (transaction ST03) to analyze statistical data for the ABAP kernel. If you are
analyzing the performance of a system, you should normally start with the workload overview. You can also display
the total values for all instances, and compare the performance of particular instances over a period of time. A wide
range of analysis views and data helps you to find the source of performance problems quickly and easily.
You can use the workload monitor to display the following, among other things:
●
Number of instances configured for your system
●
Number of users working on the different instances
●
Response time distribution
●
Distribution of workload by transaction steps, transactions, packages, subapplications, and
applications
●
Transactions with the largest response times and database time
●
Memory usage for each transaction or each user per dialog step
●
Workload caused by RFC, broken down by transactions, function modules, and destinations
●
Number and volume of spool requests
●
Statistics about response time distribution, with or without the GUI time
●
Optional: table accesses
●
Workload and transactions used by users, broken down by users, accounting numbers, and clients
●
Workload generated by requests from external systems
The following applies to all of this data:
●
You can display data for any instance (not only the instance that you are logged onto), or optionally
summarized for all instances.
●
Depending on the user mode, you can choose the period for which you want to display data between
day, week, and month, or specify the Last Minutes’ Load as you require.
●
For most analysis views, you can display all or only certain task types.

4. Features
The workload monitor has an interface that is divided into two parts. Use the tree structures on the left to make the
following settings:
●
Select the user mode
●
Select the period for which you want to display the workload
●
Select different functions and analysis views (which data do you want to display?)
The system then displays the result on the right in a standardized ALV Grid Control. You can use this to:
●
Adjust the layout of the data output
●
Find any information using sort and filter functions
●
Save user-specific views
●
Display statistics graphically
More information:
Operating the Workload Monitor
Configuring the Workload Monitor
Gap Analysis:
Without knowing where you are, it is hard to decide where to go. A Gap Analysis report assesses
your current compliance to a given standard. Based upon a visit to your company we will prepare a
detailed report about areas that need attention and/or development and make recommendations
on actions to take to become compliant.
If you know that you would like assistance in your registration efforts do not go though this added
expense. Clients who select our Accelerated Registration Program do not need a Gap Analysis since
everything that is needed for registration is included in that program; ensuring that any gaps are
filled.
If you are unsure of your needs, or where you stand, we recommend that you do get an outside
opinion via a Gap Analysis. Do not wait for the Pre-Audit or a Registration Audit to find out your
approach is incomplete or incorrect. That is an expensive way to discover your problems and
moreover the Registrar can not consult and tell you what you can do to solve any problems. All they
can do is point the problems out.
A Gap Analysis report is not for everyone, but it can play an important role in your registration effort
to both guide your activities early on and give you assurance in your approach