Ewa PPR

Report
Page 1 of 39
E-Mail Date: 01.10.2012 PPR, Unknown CO-OM BCReport: CCM BC MM FI PP PY LE SD CO LO QM PM Installation: 0020677209 Session: 1000000001529
Hint: to search, select this document and choose Ctrl+F
EarlyWatch Alert - PETL ECC Landscape 1 Service Summary

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. 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 Rating Checked Area System Configuration System Performance Workload Distribution SAP System Operating Database Settings Database Administration Authorization Checks 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 Priority Medium Medium Description There are security issues in your system. We found many ABAP dumps in your system. New Alert New New
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.
saphtmlp://htmlviewer.sap.com/uWweYNUAKV6D9G0cLNwC0G/index.html
05-Oct-12
Report
Page 2 of 39
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. Area System Performance Indicators Active Users Avg. Response Time in Dialog Task Max. Dialog Steps per Hour Avg. Response Time at Peak Dialog Hour Avg. Availability per Week Database Performance Avg. DB Request Time in Dialog Task Avg. DB Request Time in Update Task Database Space Management DB Size Last Month DB Growth Value 147 817 ms 26599 951 ms 99 % 479 ms 247 ms 627.98 GB 2.58 GB Trend up up up up steady up steady steady down
3 System Configuration
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. Rating Check Hardware Configuration Software Configuration Service Preparation
3.1 Hardware Configuration

The table below shows the detected hardware configuration: Hardware Configuration Server Type Application Server Server OS PECCCI HPUX HPUX OS Version 11.31 11.31 Number of CPUs N/A 4 Memory [MB] N/A N/A
Database Server PECCDB
05-Oct-12
Report
Page 3 of 39
Database System Database Server PECCDB Database System ORACLE Current Version 10.2.0
3.2 Software Configuration

3.2.1 Support Package Maintenance
Support Packages SAP SAP Component Component Version EA-APPL EA-DFPS 600 600 Patch Support Package Level 13 13 13 13 42 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SAPKGPAD13 SAPKGPDD13 SAPKGPFD13 SAPKGPGD13 SAPKGPHD42 Component Description SAP R/3 Enterprise PLM, SCM, Finance SAP R/3 Enterprise Defense Forces & Public Security SAP R/3 Enterprise Financial Services SAP R/3 Enterprise Global Trade SAP R/3 Enterprise Human Resources
EA-FINSERV 600 EA-GLTRADE 600 EA-HR EA-HRCAR EA-HRCAT EA-HRCAU EA-HRCBE EA-HRCBR EA-HRCCA EA-HRCCH EA-HRCCN EA-HRCDE EA-HRCDK EA-HRCES EA-HRCFI EA-HRCFR EA-HRCGB EA-HRCHK EA-HRCID EA-HRCIE EA-HRCIN EA-HRCIT EA-HRCJP EA-HRCKR EA-HRCMX EA-HRCMY EA-HRCNL EA-HRCNO 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 600
05-Oct-12
Report
Page 4 of 39
Support Packages SAP SAP Component Component Version EA-HRCNZ EA-HRCPH EA-HRCPT EA-HRCRU EA-HRCSE EA-HRCSG EA-HRCTH EA-HRCTW EA-HRCUS EA-HRCVE EA-HRCZA EA-HRGXX EA-HRRXX EA-IPPE 600 600 600 600 600 600 600 600 600 600 600 600 600 400 Patch Support Package Level 0 0 0 0 0 0 0 0 0 0 0 0 0 13 SAPKGPID13 SAP R/3 Enterprise Integrated Product and Process Engineering SAP R/3 Enterprise Public Services SAP R/3 Enterprise Retail Component Description
EA-PS EA-RETAIL ECC-DIMP ERECRUIT FI-CA FI-CAX FINBASIS INSURANCE IS-CWM IS-H IS-M IS-OIL IS-PS-CA IS-UT LSOFE PI_BASIS SAP_ABA
600 600 600 600 600 600 600 600 600 600 600 600 600 600 600 2005_1_700 700
13 13 13 13 13 13 13 13 13 14 13 13 13 13 13 18 18
SAPKGPPD13 SAPKGPRD13 SAPK60013INECCDIMP SAPK60013INERECRUIT SAPK-60013INFICA SAPK60013INFICAX SAPK60013INFINBASIS SAPK60013ININSURANC SAPK60013INISCWM SAPK-60014INISH SAPK-60013INISM SAPK60013INISOIL SAPK60013INISPSCA SAPK-60013INISUT SAPK60013INLSOFE SAPKIPYJ7I SAPKA70018
SAP E-Recruiting
SAP R/3 Enterprise FINBASIS
SAP R/3 Basis PlugIn SAP Application Basis
05-Oct-12
Report
Page 5 of 39
Support Packages SAP SAP Component Component Version SAP_AP SAP_APPL SAP_BASIS SAP_BW SAP_HR SAP_HRCAR SAP_HRCAT SAP_HRCAU SAP_HRCBE SAP_HRCBR SAP_HRCCA 700 600 700 700 600 600 600 600 600 600 600 Patch Support Package Level 15 13 18 20 63 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SAPKNA7015 SAPKH60013 SAPKB70018 SAPKW70020 SAPKE60063 SAP R/3 Standard SAP Basis Component SAP Business Information Warehouse SAP R/3 Standard HR Component Description
SAP_HRCCH 600 SAP_HRCCN 600 SAP_HRCDE SAP_HRCES SAP_HRCFI SAP_HRCFR 600 600 600 600 SAP_HRCDK 600
SAP_HRCGB 600 SAP_HRCHK 600 SAP_HRCID SAP_HRCIE SAP_HRCIN SAP_HRCIT SAP_HRCJP SAP_HRCKR 600 600 600 600 600 600
SAP_HRCMX 600 SAP_HRCMY 600 SAP_HRCNL 600 SAP_HRCNO 600 SAP_HRCNZ 600 SAP_HRCPH SAP_HRCPT SAP_HRCSE SAP_HRCTH 600 600 600 600
SAP_HRCRU 600 SAP_HRCSG 600 SAP_HRCTW 600 SAP_HRCUN 600 SAP_HRCUS 600
05-Oct-12
Report
Page 6 of 39
Support Packages SAP SAP Component Component Version SAP_HRCVE SAP_HRCZA SAP_HRRXX SEM-BW ST-A/PI ST-PI 600 600 600 600 01L_ECC600 2005_1_700 Patch Support Package Level 0 0 0 0 13 0 6 SAPKGS6013 SAPKITAR7D SAPKITLQI6 SAP SEM Server SAP Service Tools for Applications Plug-In SAP Solution Tools Plug-In Component Description
SAP_HRGXX 600
3.2.2 SAP Kernel Release

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 Note Version Component PY-IN PY-IN PY-IN PY-IN XX-CSC-IN-MM PY-IN FI-GL-FL Description PY-IN: Union Budget Changes for Year 2012 HINCALC0:Tax calculation inconsistent in case of invalid PAN Tax calculations inconsistent for emp. without a vaild PAN Budget Changes 2011 Run time error due to m/y overflow in Credit Transfer- J2I8 Amendments to IT calculation notified under circular:08/2010 Reversal not poss. due to missing values in required field
0001706872 0003 0001575366 0001 0001572614 0005 0001568264 0005 0001562761 0003 0001558475 0005 0001493450 0003
05-Oct-12
Report
Page 7 of 39
SAP Note
Version Component XX-CSC-IN PA-PM-CP XX-CSC-IN FI-SL-SL PA-PM-CP PA-PM-CP PA-PM-CP FI-AA-AA PA-PM-CP MM-IV-LIVCRE BC-CCM-BTCRUN XX-CSC-IN-SD XX-CSC-IN-MM PA-PM-CP
Description Duties not displayed under correct column in RG23C part2 No commitment references when transferring payroll result Duties not displayed under correct column in RG23A part2 FI general ledger: Performance of FI data selectn processes Financing not adjusted for periods that are not integrated System does not update change history for PBC documents Retroactive accounting date not set in spite of switch RECAL Fixed asset is incorrectly flagged as incomplete Documents not created in the sequence of their due date MIRO: Balance is not updated Message D01 in system log with reference to message BT 510 ADC appear as AED(GSI) for monthly utilized document in J2I9 Changes in heading and display of duty column for RG1 report Error corrections for document closing
0001455469 0003 0001406960 0012 0001405087 0002 0001382528 0004 0001350822 0007 0001336899 0002 0001332905 0002 0001329216 0003 0001327534 0002 0001307798 0001 0001299997 0003 0001295661 0003 0001283823 0005 0001272102 0003
3.3 Service Preparation

