Analysis from 16.11.2015
Until 22.11.2015
Report: PCD, Productive
Installation: 0020669062
Session: 4000000026787
EarlyWatch Alert-817961 - Metro Productivos
1 Service Summary
This EarlyWatch Alert session detected issues that could potentially
affect your system.
Take corrective action as soon as possible.
Alert Overview
We found more than 30 ABAP dumps in your system.
A high number of users has critical authorizations
Perform the following Guided Self Services.
Guided Self Service
Security Optimization Service
FAQ SAP Note
696478
For more information about Guided Self-Services, see SAP Enterprise Support Academy.
Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP
Enterprise Support Academy - Learning Studio - Calendar.
Check Overview
Topic
Topic
Rating
SAP System
Configuration
Subtopic
Rating
Subtopic
Check Overview
Topic
Topic
Rating
Subtopic
Rating
Subtopic
SAP Application Release
- Maintenance Phases
Database - Maintenance
Phases
Operating System(s) Maintenance Phases
SAP Kernel Release
Performance Overview
Performance Evaluation
Workload Distribution
Workload by Application
Module
DB Load Profile
SAP System Operating
Availability based on
Collector Protocols
Program Errors (ABAP
Dumps)
Update Errors
Table Reorganization
Hardware Capacity
Database Performance
Platform Information
Wait statistics
I/O Performance
SQL Server Configuration
Parameters
Missing Indexes
Database Administration
Database File Checks
Environment and
Operating
Error Analysis
Backup Strategy
Installation Checks
Database Server Load
From Expensive SQL
Check Overview
Topic
Topic
Rating
Statements
Subtopic
Rating
Subtopic
Expensive SQL
Statements
Database Server Load
Security
System Recommendations
(ABAP)
Default Passwords of
Standard Users
Control of the Automatic
Login User SAP*
Protection of Passwords
in Database Connections
ABAP Password Policy
Users with Critical
Authorizations
Software Change
Management
Number of Changes
Emergency Changes
Failed Changes
Data Volume
Management (DVM)
Note: All recommendations in this report are based on our general experience. Test them
before using them in your production system. Note that EarlyWatch Alert is an automatic
service.
Note: If you have any questions about the accuracy of the checks in this report or the
correct configuration of the SAP Solution Manager EarlyWatch Alert service, create a
customer message under component SV-SMG-SER-EWA.
Note: If you require assistance in resolving any concerns about the performance of the
system, or if you require a technical analysis of other aspects of your system as highlighted
in this report, create a customer message on component SV-BO. For details of how to set
the appropriate priority level, see SAP Note 67739.
Performance Indicators for PCD
The following table shows the relevant performance indicators in various system areas.
Area
System Performance
Indicators
Active Users (>400 steps)
Avg. Availability per Week
Avg. Response Time in Dialog
Task
Max. Dialog Steps per Hour
Avg. Response Time at Peak
Dialog Hour
Avg. Response Time in RFC
Task
Max. Number of RFCs per
Hour
Avg. RFC Response Time at
Peak Hour
Max. CPU Utilization on DB
Hardware Capacity
Server
Avg. DB Request Time in
Database Performance
Dialog Task
Avg. DB Request Time for
RFC
Avg. DB Request Time in
Update Task
Database Space
DB Size
Management
DB Growth Last Month
Value
136
100 %
Trend
526 ms
7856
545 ms
580 ms
1494
336 ms
18 %
140 ms
49 ms
241 ms
307.06
GB
18.27
GB
2 Landscape
2.1 Products and Components in current Landscape
Product
SID SAP Product
PCD SAP ERP ENHANCE PACKAGE
Main Instances (ABAP or Java based)
SID
Main Instance
PCD
SAP ECC Server
Databases
Product Version
6.07
SID
PCD
Database System
SQL SERVER
Database Version
2008 R2
2.2 Servers in current Landscape
SAP Application Servers
SID Host
Instance Name
Logical Host ABAP JAVA
PCD mtrprsaperp mtrprsaperp_PCD_00 mtrprsaperp
DB Servers
SID
Host
Logical Host (SAPDBHOST)
PCD mtrprsaperp
MTRPRSAPERP
2.3 Hardware Configuration
Host Overview
Hardware
Host
Manufacture Model
r
VMwar
e
mtrprsaper VMware,
Virtual
p
Inc.
Platfor
m
CPU
Memor
CPU
Virtualizatio Operatin CPU Core
MH
y in
Type
n
g System s
s
z
MB
Windows
Xeo
Server
n
240
VMWARE 2008 R2 4
4
20479
E7- 0
(x86_64)
4870
(SP 1)
3 Service Preparation and Data Quality of
PCD
Configuration hints for optional service data are provided.
The SAP ERP ENHANCE PACKAGE system PCD is fully prepared for
delivery of future remote services.
Rating
Check Performed
Service Data Quality
Rating
Check Performed
ST-PI and ST-A/PI Plug-Ins
Service Preparation Check (RTCCTOOL)
Service Data Control Center
Hardware Utilization Data
In preparation for SAP services, ensure that connections, collectors, and service tools are up
to date. These functionalities are explained in SAP Notes 91488 and 1172939.
3.1 Service Data Quality
The service data is collected by the Service Data Control Center (SDCCN) or read from the
Solution Manager's BW or Configuration and Change Database (CCDB).
This section comprehensively shows issues with the data quality and provides hints on how
to resolve them.
Explanation for 'Priority' Column In Tables Below
Prio. Explanation: Impact of Missing or Erroneous Data
An optional check was skipped.
3.1.1 Quality of Service Data in Solution Manager Diagnostics - BW
Prio.
Report Area
affected
Details and Related Infocube
SAP
Note
Workload of
ABAP System
PCD
Reading performance data from BW
returned neither data nor an error code.
A timeout may have occurred.
1332428
Infocube: 0CCMSMTPH used in section
'Workload Overview PCD'
3.2 ST-PI and ST-A/PI Plug-Ins
The table below shows the service plug-ins implemented and their releases and patch
levels. These recommendations are derived from report RTCCTOOL. For more information
about RTCCTOOL, see SAP Note 309711.
Rating Plug-In Release Patch Level Release Rec. Patch Level Rec.
ST-A/PI 01R_731 2
01R_731
2
ST-PI 740
2
740
2
4 Software Configuration For PCD
We have listed recommendations concerning the current software
configuration on your system.
Your system's software versions are checked. If known issues with the software versions
installed are identified, they are highlighted.
4.1 SAP Application Release - Maintenance Phases
SAP Product Version
EHP7 FOR SAP ERP 6.0
End of Mainstream Maintenance
Status
31.12.2025
In October 2014, SAP announced a maintenance extension for SAP Business Suite 7 core
application releases to 2025. If you are running a relevant release, see SAP Note 1648480
for more details and applicable restrictions.
4.2 Support Package Maintenance - ABAP
The following table shows an overview of currently installed software components.
Support Packages
Software
Component
Version
ACLDL
600
Latest
Patch Avail.
Support Package
Level Patch
Level
SAPK1
67001INACLDL
EA-APPL
617
5
10
SAPK61705INEAAPPL
EA-DFPS
617
5
10
SAPK61705INEADFPS
Component
Description
SAP R/3
Enterprise
PLM, SCM,
Finance
SAP R/3
Enterprise
Defense
Forces &
Public
Support Packages
Software
Component
Version
Latest
Patch Avail.
Support Package
Level Patch
Level
Component
Description
Security
EA-FIN
617
5
10
EA-FINSERV 617
5
10
EAGLTRADE
617
5
10
EA-HR
607
26
44
EA-IPPE
617
3
5
EA-PS
617
5
10
EA-RETAIL
617
5
10
ECC-DIMP
617
5
10
ECC-SE
605
12
14
ERECRUIT
617
5
8
FI-CA
617
5
10
SAPK61705INEAFIN
Ea Fin
SAP R/3
SAPKEnterprise
61705INEAFINSRV Financial
Services
SAP R/3
SAPKEnterprise
61705INEAGLTRAD
Global Trade
SAP R/3
SAPKEnterprise
60726INEAHR
Human
Resources
SAP R/3
Enterprise
SAPKIntegrated
61703INEAIPPE
Product and
Process
Engineering
SAP R/3
Enterprise
SAPK-61705INEAPS
Public
Services
SAP R/3
SAPKEnterprise
61705INEARETAIL
Retail
ECC Discrete
SAPKIndustries Mill
61705INECCDIMP
Products
ESA FAST
SAPKTRACK
60512INECCSE
(ECC-SE)
SAPKSAP E61705INERECRUIT Recruiting
FI-CA,
Contract
SAPK-61705INFICA
Accounts
Receivable
Support Packages
Software
Component
Version
Latest
Patch Avail.
Support Package
Level Patch
Level
FI-CAX
617
5
10
SAPK61705INFICAX
FINBASIS
747
5
10
SAPK74705INFINBASIS
FSCM_CCD
617
5
10
SAPK61705INFSCMCCD
GRCPIERP
V1000_700 19
20
GRCPINW
V1000_731 11
12
INSURANCE 617
5
10
IS-CWM
617
5
10
IS-H
IS-M
617
617
7
5
10
IS-OIL
617
5
10
IS-PRA
617
5
11
IS-PS-CA
617
5
10
IS-UT
617
5
10
LSOFE
600
25
27
MDG_APPL
617
5
10
Component
Description
and Payable
(virtuell)
FI-CAX:
Extended FICA
SAP R/3
Enterprise
FINBASIS
Fscm Ccd
SAP GRC
SAPKPlugIn for
10319INGRCPIERP
ERP
SAP GRC
SAPKPlug-in for
10511INGRCPINW
NW
SAPKINSURANCE
61705ININSURANC SAP Insurance
IS-CWM
SAPKCatch Weight
61705INISCWM
Management
SAPK-61707INISH IS-Hospital
SAPK-61705INISM IS Media
IS-OIL SAP
OIL & GAS
SAPK-61705INISOIL
Upstream /
Downstream
SAPKIS-PRA
61705INISPRA
IS-PS-CA,
SAPKTax&Revenue;
61705INISPSCA
Campus
Management
SAPK-61705INISUT IS-UT
Learning
SAPKSolution 60025INLSOFE
Front End
SAPKMDG
Support Packages
Software
Component
Version
MDG_FND
747
PI_BASIS
740
PLMWUI
747
Latest
Patch Avail.
Support Package
Level Patch
Level
61705INMDGAPPL
SAPK5
10
74705INMDGFND
SAPK7
13
74007INPIBASIS
SAPK5
10
74705INPLMWUI
SAP_ABA
740
7
13
SAP_AP
700
31
33
SAP_APPL
617
5
10
SAP_BASIS
740
7
13
SAP_BS_FND 747
5
10
SAP_BW
740
7
13
SAP_FIN
617
5
10
SAP_GWFND 740
12
13
SAP_HR
604
75
93
SAP_UI
740
13
14
SEM-BW
747
5
10
ST-A/PI
01R_731
2
2
Component
Description
Applications
MDG
Foundation
SAP R/3 Basis
Plug-In
PLM WUI
SAP
SAPKA74007
Application
Basis
SAP
SAPKNA7031
Application
Platform
SAP R/3
SAPKH61705
Standard
SAP Basis
SAPKB74007
Component
SAP Business
SAPKSuite
74705INSAPBSFND
Foundation
SAP Business
SAPKW74007
Information
Warehouse
SAPKSAP Fin
61705INSAPFIN
SAP
SAPKNetWeaver
74012INSAPGWFND Gateway
Foundation
SAP R/3
SAPKE60475
Standard HR
SAPKUser Interface
74013INSAPUI
Technology
SAPKSAP SEM
74705INSEMBW
Server
SAP Service
SAPKITAB9P
Tools for
Applications
Support Packages
Software
Component
Version
Latest
Patch Avail.
Support Package
Level Patch
Level
ST-PI
740
2
2
UIEAAP01
100
7
8
WEBCUIF
747
5
10
Component
Description
Plug-In
SAP Solution
SAPK-74002INSTPI
Tools Plug-In
UI for ERP
SAPKcentral
10007INUIEAAP01
Applications
SAPKSAP Web UIF
74705INWEBCUIF
4.3 Database - Maintenance Phases
Database
Version
SQL
Server
2008
End of
End of Standard
Extended
Vendor
Vendor
Support*
Support*
08.07.2014
09.07.2019
Comment Status
SAP
Note
Planned
Date
1177356
* Maintenance phases and duration for the DB version are defined by the vendor. Naming
of the phases and required additional support contracts differ depending on the vendor.
Support can be restricted to specific patch levels by the vendor or by SAP. Check in the
referenced SAP Note(s) whether your SAP system requires a specific patch release to
guarantee support for your database version.
See the "Service Pack" section in the database section for additional information.
Recommendation: Standard vendor support for your database version has already ended /
will end in the next future. Consider to order extended vendor support from your database
vendor or upgrade to a higher database version.
4.4 Operating System(s) - Maintenance Phases
Host
Operating
System
mtrprsaperp Windows
End of
End of
Standard
Extended
SAP
Status
Vendor
Vendor
Note
Support*
Support*
13.01.2015
14.01.2020
1177282
Host
Operating
System
End of
Standard
Vendor
Support*
End of
Extended
Vendor
Support*
Status
SAP
Note
Server 2008
R2 (x86_64)
* Maintenance phases and duration for the OS version are defined by the vendor. Naming
of the phases and required additional support contracts differ depending on the vendor.
Support can be restricted to specific patch levels by the vendor or by SAP. Check in the
referenced SAP Note(s) whether your SAP system requires a specific patch release to
guarantee support for your operating system version.
4.5 SAP Kernel Release
The following table lists all information about your SAP kernel(s) currently in use.
Instance(s)
SAP Kernel Patch
Release
Level
mtrprsaperp_PCD_00 742
101
Age in
Months
OS Family
8
Windows Server
(x86_64)
4.5.1 Kernel out of date
Your current SAP kernel release is probably not up to date.
Recommendation: Make sure that you are using the recommended SAP kernel together
with the latest Support Package stack for your product.
4.5.2 Additional Remarks
SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for
most products (generally 2–4 times a year). We recommend that you base your software
maintenance strategy on these stacks.
You should only consider using a more recent SAP kernel patch than that shipped with the
latest Support Package Stack for your product if specific errors occur.
For more information, see SAP Service Marketplace at
https://support.sap.com/software/patches/stacks.html (SAP Support Package Stack
information) and https://support.sap.com/patches (patch information).
For each patch there is an SAP Note in which all known regressions for this level are listed.
Find it using the keyword KRNL742PL101 in the SAP Note search. For detailed
information, see SAP Note 1802333 - Finding information about regressions in the SAP
kernel.
5 Hardware Capacity
We have checked your system for potential CPU or memory bottlenecks
and found that the hardware is sufficient for the current workload.
Note: Hardware capacity evaluation is based on hosts for which data is at least partially
available.
5.1 Overview System PCD
General
This analysis focuses on the workload during the peak working hours (9-11, 13) and is
based on the hourly averages collected by SAPOSCOL. For information about the
definition of peak working hours, see SAP Note 1251291.
CPU
If the average CPU load exceeds 75%, temporary CPU bottlenecks are likely to occur. An
average CPU load of more than 90% is a strong indicator of a CPU bottleneck.
Memory
If your hardware cannot handle the maximum memory consumption, this causes a memory
bottleneck in your SAP system that can impair performance. The paging rating depends on
the ratio of paging activity to physical memory. A ratio exceeding 25% indicates high
memory usage (if Java has been detected 0%) and values above 50% (Java 10%)
demonstrate a main memory bottleneck.
Max.
Max.
CPU
RAM Paging
Server
Date
Rating
Date
Rating
load
[MB] [% of
[%]
RAM]
mtrprsaperp
18 19.11.2015
20479
10 19.11.2015
Note: For virtualization or IaaS scenarios (for example, IBM PowerVM, VMware, Amazon
AWS, ...) it is possible that the CPU rating for some hosts is YELLOW or RED, even
though the utilization value is quite low. In this case, the relevant host could not use
maximum usable capacity due to a resource shortage within the virtualized infrastructure
(for example, IBM PowerVM: Shared Pool CPU utilization).
6 Business Key Figures
System errors or business exceptions can be a reason for open, overdue, or unprocessed
business documents or long-lasting processes. SAP Business Process Analysis,
Stabilization and Improvement offerings focus on helping you to find these documents (as
it may directly or indirectly negatively impact business).
This section provides an example of indicators, and its findings are a basis of further SAP
offerings. In the example below, the backlog of business documents is compared to daily or
weekly throughput or set in relation to absolute threshold numbers.
It provides business information to discuss possible technical or core business improvement
process potential.
SAP tools and methods can help to monitor and analyze business processes in more detail.
NOTE: Overdue or exceptional business documents are often caused by system errors,
such as user handling issues, configuration or master data issues, or open documents on
inactive organizational units or document types, that can be included in the measurements.
These documents are rarely processed further by the business departments and often do not
have a direct impact on customer satisfaction, revenue stream, or working capital.
Nevertheless, these documents can have negative impacts on other areas such as supply
chain planning accuracy, performance (of other transactions, reports, or processes), and
reporting quality.
6.1 SAP Business Process Analytics
With SAP Business Process Analytics in SAP Solution Manager, you can continuously
analyze the above key figures and around 750 additional out-of-the-box key figures for
continuous improvement potential in your SAP business processes.
With SAP Business Process Analytics, you can perform the following functions:
(1) Internal business process benchmarking (across organizational units, document types,
customers, materials, and so on) for a number of exceptional business documents and/or for
the cumulated monetary value of these documents.
(2) Age analysis to measure how many open documents you have from the previous years
or months.
(3) Trend analysis for these business documents over a certain time period.
(4) Create a detailed list for all of these exceptional business documents in the managed
system, enabling a root cause analysis to find reasons why these documents are open,
overdue, or erroneous.
SAP Business Process Analytics can help you to achieve the following main goals:
- Gain global transparency of business-relevant exceptions to control template adherence
- Improve process efficiency and reduce process costs by reducing system issues and
eliminating waste (for example, user handling, configuration issues, and master data issues)
- Improve working capital (increase revenue, reduce liabilities and inventory levels)
- Ensure process compliance (support internal auditing)
- Improve supply chain planning (better planning results and fewer planning exceptions)
- Improve closing (fewer exceptions and less postprocessing during period-end closing)
SAP also provides business process improvement methodology to help you identify and
analyze improvement potential within your business processes using Business Process
Analytics in SAP Solution Manager and visualize it for your senior management.
For more information, navigate to the following link: here.
6.2 SAP Active Global Support Follow-Up Opportunities
In general, SAP Active Global Support provides several self-assessments or guided services
to encourage customers to benefit from an SAP Business Process Stabilization and/or
Business Process Improvement project.
If you have an SAP Enterprise Support contract, SAP Active Global Support provides
you with the following offering for obtaining business process analytics and
implementing improvements:
- SAP Expert Guided Implementation Business Process Analytics and Improvement (SAP
EGI Portfolio Overview)
- CQC Business Process Analytics and Improvement (fact sheet).
If you have an SAP Max Attention Contract, contact your Technical Quality Manager
(TQM) for information about how SAP Active Global Support can help you obtain
business process analytics and implement improvements.
7 Workload of System PCD
This chart displays the main task types and indicates how their workload is distributed in
the system. The table below lists the detailed KPIs.
Response Time Components In Hours
Task Type Response Time Wait Time CPU Time DB Time GUI Time
DIALOG
38,8
0,1
10,9
10,3
12,8
RFC
18,1
0,0
1,8
1,5
0,0
BATCH
13,8
0,0
2,3
2,2
0,0
Others
1,6
0,1
0,1
0,9
0,0
7.1 Workload By Users
User activity is measured in the workload monitor. Only users of at least medium activity
are counted as 'active users'.
Users
dialog steps per
week
measured in
system
Low
Activity
Medium
Activity
1 to 399
400 to 4799
124
122
High
Activity
4800 or
more
Total
Users
14
260
7.2 Workload Distribution PCD
The performance of your system was analyzed with respect to the workload distribution.
We did not detect any major problems that could affect the performance of your SAP
system.
7.2.1 Workload by Application Module
The following diagrams show how each application module contributes to the total system
workload. Two workload aspects are shown:
- CPU time: total CPU load on all servers in the system landscape
- Database time: total database load generated by the application
All programs that are not classified in the SAP Application Hierarchy (transaction SE81)
are summarized in the "Un-Assigned" category. Customer programs, industry solutions,
and third-party add-on developments fall into this category.
7.2.2 DB Load Profile
The number of work processes creating database load in parallel is not
significantly high.
The following diagram shows the DB load caused by dialog, RFC, HTTP(S), and
background tasks, over different time frames.
The data provided in the diagram represents the average number of database processes
occupied by each task type in the database during the specified time frames.
These statistics are calculated as a weekly average, the average values over six working
days with a unit of one hour. Periods between 00:00-06:00 and 21:00-24:00 contain an
average value per hour, as these are not core business hours.
You can enable 24-hour monitoring by implementing SAP Note 910897. With 24-hour
monitoring, the time profile returns the workload of the system or application server on an
hourly basis rather than returning an average value per hour for the periods 00:00–06:00
and 21:00–24:00.
By comparing the load profiles for dialog and background activity, you can get an overview
of the volume of background activity during online working hours.
8 Performance Overview PCD
The performance of your system was analyzed with respect to the
average response times and total workload. We did not detect any major
problems that could affect the performance of your system.
Rating
Check
Performance Evaluation
The following table shows the average response times for various task types:
Averages of Response Time Components in ms
Dialog Response CPU Wait Load DB
GUI
Task type
Steps
Time
Time Time Time Time Time
DIALOG
265600
525,9 147,9
1,0
8,0 140,2 173,2
RFC
112422
579,5
57,2
0,8
1,8 48,9
0,0
UPDATE
13969
328,5
37,2 19,2
7,1 240,5
0,0
Averages of Response Time Components in ms
Dialog Response CPU Wait Load DB
GUI
Task type
Steps
Time
Time Time Time Time Time
UPDATE2
3611
62,1
9,8
1,1
3,8 35,5
0,0
BATCH
64323
773,2 127,3
0,5
8,1 124,5
0,0
SPOOL
11783
149,1
7,3
0,5
0,9
5,3
0,0
8.1 Performance Evaluation
The measured times are compared against reference times to provide a rating.
- If the number of dialog steps in an hour is less than 1000, this hour is not considered.
- If the total number of transaction steps is less than 20000, the rating for the task is not
performed (indicated by a gray icon in the table).
- RED if at least three time ranges are rated RED.
- YELLOW if two time ranges are rated RED or at least three time ranges are rated
YELLOW.
The table below shows that no problem is expected on the application or database servers.
Task
Steps
Application Server
Performance
Database Server
Performance
Dia
265554
Upd
13969
HTTP
0
HTTPS
0
The ratings in the table above are determined by comparisons against the reference table
below.
If the dialog response times are very poor, it will cause a RED rating for the entire check.
Reference for Reference for Reference for Reference for
Avg. Response Avg. Response Avg. DB time Avg. DB time
Task
Time (ms)
Time (ms) Red (ms) Yellow (ms) Red
Yellow Rating Rating
Rating
Rating
Dia
1200
3600
600
1800
Upd
2400
3600
1200
1800
HTTP
1200
3600
600
1800
HTTPS
1200
3600
600
1800
8.2 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the
transactions that cause the heaviest workload in your system.
8.2.1 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload.
Workload by Transaction (Dialog/HTTP(S)/WS-HTTP )
Total Avg. Avg. Avg. Avg.
Dialog Resp. Resp. CPU DB GUI
Transaction
Type
Steps Time Time Time Time Time
in % in ms in ms in ms in ms
SESSION_MANAGER DIA 15405 8,7 1.106,0 174,3 395,2 216,8
FAGLB03
DIA 7432 5,6 1.458,0 459,7 774,0
60,7
ME22N
DIA 8378 4,4 1.025,6 160,9 69,5 706,6
ME23N
DIA 21036 3,8 352,4
92,0 73,7 158,8
ME53N
DIA 13180 2,9 429,7 121,4 51,3 230,9
FBL1N
DIA 12077 2,3 379,1 214,5 109,4
30,5
Z_PDF
DIA
480 1,8 7.178,3
52,8 14,2 7.097,1
ME51N
DIA 4922 1,8 695,5 107,5 33,8 531,4
FBL3N
DIA 7750 1,7 422,0 141,3 158,4 116,8
ZMM_0041
DIA 1187 1,6 2.675,3 2.070,1 325,8 103,3
3.4% of the total response time in the above table is caused by customer transactions.
Workload by Transaction (Batch)
Total Total
Total Total
Dialog Resp. Resp.
CPU DB
Transaction
Steps Time Time in Time Time
in % s
in s
in s
SWNC_TCOLL_STARTER
2600 18,1 35.416,0 4.932,0 1.749,9
RSAL_BATCH_TOOL_DISPATCHING 168 1,0 2.026,0 818,0 557,8
(BATCH)
28205 0,9 1.708,0 478,0 814,8
RSWUWFML2
8064 0,6 1.230,0 409,0 499,4
ZCLMMINF002_ARCHIVO
7 0,6 1.093,0 250,0 947,3
RSBTCRTE
18070 0,5 1.043,0 298,0 279,6
RSPO1043
7 0,5 1.035,0
71,0 992,7
Workload by Transaction (Batch)
Transaction
RSCONN01
/BDL/TASK_SCHEDULER
ZMM_0021
Total Total
Total Total
Dialog Resp. Resp.
CPU DB
Steps Time Time in Time Time
in % s
in s
in s
2016 0,5 1.032,0 278,0 105,2
168 0,4
745,0
4,0
15,5
7 0,2
463,0
14,0
91,2
0.8% of the total response time in the above table is caused by customer transactions.
8.2.2 Transactions by DB Load
The following transaction profiles list the transactions that have the greatest share in the
database load, sorted by percentage of total database access times.
Database Load by Transactions (Dialog/HTTP(S) )
Dialog
Total DB
Avg. DB Time
Transaction
Type
Steps
Time in %
in ms
SESSION_MANAGER DIA
15405
12,6
395,2
FAGLB03
DIA
7432
11,9
774,0
ME23N
DIA
21036
3,2
73,7
ME2L
DIA
2258
2,7
587,9
FBL1N
DIA
12077
2,7
109,4
ZMM_PLANCPA
DIA
3464
2,6
358,3
FBL3N
DIA
7750
2,5
158,4
MB51
DIA
1831
2,1
555,1
ZFI_LIBRO_DIARIO DIA
31
1,7
27.247,5
ME2N
DIA
3131
1,7
267,1
4.3% of the total database time in the above table is caused by customer transactions.
If average database times are outside acceptable boundaries and you are unhappy with the
performance of a transaction, contact your in-house developers about possible optimization
potential and open a message under component SV-BO if required.
Database Load by Transactions (Batch)
Transaction
SWNC_TCOLL_STARTER
RSPO1043
Total DB
Dialog
Total DB
Time in
Steps
Time in s
%
2600
3,6
1.750,0
7
2,1
993,0
Database Load by Transactions (Batch)
Total DB
Dialog
Total DB
Transaction
Time in
Steps
Time in s
%
ZCLMMINF002_ARCHIVO
7
2,0
947,0
(BATCH)
28205
1,7
815,0
RSAL_BATCH_TOOL_DISPATCHING
168
1,2
558,0
RSWUWFML2
8064
1,0
499,0
RSBTCDEL
7
0,8
368,0
RSBTCRTE
18070
0,6
280,0
RSWWERRE
504
0,5
226,0
RHAUTUPD_NEW
7
0,3
163,0
2.0% of the total database time in the above table is caused by customer transactions.
8.3 RFC Load by Initiating Action
The load in task type RFC is shown. In the workload monitor, this information is shown as
'Load from External Systems'. The calling system can be an application server of the
system itself or any external system using the RFC interface. The 'Initial Action' is the
calling program initiating the RFC. The total response time for each initial action is shown
as an absolute value and as a percentage compared to the total RFC load considered in this
table. The average times (per dialog step) are shown in milliseconds [ms].
Calls from external systems are shown if they account for at least 8h or 5% of the total RFC
load. Local calls are shown if they account for at least 24h or 20% of the total RFC load.
Load Overview
Initial System
Local system PCD
Sum of external systems
RFC load (sum of above)
RFC load in Performance Overview
Load of all task types in Performance Overview
Load [s] Load %
13.815
58,45
9.821
41,55
23.636 100,00
65.149 275,63
295.036 1.248,24
Top 20 RFC Calls From External Systems - Average Times [ms]
Tota
Avg
l
.
Initial
Resp % of Avg.
Avg.
Avg.
Roll
Syste Initial Action
.
RFC Respons CPU
DB
Wait
m
Tim Load e Time Time Time
Tim
e in
e
s
3.70 15,6
ALM EFWK RESOURCE MANAGER
625,7 213,1 166,7 0,2
3
7
2.30
PCL EFWK RESOURCE MANAGER
9,76 1.113,0 105,6 116,3 5,0
7
GRAC_PFCG_AUTHORIZATION_SY
GRP
505 2,14 4.040,5 2.173,7 846,1 0,2
NC
ALM DIAGLS_COMPUTE_STATUS
300 1,27 4.546,9 1.327,4 1.850,0 0,1
GRP GRAC_ALERT_GENERATION
264 1,12
913,6
40,9
98,0 0,3
SSM EFWK Resource Manager (01 Minute
259 1,10 4.988,7 586,5 1.542,1 0,1
GRP GRAC_SOD 0400311511161#00001
239 1,01
796,5
39,7 164,2 0,2
GRP GRAC_SOD 0400311511211#00001
227 0,96
802,8
45,1 134,8 0,2
GRP GRAC_SOD 0400311511201#00001
224 0,95
725,8
40,5 108,2 0,2
GRP GRAC_SOD 0400311511181#00001
224 0,95
857,6
49,0 139,9 0,2
GRP GRAC_SOD 0400311511191#00001
224 0,95
793,4
46,4 125,2 0,4
GRP GRAC_SOD 0400311511171#00001
221 0,94
871,8
49,6 129,3 0,2
Top 20 RFC Calls From External Systems - Average Times [ms]
Tota
Avg
l
.
Initial
Resp % of Avg.
Avg.
Avg.
Roll
Syste Initial Action
.
RFC Respons CPU
DB
Wait
m
Tim Load e Time Time Time
Tim
e in
e
s
GRP GRAC_SOD 0400311511221#00001
220 0,93 1.219,5
73,4 208,2 0,3
GRAC_REPOSITORY_OBJECT_SYN
GRP
217 0,92 9.032,1 464,8 5.221,1 0,4
C
10.957,
GRP GRAC_ACTION_USAGE_SYNC
182 0,77 13.988,5
3.155,7 1,3
3
PCL DIAGLS_COMPUTE_STATUS
149 0,63 3.039,6 1.752,0 605,0 0,1
28.626,
TCD STMS
40 0,17 39.560,0 8.252,0
0,0
0
PCL SM:SELFDIAGNOSIS
32 0,14
766,6
12,3
32,9 0,2
SCL LANDSCAPE FETCH
29 0,12
713,0
24,2 109,2 0,7
SSM LANDSCAPE FETCH
28 0,12
672,0
24,1
65,3 0,4
Top 20 RFC Calls From Local System - Average Times [ms]
Tota
Avg
l
.
% of
Initial
Res
Avg.
Avg. Avg. Roll
RFC
Syste Initial Action
p.
Respons CPU DB
Wai
Loa
m
Tim
e Time Time Time t
d
e in
Tim
s
e
4.17 17,6
PCD ML81N
7.927,8 98,1
62,0 1,3
0
4
1.90
8.226, 17.053,
PCD SUIM
8,05 52.832,8
0,1
2
0
8
SAP_COLLECTOR_PERFMON_SWNC 1.25
1.113,
PCD
5,32 1.511,0
280,5 0,1
COLL
9
0
9.244, 18.385,
PCD PFCG
862 3,65 53.887,4
0,1
0
9
1.996,
PCD STMS
839 3,55 4.634,2
716,9 0,3
5
PCD SBWP
668 2,82
627,4 78,5 120,3 3,6
PCD LT12
521 2,20 1.029,2 223,9 219,8 0,7
PCD SU01
491 2,08 5.169,0 996,0 1.521,3 0,4
PCD ME53N
400 1,69
978,4 79,7 214,3 93,8
PCD Z_RSAUPURG_CLEAN_AUDIT
280 1,19 280.246, 281,0 303,0 0,0
Top 20 RFC Calls From Local System - Average Times [ms]
Tota
Avg
l
.
% of
Initial
Res
Avg.
Avg. Avg. Roll
RFC
Syste Initial Action
p.
Respons CPU DB
Wai
Loa
m
Tim
e Time Time Time t
d
e in
Tim
s
e
0
PCD ME23N
280 1,18
655,1 79,0
76,4 4,2
PCD ME51N
229 0,97
901,5 103,2 258,5 16,3
PCD MIGO
215 0,91
534,9 64,5 138,4 0,2
PCD ME33K
211 0,89 1.053,3 80,7
55,7 1,9
PCD ME32K
204 0,86 3.137,1 89,5
91,2 2,1
PCD ME5A
149 0,63 1.734,6 98,7 262,6 40,5
PCD ME3N
120 0,51
662,8 95,5
63,3 4,7
PCD ME21N
106 0,45
581,1 100,6 148,3 0,2
PCD FRFT_B
94 0,40
391,4 49,7
3,3 0,3
SAP_COLLECTOR_PERFMON_RSAM
PCD
88 0,37
523,9
4,5
0,6 0,2
ON40
9 SAP System Operating PCD
The daily operation of your system was analyzed. We detected some
problems that may impair system operation and stability.
9.1 Availability based on Collector Protocols
A value of 100% means that the collector was available all day. "Available" in the context
of this report means that at least one SAP instance was running. If the SAP collector was
not running correctly, the values in the table and graphics may be incorrect.
To check these logs, call transaction ST03N (expert mode) and choose "Collector and
Performance DB -> Performance Monitor Collector -> Log".
This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR
that runs every hour.
The job does NOT check availability; it carries out only general system tasks such as
collecting and aggregating SAP performance data for all servers/instances. The log does not
contain any direct information about availability; it contains only information about the
status of the hourly statistical data collection.
As of SAP Basis 6.40, system availability information is available in the CCMS
(Computing Center Management System) of an SAP System, in Service Level Reporting of
SAP Solution Manager.
This function is provided by the relevant Solution Manager Support Packages as an
advanced development. For more information, refer to SAP Note 944496, which also lists
the prerequisites that must be fulfilled before implementation can take place."
9.2 Update Errors
In a system running under normal conditions, only a small number of update errors should
occur. To set the rating for this check, the number of active users is also taken into
consideration.
We did not detect any problems.
9.3 Table Reorganization
The largest tables and/or rapidly growing tables of system PCD were checked. No standard
SAP recommendations for the applicable data volume management were found.
9.4 Program Errors (ABAP Dumps)
30 ABAP dumps have been recorded in your system in the period 16.11.2015 to
22.11.2015. ABAP dumps are generally deleted after 7 days by default. To view the ABAP
dumps in your system, call transaction ST22 and choose Selection. Then select a
timeframe.
Date
Number of Dumps
16.11.2015
17.11.2015
18.11.2015
19.11.2015
20.11.2015
21.11.2015
22.11.2015
Dum
Server (e.g.)
ps
mtrprsaperp_PCD
SYNTAX_ERROR
1
_00
mtrprsaperp_PCD
TIME_OUT
9
_00
mtrprsaperp_PCD
RFC_NO_AUTHORITY
4
_00
mtrprsaperp_PCD
MESSAGE_TYPE_X
4
_00
MEMORY_NO_MORE_PAGIN
mtrprsaperp_PCD
1
G
_00
TSV_TNEW_PAGE_ALLOC_FA
mtrprsaperp_PCD
2
ILED
_00
mtrprsaperp_PCD
SYSTEM_NO_ROLL
2
_00
Name of Runtime Error
5
4
8
3
8
1
1
Date
Time
(e.g.)
(e.g.)
17.11.20 17:53:0
DLAVID
15
3
19.11.20 09:51:0
ASADY
15
5
WF20.11.20 09:13:5
BATCH
15
5
20.11.20 10:03:0
SMORA
15
0
20.11.20 10:39:0
ANUÑEZ
15
4
CALVAR 20.11.20 16:23:3
EZ
15
7
CALVAR 20.11.20 16:23:3
EZ
15
8
User (e.g.)
Name of Runtime Error
RAISE_EXCEPTION
Dum
Date
Time
Server (e.g.)
User (e.g.)
ps
(e.g.)
(e.g.)
mtrprsaperp_PCD
22.11.20 06:01:4
7
PACUÑA
_00
15
2
It is important that you monitor ABAP dumps using transaction ST22 on a regular basis. If
ABAP dumps occur, you should determine the cause as soon as possible.
Based on our analysis, we found several ABAP dumps that need your attention.
Evaluate and resolve the above dumps. If you cannot find a solution, send a customer
message to SAP to request support.
10 Security
Critical security issues were found in your system.
See the information in the following sections.
Rating
Check
System Recommendations (ABAP)
Default Passwords of Standard Users
Control of the Automatic Login User SAP*
Protection of Passwords in Database Connections
ABAP Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
10.1 ABAP Stack of PCD
10.1.1 System Recommendations (ABAP)
System Recommendations is not used for this system.
Recommendation: SAP strongly recommends applying important security fixes as soon as
possible.
The 'System Recommendations' application provides a detailed recommendation regarding
which SAP security notes (ABAP and non-ABAP) should be implemented based on the
actual status of the system and the notes already implemented. This is a mandatory
prerequisite for setting up a strong security patch process. For more information, go to
http://service.sap.com/sysrec .
10.1.2 ABAP Password Policy
If password login is allowed for specific instances only, the password policy is checked
only for these instances.
10.1.3 Users with Critical Authorizations
For more information about the following check results, see SAP Note 863362.
Recommendation:
Depending on your environment, review your authorization concept and use the Profile
Generator (transaction PFCG) to correct roles and authorizations. You can use the User
Information System (transaction SUIM) to check the results. For each check, you can
review the roles or profiles that include the authorization objects listed in the corresponding
section.
10.1.3.1 Super User Accounts
Users with authorization profile SAP_ALL have full access to the system. There should be
a minimum of such users. The number of users with this authorization profile is stated for
each client.
Client
No. of Users Having This
Authorization
000
001
No. of Valid
Users
3
2
Rating
45
5
Authorization profile:
SAP_ALL
11 Software Change and Transport
Management of PCD
Software change management issues were found in your system.
See the information in the following sections.
11.1 SAP Netweaver Application Server ABAP of PCD
Rating
Check Performed
Number of Changes
Emergency Changes
Failed Changes
11.1.1 Number of Changes
Performing changes is an important cost driver for the IT department. It is only acceptable
to make a large number of software and configuration changes in exceptional situations,
such as during go-live for an implementation project.
No data from the managed system could be found in the configuration and change database
(CCDB). Check whether the diagnostics setup for the managed system has been performed
as described in SAP Note 1472465.
Solution Manager Diagnostics provides valuable features for root cause analysis and is an
important data source for various support services.
The CCDB data is required here to check the configuration of the managed system.
11.1.2 Number of Transport Requests
The following diagram contains information about the number of transport requests per day
that were imported into the SAP system in the last week.
Date
17.11.2015
18.11.2015
19.11.2015
20.11.2015
Workbench and
Relocation Requests
Customizing
Requests
0
0
0
0
Transport of
Copies
6
4
2
2
0
0
0
0
11.1.3 Number of Transported Objects
The following diagram contains information about the number of objects per day that was
imported into the SAP system in the last week.
Objects in Workbench Objects in
Date
and Relocation
Customizing
Requests
Requests
17.11.2015
0
18.11.2015
0
19.11.2015
0
20.11.2015
0
Objects in
Transport of
Copies
46
42
18
18
0
0
0
0
11.1.4 Emergency Changes
We analyzed the number of emergency changes in system PCD in the last week.
Rating Item
Value Explanation
Transport requests
Number of transport requests; created
created in
0
or released in production.
production
The duration between the export from
Transport requests
the development system and the import
with short
14
into the production system was shorter
transition time
than one day.
Total number of
Total number of transport requests in
14
transport requests
production.
Transport Requests with a short Transition Time
Request
DCDK915202
DCDK915204
DCDK915215
DCDK915217
DCDK915219
...
User
NOVIS
DLAVID
NOVIS
NOVIS
NOVIS
Export from DEV
17.11.2015 11:25:09
17.11.2015 12:01:07
17.11.2015 18:04:45
17.11.2015 18:13:42
17.11.2015 18:19:19
Import in PRD
18.11.2015 10:40:18
17.11.2015 12:38:49
17.11.2015 18:08:27
17.11.2015 18:17:08
17.11.2015 18:20:52
Recommendation: Transport requests with a short transition time of less than one day
have occurred in the last week. These transports may not have been tested sufficiently.
Make sure that they did not cause problems in production.
11.1.5 Failed Changes
In this check, we analyzed the number of failed changes in system PCD during the last
week.
Rating Item
Transport
requests with
import errors
Value Explanation
Number of transport requests with import
0 errors that were not resolved within one
hour.
If an old object version overwrites a
Overtakers and
newer one we count this as a transport
bypassed
sequence error. We count both the
0
transport
overtaker transport and the bypassed
requests
transport. Each transport is only counted
once.
Total number of
Total number of transport requests that
transport
14 were imported or released in production
requests
within the last week.
12 Data Volume Management (DVM)
The database size and database growth of your system PCD indicate that
no immediate action is required in the area of data volume management.
This report does not have a Data Volume Management (DVM) section because your SAP
Solution Manager system does not fulfill the technical requirements, or the ST-A/PI release
on your system PCD is too low (or could not be identified). For more information, see SAP
Note 2036442.
As a workaround, the database size and growth per year for your system PCD were
checked. Here, we found a database size of 307.06 GB and a database growth of 19.92%
per year. These figures indicate that, from a Data Volume Management perspective, no
immediate activities are required for your system PCD.
13 Database Performance for PCD
Some performance problems have been detected in your database
system. Please implement the recommendations provided in the following
sections.
13.1 I/O Performance
The following tables show how I/O operations are distributed across the data files and log
files respectively.
The average wait time per I/O operation is also shown below for each file (IOStallRead and
IOStallWrite).
Generally, high I/O read times cannot be used as a direct indication of DB performance
issues. We recommend, therefore, that you refer to SAP Note 987961 for information about
interpreting the various I/O statistics available with SQL Server 2005 and 2008.
With respect to the data files, the I/O activity must be evenly distributed among the files.
This can be achieved by manually maintaining an even amount of free space in data files.
Transaction log files are used sequentially, which is why having more than one file does not
improve performance. If you have multiple log files for other reasons, uneven distribution
can be ignored.
Additionally, the "IO related wait events" table summarizes and assesses all wait events
relevant to disk I/O performance.
Note: The average wait time for each I/O operation (IOStallRead) of the files with
YELLOW rating deviates by more than 50% from the best one. If this is not expected
behavior of your storage subsystem, contact the storage administrator or vendor. There may
be potential to improve performance for the corresponding logical volumes.
Data Files
File
Reads
% of
Writes
Reads
IOStallWrite
% of
[ms] / write
Writes
request
File
7553587 14.40 354630 7.71
ID 1
File
11434 0.02 1885229 41.01
ID 2
File
6012944 11.46 324908 7.07
ID 3
File
5923142 11.29 310933 6.76
ID 4
File
3151873 6.01
239949 5.22
ID 5
File
7510447 14.31 330726 7.19
ID 6
File
7506396 14.31 386495 8.41
ID 7
File
7431456 14.16 350238 7.62
ID 8
File
7366502 14.04 414447 9.01
ID 9
Total 52467781 100
4597555 100
IO related wait events
IOStallRead
[ms] / read
request
11.71
12.31
7.06
87.34
11.82
12.71
12.44
12.79
11.55
12.71
12.07
13.23
12.70
12.98
12.18
12.99
12.34
12.89
10.05
12.86
Wait time
Wait time / Reference
Requests
Rating
(ms)
Requests Value
Analysis timeframe (ms):
1.488.480.600
PAGEIOLATCH_SH
188.792.030 34.467.580
5,48
15,00
ASYNC_IO_COMPLETION
73.438.448
174 422.060,05
IO_COMPLETION
25.362.246 7.864.369
3,22
PAGEIOLATCH_EX
12.698.721
855.082
14,85
WRITELOG
8.834.255 2.337.254
3,78
6,00
PAGEIOLATCH_UP
79.428
7.137
11,13
Wait type
13.2 Database Buffers and Performance
The following information is based on historical data extracted from the database collector
for the week prior to this service session.
Performance
Indicator
Description
Observed Reference
value
value
Indicates how often the
DATA CACHE HIT
database accesses data in 93 %
RATIO
memory
Indicates how often stored
PROCEDURE
procedures were found in 97 %
CACHE HIT RATIO
memory
>= 97 %
> 80 %
13.3 Wait Statistics
The wait statistics of the SQL Server show long wait times for the event(s) highlighted
below. This can indicate slow performance of the I/O system or other unusual conditions.
Note that wait events that are known to have no relevance to user queries ("idle events") are
not shown in the table.
High wait time for some events may indicate a performance bottleneck. In the "Rating"
column, you may find the following symbols:
"Red flash" - in a well-tuned database, the event should not appear among the top events.
Its appearance indicates a bottleneck and thus potential for improvement. See explanations
below.
"Yellow exclamation mark" - it is normal that the wait event is among the top events, but its
average value exceeds a threshold. An improvement may be possible.
"Blue information sign" - this wait event is important for performance but does not have a
critical value.
No symbol - we do not have experience with a wait event of that type. If the overall
database performance is not affected; it can be ignored.
One of the events LCK_M_X, LCK_M_S, or LCK_M_U appears in the "Top Wait
Events Statistics" table. This indicates that some processes must wait for exclusive database
locks. Exclusive DB locks are caused either by application logic holding exclusive locks for
longer than needed, by expensive statements executed within a database transaction, or by
too high parallelization grade during background processing.
Analyze the lock history as explained in SAP Note 806342 to find the root cause.
A DB task goes to wait state SOS_SCHEDULER_YIELD if it has been running too long
on a CPU. This indicates that there are a lot of expensive, long-running statements.
Analyze the SQL statement cache by looking for statements with high total and average
CPU time, and then tune them.
If SQL statements have been optimized, but there are still high total figures for this wait
event, the database engine is suffering from an overall CPU bottleneck because of too slow
CPUs or too few CPUs for the current load. Also check whether the CPU bottleneck itself
is caused by excessive paging. If the paging rate is high, make sure you allow the SQL
Server to lock pages in the memory, as described in SAP Note 1134345, irrespective of
whether you are experiencing the symptoms described in this SAP Note.
Wait time
Wait time /
Requests
Rating
(ms)
Requests
Analysis timeframe (ms):
1.488.480.600
PAGEIOLATCH_SH
188.792.030 34.467.580
5,48
BACKUPIO
168.208.800 1.006.751
167,08
BACKUPTHREAD
86.638.184
6.920 12.519,97
BACKUPBUFFER
74.398.360 1.896.884
39,22
ASYNC_IO_COMPLETION
73.438.448
174 422.060,05
ASYNC_NETWORK_IO
59.792.216 145.720.020
0,41
IO_COMPLETION
25.362.246 7.864.369
3,22
LCK_M_U
21.365.032
16.111 1.326,11
PAGEIOLATCH_EX
12.698.721
855.082
14,85
PREEMPTIVE_OS_WRITEFILE
9.244.876
133.267
69,37
WRITE_COMPLETION
9.220.335
133.407
69,11
WRITELOG
8.834.255 2.337.254
3,78
SOS_SCHEDULER_YIELD
5.589.812 33.121.744
0,17
PREEMPTIVE_OS_PIPEOPS
3.404.254
64.054
53,15
Wait type
13.4 Missing Indexes
This check verifies that the indexes defined by SAP application developers in the SAP data
dictionary also exist in the database. Missing primary indexes can lead to inconsistent data
in the SAP system. A missing index of any kind can lead to severe performance problems.
No missing indexes were found in system PCD.
14 Database Administration for PCD
No major problems regarding the administration of your database were
found.
Note: A remote service cannot verify certain important aspects of your
administration strategy, such as your offsite storage of database backups
and whether the backup tapes can be read correctly.
14.1 Database Files
The following checks analyze the settings for database and transaction log files.
14.1.1 Data Separation
To distribute I/O load, place heavily used files such as database files, transaction log files,
files of database tempdb, and the Windows paging files on separate disks.
Note: From the SAP side, we are not in a position to check whether your partitions are
distributed across multiple physical devices.
Make sure the following brief guidelines for security, maximum performance, and
scalability are taken into account.
1. The temporary database for SQL Server (tempdb) is used by queries to execute large
join, sort, and group operations when the SQL Server buffer pool cannot provide enough
memory.
For SAP BW, SAP SEM, and SAP SCM, tempdb I/O performance can become a major
bottleneck when reporting queries are executed that use the fact table or perform
aggregation. To prevent bottlenecks, we recommend that you manage tempdb as a normal
SAP database. Use a data tempdb file on the same partition with each data SAP database
file. Furthermore, do not place tempdb on the partition and disks that contain the
transaction log. For Storage Area Network (SAN) storage, tempdb can share space with the
tempdb log files.
2. For security and performance reasons, store the SAP data files and the SAP transaction
log file(s) on separate disk systems. They should not share disks with other SQL Server
programs and database files.
3. Store the Windows paging file(s) on dedicated disks.
14.1.2 Database File Settings
When distributing database files, adhere to the following general rules:
1. If you use directly attached disks, distribute the I/O load to multiple physical disks. This
can be achieved by assigning each data file to an individual disk spindle.
2. For all data files in the R/3 system, enable the "Autogrowth" option using SQL Server
tools. Set the file growth to at least 100 MB.
3. As of SQL Server 2008 on Windows 2008R2, you can rely on the automatic growth
feature if a number of prerequisites are met. Please check SAP Note 1238993 for details.
4. After a manual or an automatic file expansion, ensure that all data files have
approximately the same amount of free space.
Note: Your current database file settings are:
Database File Name
E:\PCDDATA1\PCDDATA1.md
f
E:\PCDDATA2\PCDDATA2.ndf
E:\PCDDATA3\PCDDATA3.ndf
E:\PCDDATA4\PCDDATA4.ndf
E:\PCDDATA5\PCDDATA5.ndf
E:\PCDDATA6\PCDDATA6.ndf
E:\PCDDATA7\PCDDATA7.ndf
E:\PCDDATA8\DC4DATA8.ndf
Growth
Growth
not
activated
restricted
?
?
Next 2
Next
steps
step
possible
size
?
300.0
0 MB
300.0
0 MB
300.0
0 MB
300.0
0 MB
300.0
0 MB
300.0
0 MB
300.0
0 MB
300.0
0 MB
Free
Space
on
File
1263
5 MB
1248
0 MB
1173
0 MB
1089
8 MB
1379
3 MB
1677
0 MB
1335
4 MB
1580
5 MB
Dat
a
Ratin
file g
full?
The data file settings in system PCD are correct.
14.1.3 Transaction Log File Settings
When transaction log files of an SQL Server database are full, log files can grow
automatically, limited only by the space available on the Windows partition.
This is only true if the files are allowed to grow and sufficient space is available.
The current settings of your transaction log files are as follows:
Next
Growth
Growth not Next step
Transaction Log File Name
step
activated? restricted? possible?
size
15.00
L:\PCDLOG1\PCDLOG1.ldf
%
The log file settings in system PCD are correct.
14.2 Environment and Operating
In this section, basic information on the database and its software environment are shown.
14.2.1 Database Growth
The figures show a history of the total size and usage of the database files.
14.2.2 Largest Tables
The following table shows the largest tables currently in the database.
Reserved Used
(data + (data +
Modified
Table Name
Data (kB)
Rows
indexes) indexes)
Rows
kB
kB
SOFFCONT1
62625872 62656704 62646936 2405589 90545
REPOLOAD
19741616 19824000 19774272 362883 27836
DD03L
3853312 12969680 12851248 8767304 1126023
FAGLFLEXA
5816320 11453776 11446640 11221748 210095
REPOSRC
9817152 10357440 10341664 4502765 304441
D010TAB
4172448 10266424 10263792 43859902 98430
FAGL_SPLINFO
4800568 6896488 6892096 5795552 840098
ANLP
5296944 6348032 6345456 6578669 757569
ENHOBJCONTRACT 5342448 5361480 5342816
1403
423
D010INC
2167192 5325536 5323112 16394929 51113
14.2.3 Service Pack
SAP always recommends the latest SQL Server Service Pack. For details on the SAP
support strategy for SQL Server, see SAP Note 62988.
The recommendations for this check are as up to date as the SAP Service Tool.
Build
Builds
In Use
Comment
2938478 Cumulative update package 12
4305 10.50.4305 (CU12) for SQL Server 2008 R2 Service
Pack 2
2967540 Cumulative update package 13
10.50.4319 (CU13) for SQL Server 2008 R2 Service
Pack 2
2977319 MS14-044: Description of the
10.50.4321 security update for SQL Server 2008 R2
Service Pack 2 (QFE)
2987585 Restore Log with Standby
Mode on an Advanced Format disk may
10.50.4331
cause a 9004 error in SQL Server 2008
R2
SQL Server 2008 R2 Service Pack 3
10.50.6000
(SP3)
Release
Date
21.04.2014
30.06.2014
12.08.2014
27.08.2014
26.09.2014
Build
Builds
In Use
Release
Date
Comment
3033860 An on-demand hotfix update
10.50.6525 package is available for SQL Server
2008 R2 Service Pack 3 (SP3)
09.02.2015
Ensure that you are always using the latest SQL Server builds. Detailed information about
all SQL server builds is provided at Microsoft Knowledge Base Article 321185.
14.2.4 Database Maintenance Jobs
All database maintenance jobs are scheduled as recommended.
Job
Blocking Lockstats Job not Scheduled! (CCMS
Blocking Locks statistics)
SAP
Note
Rating
547911
14.2.5 SAP Notes for SQL Server
The following SAP Notes contain useful information to operate the ERP ENHANCE
PACKAGE R/3 ERP system on SQL Server.
SAP Note Title
1085937 Wait Event Analysis For SQL Server
111291 FAQ: SQL server analysis and avoiding deadlocks
1152848 FAQ: SQL Server Wait Events
1237682 Configuration Parameters for SQL Server 2008
555223 FAQ: Microsoft SQL Server
62988 Service packs for Microsoft SQL Server
806342 FAQ: Analyzing exclusive database locks on SQL Server
15 Database server load from expensive
SQL statements - PCD
The SQL statements identified did not lead to performance problems.
The load overview is listed in the table below for reference, and further
details of the most expensive statements are included at the end of the
section.
Database Load From Expensive Statements
Rating Logical reads [%]
Physical reads [%]
2
12
Elapsed time [%]
2
The table above shows the cumulative amount of problematic statements identified. If the
database was inactive for more than one day before the analysis was performed, the
information provided may not be entirely accurate.
Note: The overall section rating is linked to the above table rating; the ratings are described
in SAP Note 2021756.
If the table rating is RED, there are SQL statements that cause a high percentage of the
overall load on your SAP system.
If the table rating is YELLOW, there are SQL statements that cause a considerable
percentage of the overall load on your SAP system.
If the table rating is GREEN, your system SQL statement cache contains no significant
problems.
If the table rating is UNRATED, the total reads of your system's SQL statement cache were
<= 100,000,000, or some analysis data was unavailable.
The following table lists the load of each SQL statement individually. The load of the
statement is evaluated against the total load since database startup.
Note: If an object name in this table contains the character "/", it may indicate a join. If an
object is not in the ABAP Dictionary (transaction SE12) with the object name listed, check
for each part of the join (items separated by "/").
16 Database and ABAP Load Optimization
of PCD
We did not find expensive SQL statements that cause a very high load on
your system in general.
However, we collected the SQL statements that generate the most load
based on the number of buffer logical reads. Implement the
recommendations provided below in this section at your convenience.
16.1 Analysis of DB SQL CACHE on 23.11.2015 04:54:28
Expensive SQL Statements Overview
Elapsed
Logical Physical CPU
Calls
Total
Object Name
time
Calls
reads reads
time
[%]
rows
[%]
[%]
[%]
[%]
TTREE_SFW_NODES
0
0 94492
42767
1
0
0
UST12
1
0 56142 18290051
1
1
0
SWWWIHEAD
0
0 2484
0
0
6
0
SRT_RTC_DATA
0
0
414 542754
0
0
0
SRT_RTC_DATA
0
0 542754 542754
0
0
0
UST10S
1
0 49437 33484003
0
1
0
SWWWIHEAD
0
0 4963
302
0
4
0
UST10C
0
0 56429 759782
0
0
0
TTREE_SFW_NODES
0
0 32370
2490
0
0
0
UST12
0
0
729
58065
0
0
0
The statements were selected for analysis and optimization based on the "Logical reads
[%]" column. Logical reads are a measure of the workload on a database server because
they cause CPU and memory utilization.
The "Total Rows expected" column indicates the expected number of rows returned by the
statement.
16.1.1 Access on TTREE_SFW_NODES in SAPLSHI25
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 94492
117180
1,24
1
1
SELECT "SFW_ASS_ID" ,"SWITCH_ID" ,"TREE_ID" ,"NODE_ID" ,"REACTION"
FROM
"TTREE_SFW_NODES" ,(SELECT "C_0" = @P1 , "C_1" = @P2 UNION SELECT @P3
, @P4 UNION SELECT @P5 , @P6 UNION SELECT @P7 , @P8
UNION SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 ,
@P14 UNION SELECT @P15 , @P16 UNION SELECT @P17 , @P18
UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23
, @P24 UNION SELECT @P25 , @P26 UNION SELECT @P27 ,
@P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT
@P33 , @P34 UNION SELECT @P35 , @P36 UNION SELECT @P37
, @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION
SELECT @P43 , @P44 UNION SELECT @P45 , @P46 UNION SELECT
@P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION
SELECT @P53 , @P54 UNION SELECT @P55 , @P56 UNION
SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62
UNION SELECT @P63 , @P64 UNION SELECT @P65 , @P66
UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71
, @P72 UNION SELECT @P73 , @P74 UNION SELECT @P75 ,
@P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT
@P81 , @P82 UNION SELECT @P83 , @P84 UNION SELECT @P85
, @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION
SELECT @P91 , @P92 UNION SELECT @P93 , @P94 UNION SELECT
@P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) "t_00"
WHERE
"TTREE_SFW_NODES" ."TREE_ID" = "t_00" ."C_0" AND "TTREE_SFW_NODES"
."NODE_ID" = "t_00" ."C_1" /* R3:SAPLSHI25:114 T:
TTREE_SFW_NODES M:400 */
Execution Plan
|-- Nested Loops
|-- Nested Loops
|-- Merge Join
|-- Index Seek SEEK: [TTREE_SFW_NODES].TREE_ID EQ [Union1003] AND
[TTREE_SFW_NODES].
NODE_ID EQ [Union1004] ORDERED 1
|-- Clustered Index Seek SEEK: [TTREE_SFW_NODES].SFW_ASS_ID EQ [PCD].[pcd].
[TTREE_SFW_NODES].[SFW_ASS_ID] ORDERED 1
Program Data:
Origin of ABAP coding
Program Name Line
Created By Last Changed By Last Changed On
LSHI25U02 0000033 SAP
SAP
23.10.2015
0000024 DATA: del_start_index LIKE sy-tabix,
0000025 del_stop_index LIKE sy-tabix,
0000026 tmp_start LIKE sy-tabix,
0000027 del_node_level TYPE hier_iface-node_level.
0000028
0000029 *End Of Insertion MPRE 08.09.2006
0000030
0000031 *
0000032 if it_nodes[] is not initial. "do not execute select with empty for-all-entries-table
*>>>>>>>>>>>>>>>>>
0000033 SELECT * FROM ttree_sfw_nodes INTO TABLE switches
0000034 FOR ALL ENTRIES IN it_nodes
0000035 WHERE tree_id = it_nodes-tree_id
0000036 AND node_id = it_nodes-node_id.
0000037 endif.
0000038 ref_nodes[] = it_nodes[].
*<<<<<<<<<<<<<<<<<<
0000039 DELETE ref_nodes WHERE reftree_id EQ space AND refnode_id EQ space.
0000040 IF ref_nodes[] IS NOT INITIAL.
0000041 SELECT * FROM ttree_sfw_nodes INTO TABLE ref_switches
16.1.2 Access on UST12 in /GRCPI/CL_GRIA_AUTH===========
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 56142
486610
0,03
326
1
SELECT "OBJCT" ,"AUTH" ,"FIELD" ,"VON" ,"BIS"
FROM
"UST12" ,(SELECT "C_0" = @P1 , "C_1" = @P2 UNION SELECT @P3 , @P4 UNION
SELECT @P5 , @P6 UNION SELECT @P7 , @P8 UNION
SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 , @P14
UNION SELECT @P15 , @P16 UNION SELECT @P17 , @P18
UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23
, @P24 UNION SELECT @P25 , @P26 UNION SELECT @P27 ,
@P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT
@P33 , @P34 UNION SELECT @P35 , @P36 UNION SELECT @P37
, @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION
SELECT @P43 , @P44 UNION SELECT @P45 , @P46 UNION SELECT
@P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION
SELECT @P53 , @P54 UNION SELECT @P55 , @P56 UNION
SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62
UNION SELECT @P63 , @P64 UNION SELECT @P65 , @P66
UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71
, @P72 UNION SELECT @P73 , @P74 UNION SELECT @P75 ,
@P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT
@P81 , @P82 UNION SELECT @P83 , @P84 UNION SELECT @P85
, @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION
SELECT @P91 , @P92 UNION SELECT @P93 , @P94 UNION SELECT
@P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) "t_00"
WHERE
"UST12" ."MANDT" = @P101 AND "UST12" ."OBJCT" = "t_00" ."C_0" AND "UST12"
."AUTH" = "t_00" ."C_1" AND "UST12" ."AKTPS" = @P102
AND ( "UST12" ."VON" IS NOT NULL OR "UST12" ."VON" IS NULL ) AND (
"UST12" ."BIS" IS NOT NULL OR "UST12" ."BIS" IS NULL ) /*
R3:/GRCPI/CL_GRIA_AUTH===========CP:1348 T:UST12 M:400 */
Execution Plan
|-- Stream Aggregate GROUP BY: [UST12].OBJCT, [UST12].AUTH, [UST12].FIELD,
[UST12].VON,
[UST12].BIS
|-- Merge Join
|-- Clustered
[@P1] AND [UST12].AUTH EQ
|-- Clustered
[@P3] AND [UST12].AUTH EQ
|-- Clustered Inde
[@P5] AND [UST12].AUTH EQ [@
|-- Clustered Index Se
AND [UST12].AUTH EQ [@P8] AND
|-- Clustered Index Seek S
AND [UST12].AUTH EQ [@P10] AND [
|-- Clustered Index Seek SEEK:
AND [UST12].AUTH EQ [@P12] AND [US
|-- Clustered Index Seek SEEK: [US
[UST12].AUTH EQ [@P14] AND [UST12].A
|-- Clustered Index Seek SEEK: [UST12]
[UST12].AUTH EQ [@P16] AND [UST12].AKT
|-- Clustered Index Seek SEEK: [UST12].M
[UST12].AUTH EQ [@P18] AND [UST12].AKTPS
|-Clustered Index Seek SEEK: [UST12].MANDT E
[UST12].AUTH EQ [@P20] AND [UST12].AKTPS E
|-Clustered Index Seek SEEK: [UST12].MANDT EQ
[UST12].AUTH EQ [@P22] AND [UST12].AKTPS EQ
|-Clustered Index Seek SEEK: [UST12].MANDT EQ [@
[UST12].AUTH EQ [@P24] AND [UST12].AKTPS EQ [@
|-Clustered Index Seek SEEK: [UST12].MANDT EQ [@P1
[UST12].AUTH EQ [@P26] AND [UST12].AKTPS EQ [@P1
|-Clustered Index Seek SEEK: [UST12].MANDT EQ [@P101
[UST12].AUTH EQ [@P28] AND [UST12].AKTPS EQ [@P102
|-- Clustered
Index Seek SEEK: [UST12].MANDT EQ [@P101] AND [UST12
[@P30] AND [UST12].AKTPS EQ [@P102] ORDERED 1
|-- Clustered
Index Seek
SEEK:
[UST12].
MANDT EQ
[@P101] AND
[UST12].
OBJCT EQ
[@P31] AND
[UST12].
AUTH EQ
[@P32] AND
[UST12].
The execution plan has been cut because it was too long
Program Data:
Origin of ABAP coding
Last
Last
Created
Program Name
Line
Changed Changed
By
By
On
/GRCPI/CL_GRIA_AUTH===========CM004 0000110 SAP
SAP
23.10.2015
0000101 FOR ALL ENTRIES IN lt_prof
0000102 WHERE profn = lt_prof-profile
0000103 AND aktps = 'A'
0000104 AND ( objct IS NULL OR objct IS NOT NULL )
0000105 AND ( auth IS NULL OR auth IS NOT NULL ).
0000106 ENDIF.
0000107 ENDIF.
0000108
0000109 IF lt_ust10s IS NOT INITIAL.
*>>>>>>>>>>>>>>>>>
0000110 SELECT objct auth field von bis
0000111 FROM ust12 "#EC CI_BYPASS "#EC CI_GENBUFF
0000112 INTO CORRESPONDING FIELDS OF TABLE lt_object_values
0000113 FOR ALL ENTRIES IN lt_ust10s
0000114 WHERE objct = lt_ust10s-objct
0000115 AND auth = lt_ust10s-auth
0000116 AND aktps = 'A'
0000117 AND field IN it_field_range
0000118 AND ( von IS NOT NULL OR von IS NULL )
0000119 AND ( bis IS NOT NULL OR bis IS NULL ).
0000120
0000121 ENDIF.
*<<<<<<<<<<<<<<<<<<
0000122
0000123 IF iv_count IS NOT INITIAL.
0000124 /grcpi/cl_gria_auth=>gv_auth = iv_count.
16.1.3 Access on SWWWIHEAD in
CL_SWF_RUN_RESTART_HANGUP_ITMS
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 2484
315737
127,11
1
1
SELECT "WI_ID"
FROM
"SWWWIHEAD"
WHERE
"CLIENT" = @P1 AND "WI_TYPE" IN ( @P2 , @P3 , @P4 , @P5 ) AND "WI_STAT"
IN ( @P6 , @P7 ) AND "CREA_TMP" <= @P8 /* R3:
CL_SWF_RUN_RESTART_HANGUP_ITMSCP:116 T:SWWWIHEAD M:400 */
Execution Plan
|-- Nested Loops
|-- Merge Interval
|-- Sort
|-- Index Seek SEEK: [SWWWIHEAD].CLIENT EQ [@P1] ORDERED 1 WHERE:
[PCD].[pcd].
[SWWWIHEAD].[CREA_TMP]<=[@P8] AND
([PCD].[pcd].[SWWWIHEAD].[WI_STAT]=[@P7] OR
[PCD].[pcd].[SWWWIHEAD].[WI_STAT]=[@P6])
Program Data:
Origin of ABAP coding
Last
Last
Create
Program Name
Line
Change Changed
d By
d By
On
CL_SWF_RUN_RESTART_HANGUP_ITMSCM0 000003
23.10.201
SAP SAP
02
6
5
0000027 ls_wicrtts-option = 'LE'.
0000028 ls_wicrtts-low = me->get_hangup_timestamp( ).
0000029 APPEND ls_wicrtts TO lr_wicrtts.
0000030
0000031 * --- note 1961266: C seems to be the wrong index, E fits better, deactivate hints -0000032 * CONCATENATE 'INDEX("&TABLE&" "SWWWIHEAD~C"
"SWWWIHEAD^C" "SWWWIHEAD_C"'
0000033 * '"SWWWIHEAD_C__X")'
0000034 * INTO l_hint SEPARATED BY space.
0000035
*>>>>>>>>>>>>>>>>>
0000036 SELECT wi_id FROM swwwihead INTO TABLE re_wiids
0000037 WHERE wi_type IN lr_witype
0000038 AND wi_stat IN lr_wistat
0000039 * AND retry_cnt = 0
0000040 AND crea_tmp IN lr_wicrtts.
0000041 * %_HINTS ORACLE l_hint
0000042 * DB2 'USE VALUES FOR OPTIMIZATION'
*<<<<<<<<<<<<<<<<<<
0000043 * DB2 '&SUBSTITUTE VALUES&'
0000044 * INFORMIX 'TABLE &TABLE& ABINDEX(C)' "Hint4SybaseASE
0000045 * MSSQLNT 'TABLE &TABLE& ABINDEX(C)'. "#EC CI_HINTS
16.1.4 Access on SRT_RTC_DATA in
CL_SRT_WSP_CONFIG_RTC_CFG=====
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 414
251012
0,46
1311
1311
DELETE
FROM
"SRT_RTC_DATA"
WHERE
"CLIENT" = @P1 AND "BINDING_KEY" = @P2 /*
R3:CL_SRT_WSP_CONFIG_RTC_CFG=====CP:8267 T:SRT_RTC_DATA M:400 */
Execution Plan
DELETE
(@P1 nvarchar(3),@P2 nvarchar(32))DELETE FROM "SRT_RTC_DATA" WHERE
"CLIENT" = @P1 AND
"BINDING_KEY" = @P2 /* R3:CL_SRT_WSP_CONFIG_RTC_CFG=====CP:8267
T:SRT_RTC_DATA M:400 */
Estimated rows: 1311
Subtree costs: 0,99458
|-- Clustered Index Delete
|--Estimated rows: 1311
|--Estimated I/O costs: 0,971827
|--Estimated CPU costs: 0,005244
|--Subtree costs: 0,99458
|-- Top
|--Estimated rows: 1311
|--Estimated CPU costs: 0,0001311
|--Subtree costs: 0,0175091
|-- Index Seek SEEK: [SRT_RTC_DATA].BINDING_KEY EQ [@P2] AND
[SRT_RTC_DATA].CLIENT
EQ [@P1] ORDERED 1
|--Estimated rows: 1311
|--Estimated I/O costs: 0,0157789
|--Estimated CPU costs: 0,0015991
|--Subtree costs: 0,017378
Program Data:
Origin of ABAP coding
Program Name
Line
Last
Last
Created
Changed Changed
By
By
On
CL_SRT_WSP_CONFIG_RTC_CFG=====CM00
0000019 SAP
6
SAP
23.10.2015
0000010
0000011 srt_wsp_error_is_initial config_key 'config key'. "#EC NOTEXT
0000012 srt_wsp_check_charset1 config_key.
0000013
0000014 me->check_framework_id( config_key ).
0000015
0000016 * delete RTC tables
0000017 SELECT * FROM srt_rtc_bndg INTO TABLE lt_srt_rtc_bndg WHERE
config_key = config_key.
0000018 LOOP AT lt_srt_rtc_bndg ASSIGNING <srt_rtc_bndg>.
*>>>>>>>>>>>>>>>>>
0000019 DELETE FROM srt_rtc_data WHERE binding_key = <srt_rtc_bndg>binding_key.
0000020 DELETE FROM srt_rtc_datal WHERE binding_key = <srt_rtc_bndg>binding_key.
0000021 DELETE FROM srt_rtc_data_rt WHERE binding_key = <srt_rtc_bndg>binding_key.
*<<<<<<<<<<<<<<<<<<
0000022 ENDLOOP.
0000023 DELETE FROM srt_rtc_dir WHERE config_key = config_key.
0000024 DELETE FROM srt_rtc_bndg WHERE config_key = config_key.
16.1.5 Access on SRT_RTC_DATA in
CL_SRT_WSP_CONFIG_RTC_CFG=====
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 542754
378360
0,70
1
1
INSERT INTO "SRT_RTC_DATA" ( "CLIENT" ,"BINDING_KEY" ,"STATE"
,"RECORD_TYPE" ,"SUBJ_ID" ,"PROP_LIST_ID" ,"PROP_ID" ,
"SUBJ_PARENT_ID" ,"SUBJ_TYPE" ,"SUBJ_STATE" ,"PROP_LIST_STATE"
,"PROP_LIST_PREF" ,"PROP_LIST_TYPE" ,"PROP_KEY" ,"PROP_STATE" ,
"PROP_NAME" ,"PROP_NAMESPACE" ,"PROP_VALUE" ) VALUES( @P1 , @P2 ,
@P3 , @P4 , @P5 , @P6 , @P7 , @P8 , @P9 , @P10 , @P11 , @P12 ,
@P13 , @P14 , @P15 , @P16 , @P17 , @P18 ) /*
R3:CL_SRT_WSP_CONFIG_RTC_CFG=====CP:6047 T:SRT_RTC_DATA M:400 */
Execution Plan
INSERT
(@P1 nvarchar(3),@P2 nvarchar(32),@P3 nvarchar(1),@P4 nvarchar(2),@P5 int,@P6
int,@P7
int,@P8 int,@P9 nvarchar(2),@P10 nvarchar(1),@P11 nvarchar(1),@P12 smallint,@P13
nvarchar(1),@P14 nvarchar(24),@P15 nvarchar(1),@P16 nvarchar(120),@P17
nvarchar(12
Estimated rows: 1
Subtree costs: 0,0400052
|-- Clustered Index Insert SET: [PCD].[pcd].[SRT_RTC_DATA].[CLIENT] =
RaiseIfNullInsert([@P1]),[PCD].[pcd].[SRT_RTC_DATA].[BINDING_KEY] =
RaiseIfNullInsert([@P2]),[PCD].[pcd].[SRT_RTC_DATA].[STATE] =
RaiseIfNullInsert([@P3]),[PCD].[pcd].[SRT_RTC_DA
|--Estimated rows: 1
|--Estimated I/O costs: 0,04
|--Estimated CPU costs: 0,000004
|--Subtree costs: 0,0400052
Program Data:
Origin of ABAP coding
Program Name
Line
Last
Last
Created
Changed Changed
By
By
On
CL_SRT_WSP_CONFIG_RTC_CFG=====CM00
0000176 SAP
4
SAP
0000167 endif.
0000168
0000169 insert srt_rtc_bndg from table lt_srt_rtc_bndg[].
0000170 if sy-subrc <> 0.
0000171 me->if_srt_wsp_config_rtc_cfg~delete_rtc_config( config_key ).
0000172 message e009(srt_wsp) with 'SRT_RTC_BNDG' into srt_wsp_dummy.
0000173 srt_wsp_raise_t100_message.
0000174 endif.
0000175
*>>>>>>>>>>>>>>>>>
0000176 insert srt_rtc_data from table lt_srt_rtc_data[].
0000177 if sy-subrc <> 0.
0000178 me->if_srt_wsp_config_rtc_cfg~delete_rtc_config( config_key ).
*<<<<<<<<<<<<<<<<<<
0000179 message e009(srt_wsp) with 'SRT_RTC_DATA' into srt_wsp_dummy.
0000180 srt_wsp_raise_t100_message.
0000181 endif.
16.1.6 Access on UST10S in SAPLSUSI
23.10.2015
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 49437
553704
0,02
677
1
SELECT "MANDT" ,"PROFN" ,"AKTPS" ,"OBJCT" ,"AUTH"
FROM
"UST10S" ,(SELECT "C_0" = @P1 , "C_1" = @P2 UNION SELECT @P3 , @P4 UNION
SELECT @P5 , @P6 UNION SELECT @P7 , @P8 UNION
SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 , @P14
UNION SELECT @P15 , @P16 UNION SELECT @P17 , @P18
UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23
, @P24 UNION SELECT @P25 , @P26 UNION SELECT @P27 ,
@P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT
@P33 , @P34 UNION SELECT @P35 , @P36 UNION SELECT @P37
, @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION
SELECT @P43 , @P44 UNION SELECT @P45 , @P46 UNION SELECT
@P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION
SELECT @P53 , @P54 UNION SELECT @P55 , @P56 UNION
SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62
UNION SELECT @P63 , @P64 UNION SELECT @P65 , @P66
UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71
, @P72 UNION SELECT @P73 , @P74 UNION SELECT @P75 ,
@P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT
@P81 , @P82 UNION SELECT @P83 , @P84 UNION SELECT @P85
, @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION
SELECT @P91 , @P92 UNION SELECT @P93 , @P94 UNION SELECT
@P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) "t_00"
WHERE
"UST10S" ."MANDT" = @P101 AND "UST10S" ."PROFN" = "t_00" ."C_0" AND
"UST10S" ."AKTPS" = "t_00" ."C_1" /* R3:SAPLSUSI:772 T:
UST10S M:400 */
Execution Plan
|-- Nested Loops
|-- Merge Join
|-- Clustered Index Seek SEEK: [UST10S].MANDT EQ [@P101] AND [UST10S].PROFN
EQ
[Union1003] AND [UST10S].AKTPS EQ [Union1004] ORDERED 1
Program Data:
Origin of ABAP coding
Program Name Line
Created By Last Changed By Last Changed On
LSUSIU02
0000375 SAP
SAP
23.10.2015
0000366 INTO TABLE ist_usr10
0000367 PACKAGE SIZE c_package_size.
0000368 IF sy-subrc = 0.
0000369 SELECT * FROM ust10c CLIENT SPECIFIED INTO TABLE ist_ust10c
0000370 FOR ALL ENTRIES IN ist_usr10
0000371 WHERE mandt = client
0000372 AND profn = ist_usr10-profn
0000373 AND aktps = ist_usr10-aktps
0000374 ORDER BY PRIMARY KEY.
*>>>>>>>>>>>>>>>>>
0000375 SELECT * FROM ust10s CLIENT SPECIFIED INTO TABLE ist_ust10s
0000376 FOR ALL ENTRIES IN ist_usr10
0000377 WHERE mandt = client
0000378 AND profn = ist_usr10-profn
0000379 AND aktps = ist_usr10-aktps
0000380 ORDER BY PRIMARY KEY.
0000381 CLEAR soll_ust10c[].
0000382 CLEAR soll_ust10s[].
*<<<<<<<<<<<<<<<<<<
0000383 LOOP AT ist_usr10 ASSIGNING <ist_usr10>.
0000384 IF <ist_usr10>-typ = colectprof.
0000385 PERFORM fill_ust10c TABLES part_ust10c USING <ist_usr10>.
16.1.7 Access on SWWWIHEAD in RSWUWFML2
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 4963
90010
18,14
1
1
SELECT "WI_ID" ,"TCLASS"
FROM
"SWWWIHEAD"
WHERE
"CLIENT" = @P1 AND NOT "WI_RH_TASK" IN ( @P2 , @P3 , @P4 , @P5 , @P6 ,
@P7 , @P8 , @P9 , @P10 , @P11 ) AND "WI_STAT" = @P12 AND
"WI_TYPE" = @P13 AND "CREA_TMP" > @P14 AND "CREA_TMP" <= @P15 /*
R3:RSWUWFML2:2927 T:SWWWIHEAD M:400 */
Execution Plan
|-- Nested Loops
|-- Nested Loops
|-- Merge Interval
|-- Sort
|-- Index Seek SEEK: [SWWWIHEAD].CLIENT EQ [@P1] AND
[SWWWIHEAD].WI_TYPE EQ [@P13]
AND [SWWWIHEAD].WI_STAT EQ [@P12] ORDERED 1 WHERE:
[PCD].[pcd].[SWWWIHEAD].
[CREA_TMP]>[@P14] AND [PCD].[pcd].[SWWWIHEAD].[CREA_TMP]<=[@P15]
AND ([PCD].
[pcd].[SWW
|-- Clustered Index Seek SEEK: [SWWWIHEAD].CLIENT EQ
[PCD].[pcd].[SWWWIHEAD].[CLIENT]
AND [SWWWIHEAD].WI_ID EQ [PCD].[pcd].[SWWWIHEAD].[WI_ID] ORDERED 1
Program Data:
Origin of ABAP coding
Program Name Line
Created By Last Changed By Last Changed On
RSWUWFML2 0001730 SAP
SAP
23.10.2015
0001721 %_HINTS
0001722 INFORMIX 'TABLE &TABLE& ABINDEX(C)' "Hint4SybaseASE
0001723 DB2 'USE VALUES FOR OPTIMIZATION'
0001724 DB2 '&SUBSTITUTE VALUES&'.
0001725
0001726 * no longer select waiting work items
0001727
0001728 ELSE.
0001729 * Use the task index.
*>>>>>>>>>>>>>>>>>
0001730 SELECT wi_id tclass
0001731 INTO CORRESPONDING FIELDS OF TABLE lt_wi_data
0001732 FROM swwwihead
0001733 WHERE
0001734 wi_rh_task IN task_sel AND
0001735 wi_stat = wi_status_ready AND
0001736 wi_type = wi_normal AND
0001737 * note 969538:
0001738 crea_tmp > l_from_tstamp AND
0001739 crea_tmp <= l_to_tstamp.
0001740
0001741 * Add all the deadline items.
*<<<<<<<<<<<<<<<<<<
0001742 SELECT wi_id tclass
0001743 APPENDING CORRESPONDING FIELDS OF TABLE lt_wi_data
0001744 FROM swwwihead
16.1.8 Access on UST10C in SAPLSUSI
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 56429
49080
0,06
13
1
SELECT "MANDT" ,"PROFN" ,"AKTPS" ,"SUBPROF"
FROM
"UST10C" ,(SELECT "C_0" = @P1 , "C_1" = @P2 UNION SELECT @P3 , @P4 UNION
SELECT @P5 , @P6 UNION SELECT @P7 , @P8 UNION
SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 , @P14
UNION SELECT @P15 , @P16 UNION SELECT @P17 , @P18
UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23
, @P24 UNION SELECT @P25 , @P26 UNION SELECT @P27 ,
@P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT
@P33 , @P34 UNION SELECT @P35 , @P36 UNION SELECT @P37
, @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION
SELECT @P43 , @P44 UNION SELECT @P45 , @P46 UNION SELECT
@P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION
SELECT @P53 , @P54 UNION SELECT @P55 , @P56 UNION
SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62
UNION SELECT @P63 , @P64 UNION SELECT @P65 , @P66
UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71
, @P72 UNION SELECT @P73 , @P74 UNION SELECT @P75 ,
@P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT
@P81 , @P82 UNION SELECT @P83 , @P84 UNION SELECT @P85
, @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION
SELECT @P91 , @P92 UNION SELECT @P93 , @P94 UNION SELECT
@P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) "t_00"
WHERE
"UST10C" ."MANDT" = @P101 AND "UST10C" ."PROFN" = "t_00" ."C_0" AND
"UST10C" ."AKTPS" = "t_00" ."C_1" /* R3:SAPLSUSI:770 T:
UST10C M:400 */
Execution Plan
|-- Nested Loops
|-- Merge Join
|-- Clustered Index Seek SEEK: [UST10C].MANDT EQ [@P101] AND
[UST10C].PROFN EQ
[Union1003] AND [UST10C].AKTPS EQ [Union1004] ORDERED 1
Program Data:
Origin of ABAP coding
Program Name Line
Created By Last Changed By Last Changed On
LSUSIU02
0000369 SAP
SAP
23.10.2015
0000360 SELECT * FROM usr10 CLIENT SPECIFIED
0000361 WHERE mandt = client
0000362 ORDER BY PRIMARY KEY. "#EC CI_GENBUFF
0000363
0000364 DO.
0000365 FETCH NEXT CURSOR usr10_cursor
0000366 INTO TABLE ist_usr10
0000367 PACKAGE SIZE c_package_size.
0000368 IF sy-subrc = 0.
*>>>>>>>>>>>>>>>>>
0000369 SELECT * FROM ust10c CLIENT SPECIFIED INTO TABLE ist_ust10c
0000370 FOR ALL ENTRIES IN ist_usr10
0000371 WHERE mandt = client
0000372 AND profn = ist_usr10-profn
0000373 AND aktps = ist_usr10-aktps
0000374 ORDER BY PRIMARY KEY.
0000375 SELECT * FROM ust10s CLIENT SPECIFIED INTO TABLE ist_ust10s
0000376 FOR ALL ENTRIES IN ist_usr10
*<<<<<<<<<<<<<<<<<<
0000377 WHERE mandt = client
0000378 AND profn = ist_usr10-profn
0000379 AND aktps = ist_usr10-aktps
16.1.9 Access on TTREE_SFW_NODES in SAPLSHI25
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 32370
31568
0,98
1
1
SELECT "SFW_ASS_ID" ,"SWITCH_ID" ,"TREE_ID" ,"NODE_ID" ,"REACTION"
FROM
"TTREE_SFW_NODES" ,(SELECT "C_0" = @P1 , "C_1" = @P2 UNION SELECT @P3
, @P4 UNION SELECT @P5 , @P6 UNION SELECT @P7 , @P8
UNION SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 ,
@P14 UNION SELECT @P15 , @P16 UNION SELECT @P17 , @P18
UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23
, @P24 UNION SELECT @P25 , @P26 UNION SELECT @P27 ,
@P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT
@P33 , @P34 UNION SELECT @P35 , @P36 UNION SELECT @P37
, @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION
SELECT @P43 , @P44 UNION SELECT @P45 , @P46 UNION SELECT
@P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION
SELECT @P53 , @P54 UNION SELECT @P55 , @P56 UNION
SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62
UNION SELECT @P63 , @P64 UNION SELECT @P65 , @P66
UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71
, @P72 UNION SELECT @P73 , @P74 UNION SELECT @P75 ,
@P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT
@P81 , @P82 UNION SELECT @P83 , @P84 UNION SELECT @P85
, @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION
SELECT @P91 , @P92 UNION SELECT @P93 , @P94 UNION SELECT
@P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) "t_00"
WHERE
"TTREE_SFW_NODES" ."TREE_ID" = "t_00" ."C_0" AND "TTREE_SFW_NODES"
."NODE_ID" = "t_00" ."C_1" /* R3:SAPLSHI25:114 T:
TTREE_SFW_NODES M:000 */
Execution Plan
|-- Nested Loops
...
Program Data:
Origin of ABAP coding
Program Name Line
Created By Last Changed By Last Changed On
LSHI25U02 0000033 SAP
SAP
23.10.2015
0000024 DATA: del_start_index LIKE sy-tabix,
0000025 del_stop_index LIKE sy-tabix,
0000026 tmp_start LIKE sy-tabix,
0000027 del_node_level TYPE hier_iface-node_level.
0000028
0000029 *End Of Insertion MPRE 08.09.2006
0000030
0000031 *
0000032 if it_nodes[] is not initial. "do not execute select with empty for-all-entries-table
*>>>>>>>>>>>>>>>>>
0000033 SELECT * FROM ttree_sfw_nodes INTO TABLE switches
0000034 FOR ALL ENTRIES IN it_nodes
0000035 WHERE tree_id = it_nodes-tree_id
0000036 AND node_id = it_nodes-node_id.
0000037 endif.
0000038 ref_nodes[] = it_nodes[].
*<<<<<<<<<<<<<<<<<<
0000039 DELETE ref_nodes WHERE reftree_id EQ space AND refnode_id EQ space.
0000040 IF ref_nodes[] IS NOT INITIAL.
0000041 SELECT * FROM ttree_sfw_nodes INTO TABLE ref_switches
16.1.10 Access on UST12 in /GRCPI/CL_GRIA_AUTH===========
Statement Data:
Cache Statistics
Total
Object Total
Elapsed
Estimated
elapsed
Records/Execution
type
executions
time[ms]/Record
Records/Execution
time[ms]
TABLE 729
40808
0,70
80
1
SELECT "OBJCT" ,"AUTH" ,"FIELD" ,"VON" ,"BIS"
FROM
"UST12" ,(SELECT "C_0" = @P1 , "C_1" = @P2 UNION SELECT @P3 , @P4 UNION
SELECT @P5 , @P6 UNION SELECT @P7 , @P8 UNION
SELECT @P9 , @P10 UNION SELECT @P11 , @P12 UNION SELECT @P13 , @P14
UNION SELECT @P15 , @P16 UNION SELECT @P17 , @P18
UNION SELECT @P19 , @P20 UNION SELECT @P21 , @P22 UNION SELECT @P23
, @P24 UNION SELECT @P25 , @P26 UNION SELECT @P27 ,
@P28 UNION SELECT @P29 , @P30 UNION SELECT @P31 , @P32 UNION SELECT
@P33 , @P34 UNION SELECT @P35 , @P36 UNION SELECT @P37
, @P38 UNION SELECT @P39 , @P40 UNION SELECT @P41 , @P42 UNION
SELECT @P43 , @P44 UNION SELECT @P45 , @P46 UNION SELECT
@P47 , @P48 UNION SELECT @P49 , @P50 UNION SELECT @P51 , @P52 UNION
SELECT @P53 , @P54 UNION SELECT @P55 , @P56 UNION
SELECT @P57 , @P58 UNION SELECT @P59 , @P60 UNION SELECT @P61 , @P62
UNION SELECT @P63 , @P64 UNION SELECT @P65 , @P66
UNION SELECT @P67 , @P68 UNION SELECT @P69 , @P70 UNION SELECT @P71
, @P72 UNION SELECT @P73 , @P74 UNION SELECT @P75 ,
@P76 UNION SELECT @P77 , @P78 UNION SELECT @P79 , @P80 UNION SELECT
@P81 , @P82 UNION SELECT @P83 , @P84 UNION SELECT @P85
, @P86 UNION SELECT @P87 , @P88 UNION SELECT @P89 , @P90 UNION
SELECT @P91 , @P92 UNION SELECT @P93 , @P94 UNION SELECT
@P95 , @P96 UNION SELECT @P97 , @P98 UNION SELECT @P99 , @P100 ) "t_00"
WHERE
"UST12" ."MANDT" = @P101 AND "UST12" ."OBJCT" = "t_00" ."C_0" AND "UST12"
."AUTH" = "t_00" ."C_1" AND "UST12" ."AKTPS" = @P102
AND "UST12" ."FIELD" IN ( @P103 , @P104 , @P105 , @P106 , @P107 , @P108 ,
@P109 , @P110 , @P111 , @P112 , @P113 , @P114 , @P115
, @P116 , @P117 , @P118 , @P119 , @P120 , @P121 , @P122 , @P123 , @P124 ,
@P125 , @P126 , @P127 , @P128 , @P129 , @P130 , @P131
, @P132 , @P133 , @P134 , @P135 , @P136 , @P137 ) AND ( "UST12" ."VON" IS NOT
NULL OR "UST12" ."VON" IS NULL ) AND ( "UST12" .
"BIS" IS NOT NULL OR "UST12" ."BIS" IS NULL ) /*
R3:/GRCPI/CL_GRIA_AUTH===========CP:1348 T:UST12 M:400 */
Execution Plan
Program Data:
Origin of ABAP coding
Last
Last
Created
Program Name
Line
Changed Changed
By
By
On
/GRCPI/CL_GRIA_AUTH===========CM004 0000110 SAP
SAP
23.10.2015
0000101 FOR ALL ENTRIES IN lt_prof
0000102 WHERE profn = lt_prof-profile
0000103 AND aktps = 'A'
0000104 AND ( objct IS NULL OR objct IS NOT NULL )
0000105 AND ( auth IS NULL OR auth IS NOT NULL ).
0000106 ENDIF.
0000107 ENDIF.
0000108
0000109 IF lt_ust10s IS NOT INITIAL.
*>>>>>>>>>>>>>>>>>
0000110 SELECT objct auth field von bis
0000111 FROM ust12 "#EC CI_BYPASS "#EC CI_GENBUFF
0000112 INTO CORRESPONDING FIELDS OF TABLE lt_object_values
0000113 FOR ALL ENTRIES IN lt_ust10s
0000114 WHERE objct = lt_ust10s-objct
0000115 AND auth = lt_ust10s-auth
0000116 AND aktps = 'A'
0000117 AND field IN it_field_range
0000118 AND ( von IS NOT NULL OR von IS NULL )
0000119 AND ( bis IS NOT NULL OR bis IS NULL ).
0000120
0000121 ENDIF.
*<<<<<<<<<<<<<<<<<<
0000122
0000123 IF iv_count IS NOT INITIAL.
0000124 /grcpi/cl_gria_auth=>gv_auth = iv_count.
17 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs). Diagrams
are built weekly once the EarlyWatch Alert service is activated.
In this report, historical data for "Transaction Activity", "System Performance", and
"Database Performance" is taken directly from workload monitor ST03, because
EarlyWatch Alert data has been accumulated for less than 20 sessions.
In this section, a "week" is from Monday to Sunday. The date displayed is the Sunday of
the week.
17.1 System Activity
The following diagrams show the system activity over time.
The "Transaction Activity" diagram below depicts transaction activity in the system over
time.
- Total Activity: Transaction steps performed each week (in thousands)
- Dialog Activity: Transaction steps performed in dialog task each week (in thousands)
- Peak Activity: Transaction steps (in thousands) during the peak hour; this peak hour is
calculated as the hour with the maximum dialog activity in the ST03 time profile divided
by 5 working days per week.
(Peak Activity is absent if "Activity Data" is taken from ST03 data directly).
Historical data for "Transaction Activity" is obtained from the Workload Monitor (ST03).
The "User Activity" diagram below shows the user activity on the system over time.
- Total Users: Total users that logged on in one week.
- Active Users: Users who performed more than 400 transaction steps in one week.
17.2 Response Times
The following diagrams show how the response time varies over time.
The "System Performance" diagram below shows the average response time in dialog tasks
for the previous week.
Historical data for "System Performance" is obtained from the Workload Monitor (ST03).
The "Database Performance" diagram below shows the average DB response time in dialog
tasks.
The "Top 5 transactions" diagram below shows the average response time in dialog tasks
for the top 5 transactions.
The "Transaction Code" table below shows the load percentage caused by the top 5
transactions.
Transaction Code
ME53N
ME23N
ME22N
FAGLB03
SESSION_MANAGER
Load (%)
3,6
4,7
5,5
6,9
10,8
17.3 Application profile
In the following, we analyzed the trend within the following time frames:
Short term: From calendar week 43/2015 to 46/2015
Long term: From calendar week 34/2015 to 46/2015
The table below shows the time profile of the top applications by total workload during the
analyzed period.
Top Applications by Response Time
% of
Avg.
System
Task
Resp.
Application
Total
Type
Time
Resp.
in ms
Time
Dialog SESSION_MANAGER 152664 9
852
Dialog ME22N
94517 6
1020
Dialog ME23N
64201 4
324
Dialog FAGLB03
59499 4
999
Dialog ME21N
57190 3
777
Dialog Z_PDF
50460 3
9201
Dialog ZFI_REP_GAR
46772 3
6790
Total
Resp.
Time
in s
Avg.
Long
Short
Avg.
CPU
Term
Term
DB
Time
Growth Growth Time
in
(%/year) (%/year) in ms
ms
221,9 396,4- 100 84
164,2
417,0 97
145
139,9
86,3 79
68
356,0 5.379,0 536 293
8,5 763,7- 82
70
65,7- 235,2 30
49
4,9- 1.059,0- 405 1859
Top Applications by Response Time
Task
Application
Type
Total
Resp.
Time
in s
Dialog ME53N
Dialog ZMM_PLANCPA
Dialog FBL1N
Dialog ME51N
Dialog ZMM_0041
Dialog S_ALR_87011990
Dialog FAGLL03
Dialog FBL3N
Dialog ME2M
Dialog FBL5N
Dialog S_ALR_87013611
Dialog ME5A
Dialog ME2L
46152
45547
39473
37939
37356
33054
32158
30695
28189
25566
24757
22106
21834
% of
Avg.
Avg. Long
Short
Avg.
System
CPU
Resp. Term
Term
DB
Total
Time
Time Growth Growth Time
Resp.
in
in ms (%/year) (%/year) in ms
Time
ms
3
410
93,7 301,5- 76
98
3
1348
12,6- 572,0- 709 370
2
277
73,9 1.175,0- 101 72
2
728
17,5 1.033,4- 35
89
2
3322
97,8 891,6- 457 1461
2
20229
233,9
374,9 13456 5734
2
3252
147,4- 348,9 2338 282
2
487
195,4 652,6- 157 153
2
2657
226,3
169,9 1389 933
2
306
59,4
99,9 69
63
1
1267
112,3
172,0 230 601
1
840
0,8- 976,4- 90
303
1
1970
31,2- 1.619,3- 1115 741
The graph below shows how the average response time of the top five applications varies
over time. Data is normalized to 100% equaling the average value.
17.4 System Operation
The following diagram or table shows important KPIs for system operation.
17.5 Hardware Capacity
Report time frame: Service data was collected starting at 23.11.2015 04:47:31. This took 7
minutes.
You can see sample EarlyWatch Alert reports on SAP Service Marketplace at /EWA ->
Library -> Media Library.
General information about the EarlyWatch Alert is available at SAP Note 1257308.
Additional Information
Area
Solution Manager System
Solution Manager Version
Service Tool
Service Content Update On
Value
SCL
SOLUTION MANAGER 7.1
701_2010_1 SP22
17.11.2015