EarlyWatch Alert - PETL ECC Landscape 1 Service Summary Note: All recommendations provided in this report are based on our general experience. We advise that you test our recommendations before using them in your production system. Note that EarlyWatch Alert is an automatic service. Section Overview Note: For more information about EarlyWatch Alert, a sample EarlyWatch Alert report with explanations is available in the Media Library on SAP Service Marketplace ( EWA ). This provides an overview of the check rating strategy and the KPIs that trigger the alerts in this service. Alert Message Overview The service data were collected starting at 01.10.2012 04:19:37 taking 23 minutes. Note: If you need help investigating the alerts listed, order an EarlyWatch contract by contacting your local support organization or by creating a customer message in component SV-BO. If you already have such a contract, a detailed analysis can be performed during the next Service Session. Address the topic during preparation for the session. E - Mail Hint: to search, select this document and choose Ctrl+F Date: 01.10.2012 Report: PPR, Unknown CO-OM BC- CCM BC MM FI PP PY LE SD CO LO QM PM Installation: 0020677209 Session: 1000000001529 During this EarlyWatch Alert Session, we detected issues that could potentially affect your system. We recommend that you take corrective action as soon as possible. System Configuration System Performance Workload Distribution SAP System Operating Database Settings Database Administration Authorization Checks Rating Checked Area Medium There are security issues in your system. New Medium We found many ABAP dumps in your system. New Priority Description New Alert Page 1 of 39 Report 05-Oct-12 saphtmlp://htmlviewer.sap.com/uWweYNUAKV6D9G0cLNwC0G/index.html
Transcript
EarlyWatch Alert - PETL ECC
Landscape
1 Service Summary
Note: All recommendations provided in this report are based on our general experience. We advise that you test our recommendations before using them in your production system. Note that EarlyWatch Alert is an automatic service.
Section Overview
Note: For more information about EarlyWatch Alert, a sample EarlyWatch Alert report with explanations is available in the Media Library on SAP Service Marketplace ( EWA ). This provides an overview of the check rating strategy and the KPIs that trigger the alerts in this service.
Alert Message Overview
The service data were collected starting at 01.10.2012 04:19:37 taking 23 minutes.
Note: If you need help investigating the alerts listed, order an EarlyWatch contract by contacting your local support organization or by creating a customer message in component SV-BO. If
you already have such a contract, a detailed analysis can be performed during the next Service Session. Address the topic during preparation for the session.
E-Mail Hint: to search, select this document and choose Ctrl+F
Date: 01.10.2012
Report: PPR, Unknown CO-OM BC-CCM BC MM FI PP PY LE SD
CO LO QM PMInstallation: 0020677209
Session: 1000000001529
During this EarlyWatch Alert Session, we detected issues that could potentially affect your
system. We recommend that you take corrective action as soon as possible.
System Configuration
System Performance
Workload Distribution
SAP System Operating
Database Settings
Database Administration
Authorization Checks
Rating Checked Area
Medium There are security issues in your system. New
Medium We found many ABAP dumps in your system. New
Note: If you experience serious performance problems, create a customer message on component SV-BO with the priority "high" or "very high".
2 Performance Indicators for PPR
The following table shows the relevant performance indicators in various system areas.
3 System Configuration
3.1 Hardware Configuration
The table below shows the detected hardware configuration:
System Performance Active Users 147 up
Avg. Response Time in Dialog Task
817 ms up
Max. Dialog Steps per Hour 26599 up
Avg. Response Time at Peak
Dialog Hour951 ms up
Avg. Availability per Week 99 % steady
Database PerformanceAvg. DB Request Time in Dialog Task
479 ms up
Avg. DB Request Time in Update
Task247 ms steady
Database Space Management
DB Size627.98 GB
steady
Last Month DB Growth 2.58 GB down
Area Indicators Value Trend
To ensure optimal support of your SAP system, the SAP components, database, and operating system used must all be supported. Detailed information about SAP's platform support is available on SAP Service Marketplace at http://service.sap.com/platforms.
Your SAP kernel release (release 700, patch level 179) is not up-to-date.
Without the latest kernel patch level, you do not have the latest error corrections and improvements SAP offers to its customers.
You might encounter errors or performance issues that have already been fixed.
Recommendation: Ensure that you are using the SAP kernel recommended together with the latest SAP Stacks of your product.
Refer to SAP Service Marketplace for detailed information: http://service.sap.com/sp-stacks
SAP releases Support Package Stacks including kernel patches on a regular basis (generally 2-4 times a year). Therefore, we also suggest you create a strategy for periodically applying these stacks.
In special cases, you might need to use a more recent kernel patch than the one shipped
with the latest Support Package Stack for your product. SAP Support should inform you if this is the case.
3.2.3 Implemented SAP Notes via SAP Notes Assistant
SAP_HRCVE 600 0
SAP_HRCZA 600 0
SAP_HRGXX 600 0
SAP_HRRXX 600 0
SEM-BW 600 13 SAPKGS6013 SAP SEM Server
ST-A/PI 01L_ECC600 0 SAPKITAR7D
SAP Service Tools
for Applications Plug-In
ST-PI 2005_1_700 6 SAPKITLQI6SAP Solution Tools
Plug-In
Support Packages
SAP
Component
SAP Component Version
Patch
LevelSupport Package
Component
Description
0001706872 0003 PY-INPY-IN: Union Budget Changes for Year
2012
0001575366 0001 PY-INHINCALC0:Tax calculation inconsistent in case of invalid PAN
0001572614 0005 PY-INTax calculations inconsistent for emp. without a vaild PAN
0001568264 0005 PY-IN Budget Changes 2011
0001562761 0003 XX-CSC-IN-MMRun time error due to m/y overflow in Credit Transfer- J2I8
0001558475 0005 PY-INAmendments to IT calculation notified under circular:08/2010
0001493450 0003 FI-GL-FLReversal not poss. due to missing values in required field
System PPR is not fully prepared for service delivery.
For a detailed analysis, refer to the checks below. For general information about service preparation, see SAP Note 91488 (SAP Support Services: Central Preparation Note). Ensure that all functionality mentioned in this SAP Note is up-to-date, especially connections, collectors, and service tools.
0001455469 0003 XX-CSC-INDuties not displayed under correct column in RG23C part2
0001406960 0012 PA-PM-CPNo commitment references when transferring payroll result
0001405087 0002 XX-CSC-INDuties not displayed under correct column in RG23A part2
0001382528 0004 FI-SL-SLFI general ledger: Performance of FI
data selectn processes
0001350822 0007 PA-PM-CPFinancing not adjusted for periods that are not integrated
0001336899 0002 PA-PM-CPSystem does not update change history for PBC documents
0001332905 0002 PA-PM-CPRetroactive accounting date not set in spite of switch RECAL
0001329216 0003 FI-AA-AAFixed asset is incorrectly flagged as
incomplete
0001327534 0002 PA-PM-CPDocuments not created in the sequence of their due date
0001307798 0001MM-IV-LIV-CRE
MIRO: Balance is not updated
0001299997 0003BC-CCM-BTC-RUN
Message D01 in system log with reference to message BT 510
0001295661 0003 XX-CSC-IN-SDADC appear as AED(GSI) for monthly
utilized document in J2I9
0001283823 0005 XX-CSC-IN-MMChanges in heading and display of duty column for RG1 report
0001272102 0003 PA-PM-CP Error corrections for document closing
The last run of report RTCCTOOL was 00.00.0000, more than 30 days ago.
Recommendation: Run report RTCCTOOL, as described in SAP Note 91488, to check the latest
recommendations. If missing add-ons, transports, or SAP Notes are detected by RTCCTOOL, implement the recommendations provided by the tool.
3.3.2 Errors in Data Collection
The following exceptions were raised during data collection:
Recommendation: Review the SDCC(N) data collection log for this session. For function modules with an exception, check whether a help text is available when you double-click this exception. If you have access to SAP Notes, search for these errors and the corresponding short dumps or system log entries.
If you cannot resolve the problem, open a message in SV-SMG-SDD.
3.3.3 SAP OS Collector
3.3.3.1 Quality of Collected Data
The analysis below is based on the information in ST06 -> Detail analysis menu -> Compare recent days.
SAPOSCOL data quality is insufficient to perform hardware capacity checks in the SAP standard services. Check whether SAPOSCOL is active and stores data correctly (see SAPNote 189072 ).
If required, open a message on component BC-CCM-MON-OS to investigate any of the items below.
Days not Collected
Recommendation: Check whether SAPOSCOL is running and storing data correctly on
the above servers. Also check the SAPOSCOL version.
The following information can be found in transaction SM51:
4 Performance Overview PPR
The following table shows the average response times for various task types:
4.1 Current Workload
The following table lists the number of current users (measured from our workload analysis) in your system.
4.2 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 24000, the rating for the task is not performed and a blue line is entered in the table.
PECCCI_PPR_02 PECCCI
PECCDB_PPR_01 PECCDB
SAP Application Server SM51 Host Name
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.
The table below shows that no problem is expected on the application or database servers.
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.
4.3 Transaction Profile Check
The following tables show the response times and the number of dialog steps for the transactions that cause the highest workload in your system. NOTE: A business transaction normally consists of more than one dialog step. As a rough estimate, the actual number of business transactions
that are executed in your system is approximately one third of the total dialog steps shown. (Transaction CPIC/RFC is not taken into account.)
4.3.1 Transactions by Total Workload
The following tables list the activities with the highest contribution to the total workload.
Dia 1107728
Upd 67209
HTTP 0
Task StepsApplication Server Performance
Database Server Performance
Dia07-08
1213 1678 191 1355
Rating Task Time StepsAvg. Response Time (ms)
Avg. CPU Time (ms)
Avg. Database Time (ms)
Dia 1200 600
Upd 2400 1200
HTTP 1200 600
TaskReference for Avg. Response Time (ms)
Reference for Avg. DB time (ms)
Total 1175633 100,0 787,4 161,6 466,1 134,6
ZMM_DOCFLOW DIA 993 7,6 70736,6 20522,1 48182,8 732,7
SESSION_MANAGER DIA 76802 7,3 876,0 126,4 309,6 259,8
ZRECON DIA 139 5,1 341117,4 113934,0 186879,8 313,9
19.9% of the "Total Resp. Time" in the above table is caused by customer transactions.
37.7% of the "Total Resp. Time" in the above table is caused by customer transactions.
4.3.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.
17.2% of the "Total DB Time" in the above table is caused by customer transactions.
43.5% of the "Total DB Time" in the above table is caused by customer transactions.
5 Workload Distribution PPR
5.1 Workload by Application Module
The following graphics or tables 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 The 'unknown' section contains all programs that cannot be assigned to a standard SAP application module (for example, customer programs, an industry solution, or a third-party add-
on development).
Total 2033081 100,0 107,8
ZSD_PENDING_ORDER BTC 352 15,1 94054,2
ZDOCFLOW_MM BTC 29 14,7 1115051,5
RKO7CO88 BTC 4 12,4 6805230,0
PPIO_ENTRY BTC 28 6,6 517053,6
ZMM_MATERIAL_AGEING_NEW3_2130 BTC 2 5,9 6458233,5
RSBTCDEL BTC 21 4,9 511424,8
ZDOCFLOW_MM_FIX_LAY BTC 7 4,6 1436537,0
SAPKKA07 BTC 1 4,1 8883681,0
(BATCH) BTC 678829 4,0 12,9
ZDOCFLOW_MM_FIX_LAY1 BTC 7 3,2 998660,9
Database Load by Transactions (Batch/Spool)
Transaction TypeDialog Steps
Total DB Time in
%
Avg. DB Time in ms
The performance of your system was analyzed with respect to workload distribution. We did not detect any major problems that could affect the performance of your SAP System.
The following table or diagram shows the DB load caused by dialog, RFC, and background tasks
over different timeframes.
The data provided in the table represents the average number of database processes occupied by each task type in the database during the specified timeframes.
These statistics are calculated as a weekly average, which means 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. 24-hour monitoring can be enabled by implementing SAP Note 17750.
By comparing the load profiles for dialog and background activity, you can gain an overview of the volume of background activity during online working hours.
The graph above indicates that the CPUs can handle the database load. Therefore, the check is rated green.
5.3 RFC Communication
The performance of your system was analyzed with respect to the average call times and the workload created by remote function calls between the current system and other SAP and non-SAP systems. The following tables show statistics about RFCs. Note: Internal RFC communication (that means communication between the instances of the
analyzed system) is not shown in the tables. However, it is included in the 'Total' line.
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. The following table contains the number of update errors detected.
We did not detect any problems.
6.2 Table Reorganization
When analyzing your database, we detected large or rapidly growing tables or indexes.
Recommendation: Implement the SAP Notes listed below to reduce the size of some of these tables or indexes. Background: For more information about SAP Data Volume Management, see SAP Service
Marketplace at service.sap.com/dvm
6.3 Transports
Transports were not found in the period analyzed.
6.4 Program Errors (ABAP Dumps)
363 ABAP dumps have been recorded in your system in the period 24.09.2012 to 30.09.2012.
ABAP dumps are generally deleted after 7 days by default. To view the ABAP dumps in your
When checking the authorization checks, the system deems it critical if multiple users have the respective checked authorization in a client. In the context of these checks, critical means:
* More than 75 users are authorized in a client
* More than 10% of the users (at least 10) have the checked authorization in a client. (That is, an absolute figure of 10 or fewer users is ignored by the rating.)
As soon as this limit is exceeded in at least one client, the system assigns a yellow rating to the
check. This does not include clients 000 and 066. A red rating is not assigned.
We offer a Security Optimization Self-Service. This service is provided free of charge in the current version of SAP Solution Manager. We recommend that you make use of this service.
For more information, see SAP Service Marketplace at http://www.service.sap.com/SOS .
For further information about these checks (for example, about rating rules) refer to SAP Note 863362 .
7.1 Users Authorized to Display all Tables
Unauthorized access to sensitive data is possible if too many users have this authorization. The mentioned number of users for each client has the checked authorization.
Evaluated Risk - High
Recommendation: Use the Profile Generator (PFCG) to correct roles and/or transactions
SU02 (Maintain Profiles) / SU03 (Maintain Authorizations) to correct profiles and authorizations, depending on your environment. With the authorization info system (SUIM), you can check the results. For this check, you should take a look at the roles or profiles that include the authorization objects listed below.
Authorization objects: Object 1: S_TCODE with TCD=SE16, TCD=SE16N, TCD=SE17, TCD=SM30, or TCD=SM31 Object 2: S_TABU_DIS with ACTVT = 03 or 02 and DICBERCLASS = *
7.2 Users Authorized to Start all Reports
With this authorization, critical functions and reports that do not contain own authorization checks can be executed. The mentioned number of users for each client has the checked authorization.
Recommendation: Use the Profile Generator (PFCG) to correct roles and/or transactions SU02 (Maintain Profiles) / SU03 (Maintain Authorizations) to correct profiles and authorizations, depending on your environment. With the authorization info system (SUIM),
you can check the results. For this check, you should take a look at the roles or profiles that include the authorization objects listed below.
Authorization objects: Object 1: S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38 Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*
7.3 Users Authorized to Debug / Replace
This authorization provides access to data and functions, since any authorization check that is built in ABAP can be bypassed. In addition, you can change data during processing, which may lead to inconsistent results. The mentioned number of users for each client has the checked
authorization.
Evaluated Risk - High
Recommendation: Use the Profile Generator (PFCG) to correct roles and/or transactions SU02 (Maintain Profiles) / SU03 (Maintain Authorizations) to correct profiles and
authorizations, depending on your environment. With the authorization info system (SUIM), you can check the results. For this check, you should take a look at the roles or profiles that include the authorization objects listed below.
Authorization objects: Object 1: S_DEVELOP with ACTVT=02 (change) and OBJTYPE=DEBUG
Note: If you do not want to disable development in your system, you have to exclude the
OBJTYPE=DEBUG with ACTVT=02 from the profile and allow any other object type for S_DEVELOP. This means that development and debugging with visualization is still possible. You can achieve this by linking 2 authorizations to the object S_DEVELOP: one with all object
types (except for "DEBUG") and all activities, and another for the object type DEBUG only and all activities (except for 02).
8 Hardware Capacity
9 Database Settings
001 2 3
300 50 173
310 10 11
Client User Count Valid Users Rating
We have checked your system for potential CPU or memory bottlenecks and found that the hardware of your database and application servers is sufficient for the current workload.
The following table provides an overview of the load caused by different database users.
Listed for each database user is the: (a) Percentage of executed statements (b) Number of block reads from disk (indicative for the I/O load caused by this database user) (c) Number of buffers accessed
(d) Number of records returned as obtained from the shared pool (Oracle view V$SQL) at the time of the download
The first line with the name TOTAL indicates the total number of (a), (b), (c) and (d) for all the user names.
9.2 Database Parameters for PPR
We noticed that the following database parameters, which are currently active in your system, do not follow our standard recommendations. These standard recommendations cannot take into account possible special aspects for your system. Deviations from those standard recommendations may be necessary in your case. We therefore advise you to discuss theses
parameter settings in your next Service session.
9.2.0.1 Database Parameters
We have detected some problems with the settings of the database. These settings may affect performance.
'replication_dependency_tracking', otherwise you can switch it off.
9.2.0.2 Parameter EVENT
To provide special functionality or control system behavior, Oracle has a number of events. These can be activated in the configuration file and/or dynamically in the server manager or sqlplus.
In general, these events and parameters should be activated on request only. When they are no longer needed, they should be removed. However, it might be necessary to activate some events during normal database operation.
The following table displays the values for the parameter "event" as found in your system:
The following table lists events that may have to be activated. Please check the mentioned SAP Notes for details.
The following table lists events we found to be activated in your system, but which should only
be activated in special circumstances. Please check whether there are special reasons to set these events. If they are no longer needed, they should be removed.
sessions
Maximum number
of concurrent database sessions
96Please check SAP note 830576
shared_pool_reserved_size
Part of Shared
Pool for large statements
278132686Please check SAP note 830576
Parameters DescriptionCurrent value
Recommended value
event 10027 trace name context forever, level 1
10028 trace name context forever, level 1
10142 trace name context forever, level 1
10183 trace name context forever, level 1
10411 trace name context forever, level 1
10629 trace name context forever, level 32
10891 trace name context forever, level 1
38068 trace name context forever, level 100
14532 trace name context forever, level 1
38068 trace name context forever, level 100
38085 trace name context forever, level 1
38087 trace name context forever, level 1
44951 trace name context forever, level 1024
Parameter Current Value
10191 128221Increased memory consumption with Oracle >8.0.X
Recommendation: Increase the limit, or use SAPDBA to add a new data file to the tablespaces of the table above. Implementation: To determine the size needed, consider the tablespaces' history of storage
usage. Once a data file has been added, back up the extended tablespace. This ensures that the new state of the database can be recovered.
10.3 Oracle Release
We recommend that you install the latest Oracle patch set as soon as possible (see SAP Note
415900). Check SAP Note 871735 regularly for the latest patch set for Oracle 10.2.0. Note that in addition to the patch set, further bug fixes may be available and recommended. Refer to the following SAP Note(s):
11 Database server load from
expensive SQL statements - PPR
The table above shows the cumulative load of the problematic statements identified. If the database has been inactive for at least one day before the analysis is performed, the information
provided may not be accurate.
If the rating in the table is RED, we detected expensive SQL statements that cause a high load on your SAP system.
If the rating in the table is YELLOW, we detected some expensive SQL statements.
If the rating in the table is GREEN, the analysis of your system's SQL statement cache detected no significant problems.
The following table lists the load of each expensive SQL statement individually. The load of the
statement is evaluated against the current load in the database and the total load since startup. A more technical explanation is available in SAP Note 551646. The database administrator should conduct a detailed analysis, or you may prefer to order an EarlyWatch or Remote Performance analysis with focus "SQL Statement optimization".
The Technical Performance Optimization service is also available. This service is available within an
SAP Support Engagement only.
10.2.0 871096Oracle Database 10g - Patchsets/Patches for 10.2.0
Patch set
SAP Note number
Description
The expensive SQL statements that we have identified cause a significant load on the database server. This results in performance problems not only for the transactions that execute these statements but also for other users.
For further details on the rating of this check, refer to SAP Note 551646.
Note: If an object name in this table contains the character "/", it may be a statement to a join. If an object does not exist in the ABAP dictionary (transaction SE12) with the listed object name, check for each part of the join (items separated by "/").
003288 WHERE matnr_i IN s_matnr 003289 AND werks_i = s_werks-low 003290 AND lgort_i IN s_lgort 003291 AND bwart_i IN r_total 003292 AND sobkz_i IN r_sobkz.
"MANDT" = :A0 AND "MATNR_I" = :A1 AND "WERKS_I" = :A2 AND "BUDAT" <= :A3 OR "MANDT" = :A4 AND "MATNR_I" = :A5 AND "WERKS_I" = :A6 AND "BUDAT" <= :A7 OR "MANDT" = :A8 AND "MATNR_I" = :A9 AND "WERKS_I" = :A10 AND "BUDAT" <= :A11 OR "MANDT" =:A12 AND "MATNR_I" = :A13 AND "WERKS_I" = :A14 AND "BUDAT" <= :A15 OR "MANDT" = :A16 AND "MATNR_I" = :A17 AND "WERKS_I"= :A18 AND "BUDAT" <= :A19&
Program Data:
000724 * 000725 SELECT MBLNR ZEILE_I MJAHR BUDAT BWART_I MATNR_I WERKS_I 000726 MENGE_I SOBKZ_I SHKZG_I ebeln_i ebelp_i kzbew_i UMSOK_I KZVBR_I 000727 FROM WB2_V_MKPF_MSEG2 000728 INTO TABLE IT_MSEG1 000729 FOR ALL ENTRIES IN IT_FINAL 000730 WHERE MATNR_I = IT_FINAL-MATNR AND 000731 WERKS_I = IT_FINAL-WERKS AND 000732 BUDAT LE S_BUDAT.
000160 select * from trfcqout 000161 into table err_queue 000162 for all entries in err_qstate 000163 where qstate = err_qstate-qstate 000164 and dest = qdestlist-dest.
000143 000144 * Ermittlung der qRFC-Queues 000145 select distinct mandt qname dest 000146 from trfcqout 000147 into table qview 000148 where qname like qid_dbwcard 000149 and dest = qdestlist-dest 000150 and nosend = space.
11.1.6 Access on ATP_RESB
Statement Data:
TABLE 32908 86843 19510240 664517041 126626272
Cache Statistics
Object Type
Total Executions
Disk Reads
Buffer Gets
Records Processed
LQOWKU06 145 SAP SAP 24.12.2008
Origin of ABAP coding
Program Name Line Created By Last Changed By Last Changed On
"MANDT" = :A0 AND "MATNR" = :A1 AND "WERKS" = :A2 AND "XLOEK" = :A3 AND "KZEAR" = :A4 AND "BDTER" < :A5 AND "BDART" <> :A6 AND "SOBKZ" IN ( :A7 , :A8 ) AND "BDMNG" > "ENMNG" AND "TXTPS" = :A9 AND "SCHGT" = :A10 AND "DBSKZ" = :A11 AND ( "VORAB" IS NULL OR "VORAB" = :A12 )&
000033 WHERE matnr = atpmat-matnr 000034 AND werks = atpmat-werks 000035 AND xloek = space 000036 AND kzear = space 000037 AND bdter < atpmat-endwz 000038 AND bdart <> skbed 000039 AND sobkz IN (space, sobkzk) 000040 AND bdmng > atp_resb~enmng 000041 AND txtps = space 000042 AND schgt = space 000043 AND dbskz = space 000044 AND ( vorab IS NULL 000045 OR vorab = space ).
11.1.7 Access on JEST
Statement Data:
SELECT
*
FROM
"JEST"
WHERE
"MANDT" = :A0 AND "OBJNR" IN ( :A1 , :A2 , :A3 , :A4 , :A5 )&
000110 SELECT * FROM JEST CLIENT SPECIFIED 000111 APPENDING TABLE JEST_BUF 000112 FOR ALL ENTRIES IN OBJNR_TAB 000113 WHERE MANDT EQ CLIENT 000114 AND OBJNR = OBJNR_TAB-OBJNR.
11.1.8 Auxiliary Storage Quality Information
The following table shows the top tables (max. 20) that have an average record length of less than 4000 bytes, more than 100 chained rows in total, and a number of chained rows that is
over 5% of the total number of rows in the table (based on the available CBO statistics).
The following table shows the top "regular" (not partitioned, empty, index organized) tables (max. 20) that have more than 1000 blocks with the lowest storage quality (based on the available CBO statistics).
The following table shows the top "type normal" indexes (max. 20) that have more than 1000 blocks with the lowest storage quality (based on the available CBO statistics).
LBSVAU14 110 SAP SAP 09.12.2004
Origin of ABAP coding
Program Name Line Created By Last Changed By Last Changed On
All the information in this section is based on the Oracle CBO statistics. Thus if statistics are old, the data displayed may not be accurate.
12 Trend Analysis
This section contains the trend analysis for key performance indicators (KPIs). Diagrams are built week by week after activating the EarlyWatch Alert Service.
Historical data for "Transaction Activity" and "System Performance" is taken directly from workload monitor ST03 if data for less than 20 sessions has been accumulated. In this report, historical data
is taken directly from workload monitor ST03.
12.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).