System PPR is not fully prepared for service delivery. Rating Performed Check Service Data Control Center Service Preparation Check (RTCCTOOL) ST-PI and ST-A/PI Plug-Ins Missing Function Modules Errors in Data Collection SAP OS Collector Workload Monitor (ST03) 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. Check not Performed SAP OS Collector Version
Hint SAP OS collector version could not be determined.
Recommendation Review SAP Note 1075827.
05-Oct-12
Report
Page 8 of 39
3.3.1 Service Preparation Check (RTCCTOOL)

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: Host PECCCI PECCDB PECCCI PECCDB PECCCI PECCDB PECCCI PECCDB Function Name GET_FSYS_SINGLE GET_FSYS_SINGLE GET_MEM_ALL GET_MEM_ALL GET_CPU_ALL GET_CPU_ALL FILL_SNAPSHOT_DATA FILL_SNAPSHOT_DATA Exception SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV SHARED_MEMORY_NOT_AV
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

Host Name PECCCI PECCDB Days not Collected 24.09.2012-30.09.2012 24.09.2012-30.09.2012
Recommendation: Check whether SAPOSCOL is running and storing data correctly on the above servers. Also check the SAPOSCOL version.
05-Oct-12
Report
Page 9 of 39
3.3.4 Info: Active SAP Application Servers

The following information can be found in transaction SM51: SAP Application Server PECCCI_PPR_02 PECCDB_PPR_01 SM51 Host Name PECCCI PECCDB
4 Performance Overview PPR

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: Avg. Resp. Time in ms 816,8 653,8 301,0 66,7 380,7 1187,2 Avg. Avg. Avg. Avg. Avg. CPU Wait Load DB GUI Time in Time in Time in Time in Time in ms ms ms ms ms 168,6 37,6 46,1 18,0 206,9 34,6 5,1 43,5 4,3 0,7 6,0 2,0 2,0 2,5 4,1 1,0 2,4 0,3 479,4 357,8 247,3 43,4 111,6 9,7 134,6 0,0 0,0 0,0 0,0 0,0
Task type DIALOG RFC UPDATE UPDATE2 BATCH SPOOL
Dialog Steps 1108524 1139720 67209 52315 2003890 29525
4.1 Current Workload

The following table lists the number of current users (measured from our workload analysis) in your system. Low Activity 12 Medium Activity 52 High Activity 95 Total Users 159
Users Measured in 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.
05-Oct-12
Report
Page 10 of 39
The table below shows that no problem is expected on the application or database servers. Application Server Performance Database Server Performance
Task Steps Dia Upd HTTP 1107728 67209 0
Rating Task Time Steps Dia 0708
Avg. Response Time (ms)
Avg. CPU Time (ms) 191
Avg. Database Time (ms) 1355
1213 1678
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 Avg. Response Time (ms) 1200 2400 1200 Reference for Avg. DB time (ms) 600 1200 600
Task Dia Upd HTTP
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. Workload by Transaction (Dialog/Update) Dialog Steps Total Resp. Time in % Avg. Resp. Time in ms 787,4 70736,6 876,0 4859,4 1080,3 3102,0 923,8 1916,8 Avg. CPU Time in ms 161,6 20522,1 126,4 1956,7 194,3 37,5 85,2 122,0 Avg. Avg. DB GUI Time in Time ms in ms 466,1 134,6 48182,8 732,7 309,6 259,8 2288,3 512,4 688,3 192,4 3042,9 767,4 1660,1 7,0 77,8 51,4
Transaction
Type
Total ZMM_DOCFLOW ZRECON ZSO_PND MIRO F-58 CO02 FAGLL03 DIA DIA DIA DIA DIA DIA DIA SESSION_MANAGER DIA
1175633 100,0 993 76802 139 9035 36128 8462 25733 12373 7,6 7,3 4,7 4,2 2,8 2,6 2,6
5,1 341117,4 113934,0 186879,8 313,9
05-Oct-12
Report
Page 11 of 39
Workload by Transaction (Dialog/Update) Dialog Steps 9190 1451 Total Resp. Time in % 2,5 2,4 Avg. Resp. Time in ms 2530,8 15083,8 Avg. CPU Time in ms 688,7 50,9 Avg. Avg. DB GUI Time in Time ms in ms 1340,2 516,4 15007,7 15,3
Transaction
Type
ZSR FBZ5
DIA DIA
19.9% of the "Total Resp. Time" in the above table is caused by customer transactions. Workload by Transaction (Batch/Spool) Transaction Total ZSD_PENDING_ORDER RKO7CO88 RSBTCRTE RSDBAJOB ZDOCFLOW_MM (BATCH) SAPF124 RSARFCSE PPIO_ENTRY BTC BTC BTC BTC BTC BTC BTC BTC BTC Dialog Type Steps Total Avg. Resp. Avg. CPU Resp. Time in Time in Time ms ms in % 385,6 564759,5 123,3 2249139,5 1219454,5 37,3 855588,6 33,3 618153,3 201,8 469301,8 85,2 78,9 25,4 10,4 8,0 4,5 3,2 3,1 2,7 2,2 Avg. DB Time in ms 107,8 94054,2 7,7 118,0
2033081 100,0 352 4 658917 28 2 29 678829 28 648074 28
14,1 27605370,3 19731215,0 6805230,0
ZMM_MATERIAL_AGEING_NEW3_2130 BTC
7,8 30711751,0 24221470,0 6458233,5 109425,9 1115051,5 10,3 708393,9 12,0 119487,9 12,9 233553,5 7,8 517053,6
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. Database Load by Transactions (Dialog/Update) Transaction Total ZMM_DOCFLOW ZRECON F-58 MIRO FBZ5 ZSO_PND FAGLL03 CO02 MB25 DIA DIA DIA DIA DIA DIA DIA DIA DIA Type Dialog Steps 1175633 993 139 8462 36128 76802 1451 9035 12373 25733 438 Total DB Time in % 100,0 8,7 4,7 4,7 4,5 4,3 4,0 3,8 3,7 3,6 3,5 Avg. DB Time in ms 466,1 48182,8 186879,8 3042,9 688,3 309,6 15007,7 2288,3 1660,1 767,4 43976,3
SESSION_MANAGER DIA
05-Oct-12
Report
Page 12 of 39
17.2% of the "Total DB Time" in the above table is caused by customer transactions. Database Load by Transactions (Batch/Spool) Transaction Total ZSD_PENDING_ORDER ZDOCFLOW_MM RKO7CO88 PPIO_ENTRY RSBTCDEL ZDOCFLOW_MM_FIX_LAY SAPKKA07 (BATCH) ZDOCFLOW_MM_FIX_LAY1 BTC BTC BTC BTC BTC BTC BTC BTC BTC Dialog Type Steps 2033081 352 29 4 28 2 21 7 1 678829 7 Total DB Avg. DB Time in Time in ms % 100,0 15,1 14,7 12,4 6,6 5,9 4,9 4,6 4,1 4,0 3,2 107,8 94054,2 1115051,5 6805230,0 517053,6 6458233,5 511424,8 1436537,0 8883681,0 12,9 998660,9
ZMM_MATERIAL_AGEING_NEW3_2130 BTC
43.5% of the "Total DB Time" in the above table is caused by customer transactions.
5 Workload Distribution PPR

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. Rating Check Workload by Application Module DB Load Profile
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 addon development).
05-Oct-12
Report
Page 13 of 39
Module Unknown CO-OM BC-CCM BC MM FI PP PY
CPU Time in % 48,1 12,3 10,0 9,8 5,7 4,8 3,6 1,7
Module
DB Time in %
05-Oct-12
Report
Page 14 of 39
Module BC Unknown MM FI PP CO-OM BC-CCM LE QM LO CO
DB Time in % 33,5 23,4 12,5 9,5 8,5 2,6 2,4 2,1 2,0 1,2 1,1
5.2 DB Load Profile

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.
05-Oct-12
Report
Page 15 of 39
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 nonSAP 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. Average call Bytes Bytes sent time, received ms 169 847288609 1350121055 58639453 225525 952376 102072 33572 166912 301779 151125 4247 70302466 199328 69242144 23387 665859 8006 1070388422 62462 32304 4089 303669 8703
Outgoing function call ARFC_RUN_NOWAIT QDEST_RUN_DESTINATION SAPXPG_END_XPG SALT_TOOLSET_STARTER GOS_EXECUTE_SERVICE RSAP_TRFC_SEND ARFC_DEST_SHIP SXPG_COMMAND_EXECUTE RSAP_IDOC_SEND
Calls
Total call time, s
574450 97306,40 10754 86092,23 148 203 77 661 7 195 9244,36 6557,74 6006,27 2702,64 2125,68 1697,01
31 62919,09 2029648
78004 6935386895
Incoming function call QDEST_RUN ARFC_RUN_NOWAIT ZTEST QDEST_RUN_DESTINATION SALT_TOOLSET_STARTER SWNC_COLLECTOR_STARTER GOS_EXECUTE_SERVICE RSAP_TRFC_SEND PRGN_SHOW_EDIT_AGR
Calls
Average Bytes Total call call Bytes sent time, received time, s ms 78012 30829 2236 61192 11088 33451 72365 37705 0 0 1041916 0 102072 0 1437250 949703796 1403077 71731775 196392 180236 54920 173 2533991139
4457 347697,74 669497 116145,48 2917 19160 151 668 196 83 92 89927,68 42848,56 9240,00 7406,50 6556,49 6006,26 3468,89
67396678 1326638128
86403 7149347957
6 SAP System Operating PPR

Your system was analyzed with respect to daily operation. We detected some problems that may impair system operation and stability. To ensure system stability, you should take corrective action as soon as possible. Rating Check Table Reorganization
05-Oct-12
Report
Page 16 of 39
6.1 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. 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 Table / Index Name ARFCSSTATE BALDAT Size of Table / Index [MByte] Recommended SAP Note
1664,0 375566 7936,0 195157
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
05-Oct-12
Report
Page 17 of 39
system, call transaction ST22 and choose Selection. Then select a timeframe. Date 24.09.2012 25.09.2012 26.09.2012 27.09.2012 28.09.2012 29.09.2012 30.09.2012 Total of Server (e.g.) Error (s) Quantity of Dumps 94 61 120 7 45 2 34
Name of runtime Error(s) MESSAGE_TYPE_UNKNOWN TSV_TNEW_BLOCKS_NO_ROLL_MEMORY DYNPRO_MSG_IN_HELP CALL_FUNCTION_SYSCALL_ONLY SYSTEM_CORE_DUMPED PERFORM_NOT_FOUND TABLE_INVALID_INDEX CALL_FUNCTION_SINGLE_LOGIN_REJ SYSTEM_ON_COMMIT_INTERRUPTED LIST_TOO_MANY_LPROS OBJECTS_OBJREF_NOT_ASSIGNED SAPSQL_ARRAY_INSERT_DUPREC DBIF_RSQL_SQL_ERROR DYNPRO_FIELD_CONVERSION RAISE_EXCEPTION TIME_OUT MESSAGE_TYPE_X TSV_TNEW_PAGE_ALLOC_FAILED
User (e.g.)
Date (e.g.)
Time (e.g.)
3 PECCDB_PPR_01 RPG5003316 24.09.2012 12:34:16 2 PECCDB_PPR_01 ES5015065 2 PECCDB_PPR_01 GS5002059 9 PECCDB_PPR_01 SAPSYS 1 PECCDB_PPR_01 GS5002059 25.09.2012 10:31:14 25.09.2012 11:01:16 25.09.2012 12:08:23 25.09.2012 12:11:10
1 PECCDB_PPR_01 SMM5040693 25.09.2012 14:38:49 1 PECCDB_PPR_01 ASW5040688 26.09.2012 11:32:52 18 PECCDB_PPR_01 PETLBASIS 2 PECCDB_PPR_01 JKP5040684 1 PECCDB_PPR_01 BS5022143 2 PECCCI_PPR_02 NK5002104 27.09.2012 15:20:44 28.09.2012 12:31:48 29.09.2012 13:29:15 30.09.2012 09:37:25 1 PECCDB_PPR_01 KKO5030139 28.09.2012 12:31:09
1 PECCDB_PPR_01 SAD5040660 30.09.2012 09:27:05 279 PECCCI_PPR_02 UPL5022144 30.09.2012 12:21:32 6 PECCCI_PPR_02 MMA5030067 30.09.2012 13:58:46 23 PECCDB_PPR_01 SP5024025 9 PECCDB_PPR_01 SP5030228 30.09.2012 16:56:43 30.09.2012 22:26:56 2 PECCDB_PPR_01 SSK5040571 30.09.2012 17:54:35
7 Authorization Checks
Critical security issues were detected in your system. See the information in the following checks. Rating Check Users Authorized to Display all Tables Users Authorized to Start all Reports Users Authorized to Debug / Replace Users Authorized to Display Other Users Spool Request Users Authorized to Administer RFC Connections Users Authorized to Reset/Change User Passwords
05-Oct-12
Report
Page 18 of 39
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. Client 001 300 310 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 = * User Count 2 29 10 Valid Users 3 173 11 Rating
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. Client 001 300 310 Evaluated Risk - High User Count 2 44 10 Valid Users 3 173 11 Rating
05-Oct-12
Report
Page 19 of 39
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. Client 001 300 310 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). User Count 2 50 10 Valid Users 3 173 11 Rating
8 Hardware Capacity
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. Max. CPU Date load [%] 50 06.09.2012 RAM [MB] 0 Max. Paging [% of RAM] 0
Server PECCCI
Rating
Date Rating
9 Database Settings
05-Oct-12
Report
Page 20 of 39
We have detected some problems with the settings of the database. These settings may affect performance. Rating Check Missing Indexes Database Key Performance Indicators Setup of the Temporary Tablespace Database Parameters Optimizer Statistics Automatic stats creation
9.1 Load per user

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.
Load per user (percentages) User name Executions Disk reads Buffer gets Rows processed
total (not a user name!) SAPSR3 OPS$PPRADM SYS ORACLE_OCM
128525900 2146638046 5949837482 1403846087
99% 0% 1% 0%
100% 0% 0% 0%
99% 1% 0% 0%
100% 0% 0% 0%
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

Note for Oracle parameter settings Note number Description
05-Oct-12
Report
Page 21 of 39
Note for Oracle parameter settings Note number 1238487 830576 Description Update of threshold values of database system check Parameter recommendations for Oracle 10g Current value Recommended value
Parameters
Description
_fix_control
Bug fix control parameter Maximum size of the optimizer trace file
5705630:ON, 5765456:3, Please check 6221403:ON, SAP note 6329318:ON, 830576 6399597:ON, 6 UNLIMITED Please check SAP note 830576 Please check SAP note 830576 Please check SAP note 830576 Please check SAP note 830576
max_dump_file_size
optimizer_index_caching
Adjust the usage of 0 nested loops Percentage of the calculated index costs 100
optimizer_index_cost_adj
Parallel Query: Size parallel_execution_message_size of messages 2152 for parallel execution Parallel Query: Maximum number of parallel execution servers
parallel_max_servers
65
Please check SAP note 830576
See SAP Notes 830576 and 651060 to confirm the correct configuration of PARALLEL_MAX_SERVERS. If it is configured correctly, then ignore the yellow rating for this parameter. Current Recommended value value 2 Please check SAP note 830576 Please check SAP note 830576 Please check SAP note 830576
Parameters
Description Number of parallel execution processes/threads per CPU
parallel_threads_per_cpu
processes
Maximum number of database 80 shadow/background processes
Produce information replication_dependency_tracking for the Replication TRUE Server
If you use replication in your system do not change the setting of parameter
05-Oct-12
Report
Page 22 of 39
'replication_dependency_tracking', otherwise you can switch it off. Current value Recommended value Please check SAP note 830576 Please check SAP note 830576
Parameters sessions
Description
Maximum number of concurrent 96 database sessions 278132686
Part of Shared shared_pool_reserved_size Pool for large statements
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: Parameter event Current Value 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 The following table lists events that may have to be activated. Please check the mentioned SAP Notes for details. Note number for Event
Event
Description Increased memory consumption with Oracle >8.0.X Incorrect values in Oracle 10.2 (II)
10191 128221 10162 977319
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. Event
05-Oct-12
Report
Page 23 of 39
Event 10142 10411 38085 44951
10 Database Administration
In the checks performed, problems regarding the administration of your database were found. Rating Check Database Growth Backup Frequency Archive Frequency Freespace in Tablespaces Space Critical Objects brconnect -f check (sapdba -check) schedule Multibyte Character Sets
10.1 Database Growth

The following figure shows the development of the size of your database in GB.
An overview of the freespace development of your database in GB is shown here.
05-Oct-12
Report
Page 24 of 39
The following table shows you the current size and the monthly growth of your database in GB. Date 31.10.2011 30.11.2011 30.12.2011 31.01.2012 29.02.2012 31.03.2012 30.04.2012 31.05.2012 30.06.2012 31.07.2012 31.08.2012 30.09.2012 Current Size in GB 555,46 561,01 564,76 569,89 575,72 580,51 588,99 602,56 610,18 615,92 625,40 627,98 Monthly Growth in GB 5,44 5,55 3,75 5,13 5,83 4,79 8,48 13,57 7,62 5,74 9,48 2,58
10.2 Freespace in Tablespaces

We checked your system for tablespaces that may overflow in the near future.
10.2.1 Tablespaces - Autoextend Limit

Free Tablespace Size (KB) (KB) PSAPSR3 Avg. %Chg/Week AutoExt Used (KB) 91 %Used after AutoExt
630824960 52308608 1454695
1,547,444,224 37
You have set the 'autoextend' option for some tablespaces to a limited value. More than 80% of the limited size is already used.
05-Oct-12
Report
Page 25 of 39
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): Patch set 10.2.0 SAP Note number 871096
Description Oracle Database 10g - Patchsets/Patches for 10.2.0
11 Database server load from expensive SQL statements - PPR

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. Database Load From Expensive Statements Rating Buffer Load [%] 30 Disk Load [%] 26 CPU Load [%] 31
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.
05-Oct-12
Report
Page 26 of 39
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 "/").
11.1 Analysis of DB SQL CACHE on

Expensive SQL Statements Overview Object Name CPU Load [%] I/O Load [%] 1 0 25 0 0 0 0 Elapsed Records Executions Time [%] Processed 8 6 4 4 4 3 2 57 71798 16934 226 32908 107360 397762 13187401 17340181 126625838 1720 126626272 12857322 23234601
WB2_V_MKPF_MSEG2 0 WB2_V_MKPF_MSEG2 1 TRFCQOUT BSAS TRFCQOUT ATP_RESB JEST 17 0 11 1 0
11.1.1 Access on WB2_V_MKPF_MSEG2

Statement Data: Cache Statistics Object Type VIEW SELECT "MBLNR" , "XABLN" , "LGORT_I" "EBELN_I" "XAUTO_I" FROM "WB2_V_MKPF_MSEG2" WHERE "MANDT" = :A0 AND "WERKS_I" = :A1 AND "BWART_I" IN ( :A2 , :A3 , :A4 , :A5 , :A6 , :A7 , :A8 , :A9 , :A10 , :A11 ) AND "SOBKZ_I" IN ( :A12 , :A13 )& Execution Plan (From: V$SQL_PLAN addr= C000000249BAE898 hash= 793605046 sql_id 7nuw4xwrnuw SELECT STATEMENT Estimated Costs= 201,456 Estimated Rows= 0 Optimizer: ALL_ROWS 5 HASH JOIN Estimated Costs= 201,456 Estimated Rows= 90,406 Access predicates: "MJAHR" , "BUDAT" , "CPUTM" , "USNAM" , "TCODE2" , "VGART" , "BKTXT" , "ZEILE_I" , "BWART_I" , "SOBKZ_I" , "MATNR_I" , "WERKS_I" , , "LIFNR_I" , "MENGE_I" , "MEINS_I" , "DMBTR_I" , "WAERS_I" , , "EBELP_I" , "LFBNR_I" , "LFBJA_I" , "SMBLN_I" , "SJAHR_I" , Total Executions Disk Reads 57 11027173 40977042 Buffer Gets 17244209 Records Processed 13187401
05-Oct-12
Report
Page 27 of 39
"T0002"."MANDT"="T0001"."MANDT" AND "T0002"."MBLNR"="T0001"."MBLNR" AND "T0 002"."MJAHR"="T0001"."MJAHR" Estim. Bytes: 14,916,990 Estim. CPU-Costs = 4,615,012,309 Estim. IO-Costs = 200,691 Estim. Temp. Space: 10,314,000 Last WorkArea Mem kB: 85,890,048 3 INLIST ITERATOR 2 TABLE ACCESS BY INDEX ROWID MSEG Estimated Costs= 187,224 Estimated Rows= 90,406 Filter predicates: (INTERNAL_FUNCTION("T0002"."SOBKZ") AND "T0002"."MANDT"=:A0) Estim. Bytes: 9,221,412 Estim. CPU-Costs = 2,035,271,777 Estim. IO-Costs = 186,887 1 INDEX RANGE SCAN MSEG~ZSU Estimated Costs= 11,596 Estimated Rows= 180,812 Filter predicates: "T0002"."WERKS"=:A1 Access predicates: (("T0002"."BWART"=:A2 OR "T0002"."BWART"=:A3 OR "T0002"."BWART"=:A4 OR "T00 02"."BWART"=:A5 OR "T0002"."BWART"=:A6 OR "T0002"."BWART"=:A7 OR "T0002"."B WART"=:A8 OR "T0002"."BWART"=:A9 OR "T0002"."BWART"=:A10 OR "T0002"."BWART" =:A11)) AND "T0002"."WERKS"=:A1 Search Columns: 2 Estim. CPU-Costs = 584,004,677 Estim. IO-Costs = 11,499 4 TABLE ACCESS FULL MKPF Estimated Costs= 11,282 Estimated Rows= 2,383,400 Filter predicates: "T0001"."MANDT"=:A0 Estim. Bytes: 150,154,200 Estim. CPU-Costs = 1,991,797,632 Estim. IO-Costs = 10,952 Program Data: Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On ZDOCFLOW_MM 003280 003281 003282 003283 003284 003285 003286 003287 3280 KABIR PETLABAP 11.08.2010
SELECT mblnr mjahr budat cputm usnam tcode2 vgart xabln bktxt zeile_i bwart_i sobkz_i matnr_i werks_i lgort_i lifnr_i menge_i meins_i dmbtr_i waers_i ebeln_i ebelp_i lfbnr_i lfbja_i smbln_i sjahr_i xauto_i INTO CORRESPONDING FIELDS OF TABLE wt_inittab FROM wb2_v_mkpf_mseg2
05-Oct-12
Report
Page 28 of 39
003288 003289 003290 003291 003292
WHERE matnr_i IN s_matnr AND werks_i = s_werks-low AND lgort_i IN s_lgort AND bwart_i IN r_total AND sobkz_i IN r_sobkz.
11.1.2 Access on WB2_V_MKPF_MSEG2

Statement Data: Cache Statistics Object Type VIEW SELECT "MBLNR" , "ZEILE_I" , "MJAHR" , "BUDAT" , "BWART_I" , "MATNR_I" , "WERKS_I" , "MENGE_I" , "SOBKZ_I" , "SHKZG_I" , "EBELN_I" , "EBELP_I" , "KZBEW_I" , "UMSOK_I" , "KZVBR_I" FROM "WB2_V_MKPF_MSEG2" WHERE "MANDT" "MANDT" "MANDT" "MANDT" "MANDT" = :A0 AND "MATNR_I" = :A1 AND "WERKS_I" = :A2 AND "BUDAT" <= :A3 OR = :A4 AND "MATNR_I" = :A5 AND "WERKS_I" = :A6 AND "BUDAT" <= :A7 OR = :A8 AND "MATNR_I" = :A9 AND "WERKS_I" = :A10 AND "BUDAT" <= :A11 OR =:A12 AND "MATNR_I" = :A13 AND "WERKS_I" = :A14 AND "BUDAT" <= :A15 OR = :A16 AND "MATNR_I" = :A17 AND "WERKS_I"= :A18 AND "BUDAT" <= :A19& Total Executions 71798 Disk Reads 6602175 34099091 Buffer Gets 72260730 Records Processed 17340181
Program Data: Origin of ABAP coding Program Name Line Created By Last Last Changed By Changed On 05.09.2012
ZMM_MATERIAL_AGEING_NEW3 725 PETLABAP PETLABAP 000724 000725 000726 000727 000728 000729 000730 000731 000732
* SELECT MBLNR ZEILE_I MJAHR BUDAT BWART_I MATNR_I WERKS_I MENGE_I SOBKZ_I SHKZG_I ebeln_i ebelp_i kzbew_i UMSOK_I KZVBR_I FROM WB2_V_MKPF_MSEG2 INTO TABLE IT_MSEG1 FOR ALL ENTRIES IN IT_FINAL WHERE MATNR_I = IT_FINAL-MATNR AND WERKS_I = IT_FINAL-WERKS AND BUDAT LE S_BUDAT.
11.1.3 Access on TRFCQOUT

Statement Data:
05-Oct-12
Report
Page 29 of 39
Cache Statistics Object Type TABLE SELECT * FROM "TRFCQOUT" WHERE "MANDT" = :A0 AND "QSTATE" IN ( :A1 , :A2 , :A3 , :A4 , :A5 ) AND "DEST" = :A6& Execution Plan (From: V$SQL_PLAN addr= C000000249BAE898 hash= 793605046 sql_id 7nuw4xwrnuw SELECT STATEMENT Estimated Costs= 8,428 Estimated Rows= 0 Optimizer: ALL_ROWS 1 TABLE ACCESS FULL TRFCQOUT Estimated Costs= 8,428 Estimated Rows= 699,256 Filter predicates: ("DEST"=:A6 AND "MANDT"=:A0 AND INTERNAL_FUNCTION("QSTATE")) Estim. Bytes: 114,677,984 Estim. CPU-Costs = 1,461,277,974 Estim. IO-Costs = 8,186 Program Data: Origin of ABAP coding Program Name Line Created By Last Changed By LQOWKU06 000160 000161 000162 000163 000164 160 SAP SAP Last Changed On 24.12.2008 Total Executions Disk Reads Buffer Gets Records Processed 126625838
16934 531757806 20893142 1020936423
select * from trfcqout into table err_queue for all entries in err_qstate where qstate = err_qstate-qstate and dest = qdestlist-dest.
11.1.4 Access on BSAS

Statement Data: Cache Statistics Object Type TABLE SELECT Total Executions 226 Disk Reads 7418436 20179206 Buffer Gets 16040122 Records Processed 1720
05-Oct-12
Report
Page 30 of 39
"MANDT" , "BUKRS" , "HKONT" , "AUGDT" , "AUGBL" , "ZUONR" , "GJAHR" , "BELNR" , "BUZEI" , "BUDAT" , "BLDAT" , "WAERS" ,"XBLNR" , "BLART" , "MONAT" , "BSCHL" , "SHKZG" , "GSBER" , "MWSKZ" , "FKONT" , "DMBTR" , "WRBTR" , "MWSTS" , "WMWST" ,"SGTXT" , "PROJN" , "AUFNR" , "WERKS" , "KOSTL" , "ZFBDT" , "XOPVW" , "VALUT" , "BSTAT" , "BDIFF" , "BDIF2" , "VBUND" ,"PSWSL" , "WVERW" , "DMBE2" , "DMBE3" , "MWST2" , "MWST3" , "BDIF3" , "RDIF3" , "XRAGL" , "PROJK" , "PRCTR" , "XSTOV" ,"XARCH" , "PSWBT" , "XNEGP" , "RFZEI" , "CCBTC" , "XREF3" , "BUPLA" , "PPDIFF" , "PPDIF2" , "PPDIF3" , "BEWAR" , "IMKEY" , "DABRZ" , "INTRENO" , "GRANT_NBR" , "FKBER" , "FIPOS" , "FISTL" , "GEBER" , "PPRCT" , "BUZID" , "AUGGJ" , "UZAWE" , "SEGMENT" , "PSEGMENT" , "FIPEX" , "PRODPER" , "QSSKZ" , "PROPMANO" FROM "BSAS" WHERE "MANDT" = :A0 AND "BUKRS" = :A1 AND "AUGBL" = :A2& Execution Plan (From: V$SQL_PLAN addr= C000000249BAE898 hash= 793605046 sql_id 7nuw4xwrnuw SELECT STATEMENT Estimated Costs= 22,978 Estimated Rows= 0 Optimizer: ALL_ROWS 2 TABLE ACCESS BY INDEX ROWID BSAS Estimated Costs= 22,978 Estimated Rows= 5 Estim. Bytes: 1,535 Estim. CPU-Costs = 448,100,612 Estim. IO-Costs = 22,904 1 INDEX RANGE SCAN BSAS~0 Estimated Costs= 22,977 Estimated Rows= 5 Filter predicates: "AUGBL"=:A2 Access predicates: "MANDT"=:A0 AND "BUKRS"=:A1 AND "AUGBL"=:A2 Search Columns: 3 Estim. CPU-Costs = 448,085,140 Estim. IO-Costs = 22,903 Program Data: Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On ZRFFORI01 002776 002777 002778 002779 002780 002781 2777 SUBHASISH ABAP 13.08.2009
SELECT * INTO CORRESPONDING FIELDS OF TABLE itab_bsas FROM bsas " Accounting Document Segment WHERE bukrs = l_zbukr * AND belnr <> l_belnr.
11.1.5 Access on TRFCQOUT

Statement Data:
05-Oct-12
Report
Page 31 of 39
Cache Statistics Object Type TABLE SELECT DISTINCT "MANDT" , "QNAME" , "DEST" FROM "TRFCQOUT" WHERE "MANDT" = :A0 AND "DEST" = :A1 AND "NOSEND" = :A2& Execution Plan (From: V$SQL_PLAN addr= C000000249BAE898 hash= 793605046 sql_id 7nuw4xwrnuw SELECT STATEMENT Estimated Costs= 2,776 Estimated Rows= 0 Optimizer: ALL_ROWS 2 HASH UNIQUE Estimated Costs= 2,776 Estimated Rows= 424 Estim. Bytes: 8,480 Estim. CPU-Costs = 836,534,281 Estim. IO-Costs = 2,637 1 INDEX FAST FULL SCAN TRFCQOUT~3 Estimated Costs= 2,727 Estimated Rows= 349,628 Filter predicates: ("DEST"=:A1 AND "NOSEND"=:A2 AND "MANDT"=:A0) Estim. Bytes: 6,992,560 Estim. CPU-Costs = 540,412,876 Estim. IO-Costs = 2,637 Program Data: Origin of ABAP coding Program Name Line Created By Last Changed By LQOWKU06 000143 000144 000145 000146 000147 000148 000149 000150 145 SAP SAP Last Changed On 24.12.2008 Total Executions 32908 Disk Reads Buffer Gets Records Processed 126626272
86843 19510240 664517041
* Ermittlung der qRFC-Queues select distinct mandt qname dest from trfcqout into table qview where qname like qid_dbwcard and dest = qdestlist-dest and nosend = space.
11.1.6 Access on ATP_RESB

Statement Data:
05-Oct-12
Report
Page 32 of 39
Cache Statistics Object Type VIEW SELECT * FROM "ATP_RESB" WHERE "MANDT" = = :A4 AND "BDMNG" > ( "VORAB" :A0 AND "BDTER" "ENMNG" IS NULL "MATNR" = :A1 AND < :A5 AND "BDART" AND "TXTPS" = :A9 OR "VORAB" = :A12 "WERKS" = :A2 AND "XLOEK" = :A3 AND "KZEAR" <> :A6 AND "SOBKZ" IN ( :A7 , :A8 ) AND AND "SCHGT" = :A10 AND "DBSKZ" = :A11 AND )& Total Executions 107360 Disk Reads 2860652 15833036 Buffer Gets 38297948 Records Processed 12857322
Execution Plan (From: V$SQL_PLAN addr= C000000249BAE898 hash= 793605046 sql_id 7nuw4xwrnuw SELECT STATEMENT Estimated Costs= 5 Estimated Rows= 0 Optimizer: ALL_ROWS 2 TABLE ACCESS BY INDEX ROWID RESB Estimated Costs= 5 Estimated Rows= 1 Filter predicates: ("T0001"."TXTPS"=:A9 AND "T0001"."BDART"<>:A6 AND "T0001"."BDMNG">"T0001"." ENMNG" AND INTERNAL_FUNCTION("T0001"."SOBKZ") AND "T0001"."SCHGT"=:A10 AND "T0001"."DBSKZ"=:A11 AND ("T0001"."VORAB"=:A12 OR "T0001"."VORAB" IS NULL)) Estim. Bytes: 150 Estim. CPU-Costs = 39,462 Estim. IO-Costs = 5 1 INDEX RANGE SCAN RESB~M Estimated Costs= 4 Estimated Rows= 1 Access predicates: "T0001"."MANDT"=:A0 AND "T0001"."MATNR"=:A1 AND "T0001"."WERKS"=:A2 AND "T0 001"."XLOEK"=:A3 AND "T0001"."KZEAR"=:A4 AND "T0001"."BDTER"<:A5 Search Columns: 6 Estim. CPU-Costs = 28,686 Estim. IO-Costs = 4 Program Data: Origin of ABAP coding Program Name Line Created By Last Changed By LATP2FR1 30 SAP SAP Last Changed On 13.03.2006
000030 SELECT * 000031 FROM atp_resb 000032 INTO atp_resb
05-Oct-12
Report
Page 33 of 39
000033 000034 000035 000036 000037 000038 000039 000040 000041 000042 000043 000044 000045
WHERE matnr = atpmat-matnr AND werks = atpmat-werks AND xloek = space AND kzear = space AND bdter < atpmat-endwz AND bdart <> skbed AND sobkz IN (space, sobkzk) AND bdmng > atp_resb~enmng AND txtps = space AND schgt = space AND dbskz = space AND ( vorab IS NULL OR vorab = space ).
11.1.7 Access on JEST

Statement Data: Cache Statistics Object Type TABLE SELECT * FROM "JEST" WHERE "MANDT" = :A0 AND "OBJNR" IN ( :A1 , :A2 , :A3 , :A4 , :A5 )& Execution Plan (From: V$SQL_PLAN addr= C000000249BAE898 hash= 793605046 sql_id 7nuw4xwrnuw SELECT STATEMENT Estimated Costs= 31 Estimated Rows= 0 Optimizer: ALL_ROWS 3 INLIST ITERATOR 2 TABLE ACCESS BY INDEX ROWID JEST Estimated Costs= 31 Estimated Rows= 44 Estim. Bytes: 1,408 Estim. CPU-Costs = 326,432 Estim. IO-Costs = 31 1 INDEX RANGE SCAN JEST~0 Estimated Costs= 8 Estimated Rows= 44 Access predicates: "MANDT"=:A0 AND (("OBJNR"=:A1 OR "OBJNR"=:A2 OR "OBJNR"=:A3 OR "OBJNR"=:A4 OR "OBJNR"=:A5)) Search Columns: 2 Estim. CPU-Costs = 151,829 Estim. IO-Costs = 8 Total Executions 397762 Disk Reads 2265410 8246947 Buffer Gets 21640375 Records Processed 23234601
05-Oct-12
Report
Page 34 of 39
Program Data: Origin of ABAP coding Program Name Line Created By Last Changed By LBSVAU14 000110 000111 000112 000113 000114 110 SAP SAP Last Changed On 09.12.2004
SELECT * FROM JEST CLIENT SPECIFIED APPENDING TABLE JEST_BUF FOR ALL ENTRIES IN OBJNR_TAB WHERE MANDT EQ CLIENT 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). Tables with Fragmentation Table Name SNAP ACCTIT MSEG BSIS RFBLG COEP ACCTCR AUFM CKMI1 VBDATA BSIM QAMV APQD RESB PPOIX NAST LIPS Rows 40093 Average Row Length 1558 Blocks Kb Used Kb Needed Kb Wasted 21839695 20830786 18315853 14859568 12198230 8012727 5912554 3864461 3567022 2381624 2334000 1508942 766594 708281 510253 428718 358179 232260
3123752 21900735 61040 4127316 28936758 8105972 3826040 26824501 8508647 3172858 22245019 7385451 2364689 16578918 4380688 1740659 12203821 4191094 1292586 9062366 760627 637867 425084 335060 269588 171380 118217 683774 163196 179564 85577 5332783 4472108 2980279 2349117 1890091 1201551 828824 4793964 1144173 1258930 599983 3149812 1468322 905086 598655 15117 381149 434957 120543 4283711 715455 900750 367723
14769600 561 11138000 678 14756000 303 3430600 9744433 4499067 5066300 31983 4940467 910830 1250 1841 330 205 120 483 78 488 415 595 130 274 960
FAGLFLEXA 38723800 224
ARFCSDATA 6578400
2654197 18608668 11833411 6775258
29481600 50
ALALERTDB 296720 7359933 5592567 3354067 391830
17558900 734
1873649 13136219 12603312 532907
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).
05-Oct-12
Report
Page 35 of 39
Indexes with low Storage Quality Index Name TEMSGU~DAT AGR_USERS~U UST04~0 PLAF~0 KBKO~0 VEPVG~A BSID~2 VBBE~0 EBAN~0 BSID~5 KBED~1 RSEUINC~1 VEPVG~0 ARFCSSTATE~05 KBED~0 VBMOD~0 VBDATA~0 EQBS~0 MDTC~0 Rows 1275 807 1017 64243 64797 4022 9153 20209 69837 9153 228230 13935 4022 247170 31632 31660 25215 338380 Average Row Length 17 24 36 24 26 24 24 22 38 31 41 32 21 76 42 46 50 26 32 Leaf Kb Blocks Used 265 134 153 6237 7700 108 297 446 1558 3793 613 12600 460 455 13560 1798 1816 700 10900 1871 946 1080 44035 54364 763 2097 3149 11000 26780 4328 88959 3248 3212 95737 12694 12821 4942 76957 Storage Kb Quality Needed (%) 21 19 36 1506 1645 32 94 197 750 2114 366 7132 286 299 10138 1421 1546 640 10574 1 2 3 3 3 4 4 6 7 8 8 8 9 9 11 11 11 12 13 14
SHP_IDX_GDSI~0 1378
3222200 34
138267 976200 106987
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).
05-Oct-12
Report
Page 36 of 39
Historical data for "Transaction Activity" is obtained directly from ST03 transaction data.
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.
12.2 Response Times

The following diagrams show how the response time varies over time.
05-Oct-12
Report
Page 37 of 39
The "System Performance" diagram below shows the average response time in dialog tasks for the previous week. Historical data for "System Performance" is obtained directly from ST03 transaction data.
The "Database Performance" diagram below shows the average DB response time in dialog tasks.
The "Top 5 transactions" diagram below show the average response time in dialog tasks for the top 5 transactions.
05-Oct-12
Report
Page 38 of 39
The "Transaction Code" table below shows the load percentage caused by the top 5 transactions. Transaction Code ZMM_DOCFLOW SESSION_MANAGER ZRECON ZSO_PND MIRO Load (%) 7.6 7.3 5.1 4.7 4.2
12.3 System Operation

The following diagram or table shows important KPIs for system operation. Note: The column 'Availability' is filled for systems with SAP Basis 4.6 and higher.
05-Oct-12
Report
Page 39 of 39
12.4 Hardware Capacity
05-Oct-12

Ewa PPR

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ewa PPR

Caricato da

Copyright:

Formati disponibili

Report

Hint: to search, select this document and choose Ctrl+F

EarlyWatch Alert - PETL ECC Landscape 1 Service Summary

2 Performance Indicators for PPR

3.1 Hardware Configuration

Database Server PECCDB

3.2 Software Configuration

SAP R/3 Enterprise FINBASIS

SAP R/3 Basis PlugIn SAP Application Basis

3.2.2 SAP Kernel Release

3.2.3 Implemented SAP Notes via SAP Notes Assistant

3.3 Service Preparation

Hint SAP OS collector version could not be determined.

Recommendation Review SAP Note 1075827.

3.3.1 Service Preparation Check (RTCCTOOL)

3.3.2 Errors in Data Collection

3.3.3 SAP OS Collector

Days not Collected

3.3.4 Info: Active SAP Application Servers

4 Performance Overview PPR

Task type DIALOG RFC UPDATE UPDATE2 BATCH SPOOL

Dialog Steps 1108524 1139720 67209 52315 2003890 29525

4.1 Current Workload

Users Measured in System

4.2 Performance Evaluation

Task Steps Dia Upd HTTP 1107728 67209 0

Rating Task Time Steps Dia 0708

Avg. Response Time (ms)

Avg. CPU Time (ms) 191

Avg. Database Time (ms) 1355

Task Dia Upd HTTP

4.3 Transaction Profile Check

4.3.1 Transactions by Total Workload

5,1 341117,4 113934,0 186879,8 313,9

2033081 100,0 352 4 658917 28 2 29 678829 28 648074 28

14,1 27605370,3 19731215,0 6805230,0

4.3.2 Transactions by DB Load

5 Workload Distribution PPR

5.1 Workload by Application Module

Module Unknown CO-OM BC-CCM BC MM FI PP PY

Module BC Unknown MM FI PP CO-OM BC-CCM LE QM LO CO

5.2 DB Load Profile

5.3 RFC Communication

Total call time, s

6 SAP System Operating PPR

6.1 Update Errors

We did not detect any problems.

6.2 Table Reorganization

1664,0 375566 7936,0 195157

6.4 Program Errors (ABAP Dumps)

7.1 Users Authorized to Display all Tables

7.2 Users Authorized to Start all Reports

7.3 Users Authorized to Debug / Replace

9.1 Load per user

total (not a user name!) SAPSR3 OPS$PPRADM SYS ORACLE_OCM

128525900 2146638046 5949837482 1403846087

9.2 Database Parameters for PPR

9.2.0.1 Database Parameters

Please check SAP note 830576

Description Number of parallel execution processes/threads per CPU

Maximum number of database 80 shadow/background processes

Produce information replication_dependency_tracking for the Replication TRUE Server