SPP - PAR ABAP - Very Critical (Red) - EWA

Service Report
EarlyWatch ® Alert
Confidential
SAP System ID SPP

Product SAP ERP ENHANCE PACKAGE 6.08
Status Productive
DB System SAP HANA Database 2.00.066.00
Processed on SAP Solution Manager MSA

Release SOLUTION MANAGER 7.2
Service Tool 720 SP25

Service Content 23.06.2023
Analysis from 02.10.2023 Session No. 0010000000954

Until 08.10.2023 Installation No. 0020610116
Authorized for SAP employees delivering SAP Services and Support, authorized partners, and customer employees. Please
forward to authorized recipients only.
EarlyWatch Alert 20610116 - SPP 02.10.2023 - 08.10.2023
1 Service Summary
-
The EarlyWatch Alert service has detected severe problems that
may cause you to lose business. Please evaluate the
recommendations.
Alerts Decisive For Red Report

-
SAP HANA database: Severe issues for operating or administration in terms of log backup/recovery have been
detected.
Alert Overview
-
SAP HANA database: User SYSTEM is active and valid.
Users with critical authorizations, which allow to do anything in client 000
Users with critical authorizations, which allow to do anything in other client(s) than 000
Users with critical authorizations, which should not be used in production in other client(s) than 000
SAP HANA database: Some issues for operating or administration in terms of data backup/recovery have been
detected.
SAP HANA Database: The maintenance end for your HANA Database Support Package Stack will be reached in the
soon.
We found more than 30 ABAP dumps in your system.
SAP HANA database: Parameters are not set in accordance with the recommendation.
Secure password policy is not sufficiently enforced.
SAP HANA database: Recommended Audit configuration is not applied.
SAP HANA database: System Recommendations are not used or outdated.
User SAP* does not exists in client 000, potentially allowing critical logon in the future
User SAP* does not exists in other client(s) than 000, potentially allowing critical logon in the future
Note: If you send SAP EarlyWatch Alert data to SAP, this report can also be viewed in the SAP ONE Support Launchpad
or in "SAP for Me" respectively. How to access the interactive SAP Fiori application is explained in SAP Note 2520319 .
The link to the latest reports for this system: SAP EarlyWatch Alert Reports
Link to the analytical dashboard for this system: SAP EarlyWatch Alert Dashboard
Specific links to analytical detail pages in SAP EarlyWatch Alert Workspace are included in the respective sections in this
report.
Based on these findings, it is recommended that you perform the following Guided Self-Services.
Guided Self Service FAQ SAP Note
Security Optimization Service 1484124
For more information about Guided Self-Services, see SAP Enterprise Support Academy . Academy -
Check Overview
-
Topic Rating Topic Subtopic Rating Subtopic
Software Configuration for SPP - -
- - SAP Application Release -
Maintenance Phases
- - Security Risk Due to Outdated
Support Packages
- - Database - Maintenance Phases
Confidential Service Summary 2/120

- - Operating System(s) -
Maintenance Phases
- - SAP Kernel Release
Performance Overview SPP - -
Workload Distribution SPP - -
- - Workload by Application Module
- - DB Load Profile
SAP System Operating SPP - -
- - Availability based on Collector
Protocols
- - Program Errors (ABAP Dumps)
- - Update Errors
- - Table Reorganization
- - Critical Number Ranges
Hardware Capacity - -
Security - -
- - System Recommendations
(HANA)
- - Maintenance Status of current
SAP HANA Database Revision
- - SAP HANA System Privilege
DATA ADMIN
- - SAP HANA Password Policy
- - SAP HANA Audit Trail
- - SAP HANA SQL Trace Level
- - SAP HANA Network Settings for
Internal Services
- - SAP HANA SSFS Master
Encryption Key
- - Activation Status and Validity of
User SYSTEM
- - System Recommendations
(ABAP)
- - Age of Support Packages
- - Default Passwords of Standard
Users
- - Control of the Automatic Login
User SAP*
- - Protection of Passwords in
Database Connections
- - ABAP Password Policy
- - RFC Gateway Security
- - Message Server Security
- - Critical authorizations, which
allow to do anything
should not be used in production
should only see very limited use
in production
Software Change and Transport Management of - -
SPP
- - Number of Changes
- - Emergency Changes
- - Failed Changes
SAP HANA Database HPP - -
- - SAP HANA Stability and Alerts
- - SAP HANA Database
Configuration
- - SAP HANA Resource
Consumption
- - SAP HANA Workload and
Performance
- - Size and Growth
- - Administration
SAP NetWeaver Gateway - -
- - MetaData Cache Activation
- - Logging Configuration
- - Gateway Error Logs
- - Important Periodic Jobs
Fiori Checks for SPP - -
- - Maintenance and Update
Strategy for SAP Fiori Front-End
Server
- - SAPUI5 Version
- - SAP Fiori Cache Buster
Activation
- - HTTP/2 Support
- - SAP Fiori Launchpad
Performance - Home Page Mode
- - Activated but unused ICF
services in UI5 apps
The check overview includes checks executed with a green result, which do not appear in the report.
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 to resolve 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, please contact your customer representative (for
example, TQM or ESA). To contact the SAP Enterprise Support advisory team or Customer Interaction Center, please refer
to the local contact number specified in SAP Note 560499 . For details of how to set the appropriate priority level, see SAP
Note 67739 .
-
1.1 Performance Indicators for SPP
-
The following table shows the relevant performance indicators in various system areas.
Area Indicators Value Trend
System Performance Active Users (>400 steps) 117
- Avg. Availability per Week 100 %
- Avg. Response Time in Dialog Task 291 ms
- Max. Dialog Steps per Hour 8602
- Avg. Response Time at Peak Dialog Hour 227 ms
- Avg. Response Time in RFC Task 307 ms
- Max. Number of RFCs per Hour 1391
- Avg. RFC Response Time at Peak Hour 256 ms
Hardware Capacity Max. CPU Utilization on DB Server 4%
Database Performance Avg. DB Request Time in Dialog Task 100 ms
- Avg. DB Request Time for RFC 20 ms
- Avg. DB Request Time in Update Task 27 ms
Database Space Management DB Size 165.30 GB

2 Landscape
-
2.1 Products and Components in current Landscape
-
Product
-
System SAP Product Product Version
SPP_PAR~ABAP SAP ERP ENHANCE PACKAGE 6.08
Main Instances
-
Related System Main Instance
SPP_PAR~ABAP SAP ECC Server
Databases
-
Related System Database System Database Version DB ID
SPP_PAR~ABAP SAP HANA Database 2.00.066.00 HPP
-
2.2 Servers in current Landscape
-
SAP Application Servers
-
System Host Instance Name Logical Host ABAP JAVA
SPP_PAR~ABAP srvprdpar1 srvprdpar1_SPP_00 srvprdpar1 -
DB Servers
-
Related System Host Logical Host (SAPDBHOST)
SPP_PAR~ABAP srvprdpar1 srvprdpar1
Components
-
Related System Component Host Instance Name Logical Host
SPP_PAR~ABAP ABAP SCS srvprdpar1 srvprdpar1_SPP_01 srvprdpar1
-
2.3 Hardware Configuration
-
Host Overview
-
Host Hardware Model CPU Type CPU MHz Virtualiza Operating System CPUs Cores Memory
Manufact tion in MB
urer
srvprdpar1 VMware, VMware7, Xeon Gold 2200 VMWARE SUSE Linux 24 24 515464
Inc. 1 6338N Enterprise Server 15
(x86_64)
Confidential Landscape 5/120

3 Service Data Quality and Service Readiness

-
Some service data is missing for this report and not all checks could be performed.
This does not impact the report rating.
The SAP ERP ENHANCE PACKAGE system SPP is not fully prepared for delivery of
future remote services .
Rating Check Performed

Sending EarlyWatch Alert of SPP to SAP Backbone
Configuring SPP for SAP Note Assistant
Service Data Quality
Service Preparation of SPP
-
3.1 Sending EarlyWatch Alert of SPP to SAP Backbone
-
System SPP is prepared for
SAP Support Backbone update
sending EWA data on HTTPS through Solution Manager 7.2 MSA
All connections to SAP Support Backbone use https protocol only. For a how to, refer to Connectivity to SAP .
The following table shows the latest data transmissions for system SPP:
Latest Service Data for System SPP Sent to SAP
-
Date System Sends Kernel Kernel ST-PI ST-PI Destina User Ready Date Dest.
(collect EWA? tion for 2020 (last Functio
ed) sent) nal?
09.10.2 Solution yes 753_RE 740 20 HTTPS S-user 02.10.2
023 Manage L 1100 -> SAP 023
r 7.2
MSA
-
3.2 Service Data Quality
-
For this service, only data of minor importance is missing. This section provides a comprehensive overview of how the
content of the report is affected.
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) .
Recommendation: To resolve issues with the service data quality, follow the hints and SAP Notes provided below.
-
3.2.1 Quality of Data in Service Data Control Center (SDCC)
-
Quality Of Service Data In ST-A/PI
-
Prio. Report Area affected Details and Related ST-A/PI Module SAP Note
Application Management of System EWM Checks requiring 2827332
SPP online collectors
are missing. To allow
online collectors
run report RTCCTOOL .ÿST-A/PI function: COLLECTED DATA
in project DCA
Confidential Service Data Quality and Service 6/120

Readiness
Prio. Report Area affected Details and Related ST-A/PI Module SAP Note
Application Management of ABAP MM Checks requiring 2827332
System SPP online collectors
aremissing. To allow
online collectors
, run report RTCCTOOL.ÿST-A/PI function:
MISSING_MATERIALS in project NDL used in section '
Materials Management - Inventory Management Checks
Application Management of ABAP Content is only available if you allow 2827332
System SPP online collectors
. Run report RTCCTOOL.ÿST-A/PI function:
SAP_BACKBONE_UPDATE in project NDL used in section '
Service Data Quality and Service Readiness
-
3.2.2 Quality of Service Data in Solution Manager Diagnostics - BW
-
Prio. Report Area affected Details and Related Infocube SAP Note
Workload of ABAP System SPP No performance data is returned from 1840395
BW InfoCube.ÿInfocube: 0CCMSMTPH
used in section '
Workload Overview SPP
Legend for 'Priority' Column Above
-
Prio. Explanation: Impact of Missing or Erroneous Data
Some important check could not be processed. The report can be rated green nevertheless.
Only checks of minor importance are affected.
An optional check was skipped.
-
3.3 Service Preparation of SPP
-
Service Preparation Check (RTCCTOOL)
Service Data Control Center of SPP
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 .
Confidential Service Data Quality and Service 7/120

Readiness
4 Software Configuration for SPP

-
We did not find any critical issues concerning the software configuration on your
current 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 End of Mainstream Maintenance Status
EHP8 FOR SAP ERP 6.0 31.12.2027
SAP NetWeaver Version End of Mainstream Maintenance Status

SAP NETWEAVER 7.5 31.12.2027
Rating Legend
-
Rating Description
Mainstream / Extended maintenance offered by SAP is available for the next 18 months or longer.
Mainstream / Extended maintenance offered by SAP will end in 6 to 18 months.
Mainstream / Extended maintenance offered by SAP has expired or will expire in the next 6 months.
Your main product version runs under SAP mainstream maintenance until 31.12.2027.
Your SAP NetWeaver version is supported in combination with your main product version until 31.12.2027.
Please note that this check, if created on your on-premise SAP Solution Manager, does not take account of extended
maintenance options. In this case, your main product version is checked for SAP mainstream maintenance only ,
which might lead to invalid ratings, especially for SAP S/4HANA 1709, SAP S/4HANA 1809, and SAP S/4HANA 1909.
A complete verification, including also your individual extended maintenance contracts, is available only on your EWA
Workspace account at SAP ONE Support Launchpad or SAP for Me respectively.
For general information about EarlyWatch Alert Workspace see How to access the SAP EarlyWatch Alert apps in the SAP
ONE Support Launchpad .
-
4.2 Support Package Maintenance - ABAP
-
The following table shows an overview of currently installed software components.
Support Packages
-
Software Version Patch Level Latest Avail. Patch Level Support Package Component
Component Description
EA-DFPS 618 19 21 SAPK-61819INEADFPS EA-Defense Forces
& Public Security
EA-FINSERV 618 19 21 SAPK-61819INEAFINSRV SAP R/3 Enterprise
Financial Services
EA-GLTRADE 618 19 21 SAPK-61819INEAGLTRAD SAP R/3 Enterprise
Global Trade
EA-HR 608 109 124 SAPK-608A9INEAHR SAP R/3 Enterprise
Human Resource &
Travel Extension
Confidential Software Configuration for SPP 8/120

EA-IPPE 618 7 8 SAPK-61807INEAIPPE SAP Integrated
Product and
Process
Engineering
EA-PS 618 19 21 SAPK-61819INEAPS SAP R/3 Enterprise
Public Services
EA-RETAIL 618 19 21 SAPK-61819INEARETAIL SAP R/3 Enterprise
Retail
ECC-DIMP 618 19 21 SAPK-61819INECCDIMP ECC Discrete
Industries Mill
Products
ECC-SE 605 21 22 SAPK-60521INECCSE ESA FAST TRACK
(ECC-SE)
ERECRUIT 617 23 25 SAPK-61723INERECRUIT HCM E-Recruiting
FI-CA 618 1 21 SAPK-61801INFICA FI-CA, Contract
Accounts
Receivable and
Payable (virtuell)
FI-CAX 618 1 21 SAPK-61801INFICAX FI-CAX: Extended
FI-CA
FINBASIS 748 19 21 SAPK-74819INFINBASIS FINBASIS
FSCM_CCD 618 19 21 SAPK-61819INFSCMCCD Fscm Ccd
INSURANCE 618 1 21 SAPK-61801ININSURANC INSURANCE SAP
Insurance
IS-CWM 618 1 21 SAPK-61801INISCWM IS-CWM Catch
Weight
Management
IS-H 618 1 35 SAPK-61801INISH IS-Hospital
IS-M 618 1 21 SAPK-61801INISM Media
IS-OIL 618 1 21 SAPK-61801INISOIL SAP for Oil & Gas
IS-PRA 618 19 21 SAPK-61819INISPRA IS-PRA
IS-PS-CA 618 1 21 SAPK-61801INISPSCA IS-Public Sector
Contract
Accounting
IS-UT 618 1 21 SAPK-61801INISUT IS-UT
LSOFE 617 22 24 SAPK-61722INLSOFE Learning Solution -
Front End
MDG_APPL 619 20 22 SAPK-61920INMDGAPPL MDG Applications
MDG_FND 749 20 22 SAPK-74920INMDGFND MDG Foundation
MDG_MDC 100 20 22 SAPK-10020INMDGMDC Master Data
Consolidation
MDG_UX 619 20 22 SAPK-61920INMDGUX MDG Additional
User Interface
PLMWUI 748 19 21 SAPK-74819INPLMWUI PLM WUI
SAP_ABA 750 25 28 SAPK-75025INSAPABA SAP
Anwendungsbasis
SAP_AP 750 17 19 SAPK-75017INSAPAP SAP Application
Platform
SAP_APPL 618 19 21 SAPK-61819INSAPAPPL SAP APPL
SAP_BASIS 750 25 28 SAPK-75025INSAPBASIS SAP Basis
component
SAP_BS_FND 748 19 21 SAPK-74819INSAPBSFND SAP Business
Suite Foundation
SAP_BW 750 25 28 SAPK-75025INSAPBW SAP Business
Warehouse
SAP_FIN 618 19 21 SAPK-61819INSAPFIN Financials

SAP_GWFND 750 26 28 SAPK-75026INSAPGWFND SAP NetWeaver
Gateway
Foundation
SAP_HR 608 109 124 SAPKE608A9 SAP HR
SAP_UI 754 12 14 SAPK-75412INSAPUI User Interface
Technology
SEM-BW 748 19 21 SAPK-74819INSEMBW SAP SEM
ST-A/PI 01V_731 2 2 SAPKITABC5 ST-A/PI Service
Tools for
Applications
Plug-In
ST-PI 740 24 24 SAPK-74024INSTPI Solution Tools
Plugin
UIBAS001 500 8 8 SAPK-50008INUIBAS001 UI for Basis
Applications
UIEAAP01 100 16 16 SAPK-10016INUIEAAP01 UI for ERP central
Applications
UIX01EAP 100 14 14 SAPK-10014INUIX01EAP UI for ERP Central
Applications
WEBCUIF 748 19 21 SAPK-74819INWEBCUIF SAP Web UIF
-
4.3 Database - Maintenance Phases
-
Database Version End of Standard Vendor Support* Comment Status SAP Note
SAP HANA Database 2.0 - Follows Application 2378962
* 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.
-
4.4 Operating System(s) - Maintenance Phases
-
Host Operating System End of Standard End of Extended Vendor Comment Status SAP Note
Vendor Support*
Support*
srvprdpar1 SUSE Linux Enterprise 31.07.2028 31.07.2031 Limited (LTSS) 936887
Server 15 (x86_64)
* Maintenance phases and duration for the operating system 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 HANA Database Version for HPP
-
The following table shows your current/planned SAP HANA database version.
HANA Database Version
-
SID SPS Stack SP Revision Maintenance Revision In Maintenance ? SAP Notes Upgrade
Information
HPP 2.00 SP 06 2.00.066.000 no 2378962
-
4.5.1 HANA Database Support Package Stack for HPP
-
The following table shows your current/planned SAP HANA database support package stack. For current support package
stack the remaining number of days until the maintenance end is reached is calculated. If the number of days until the
maintenance end is larger than 90 days a warning is shown.
Support Package Stack
-
Current Version Current Support Available Available Maintenance Number of days Rating
Package Stack Version Support end until
Package Stack Maintenance
End
2 06 2 07 31.12.2023 83
You will reach the maintenance end of the Support Package within the next 90 days or you will reach the maintenance end
of the SAP HANA Version within the next 180 days.
-
4.6 SAP HANA: SQLDBC Version
-
4.6.1 SAP HANA: Installed SQLDBC Version
-
The following table shows your currently installed SAP HANA database client component version.
Instance Name SQLDBC Version Rating
srvprdpar1 00 2.15.019
SAP Note Description

1906576 HANA client and server cross-version compatibility
2339267 The SAP HANA client version and installation manifest file doesn't match currently available SAP HANA
server version information
-
4.7 SAP HANA: Installed DBSL Version
-
The following table shows the DBSL version currently installed.
Instance Current DBSL Current DBSL Recommended Recommended Rating
Release Patch DBSL Release DBSL Patch
srvprdpar1_SPP_00 753 1200 753 423
Your installed SAP HANA DBSL meets the recommended requirement to access the SAP HANA database.
-
4.8 SAP Kernel Release
-
Your system is running an SAP kernel that is up to date. This means that you have the latest available improvements and
error corrections offered by SAP to its customers.
Instance(s) SAP Kernel Release Patch Level Age in Months OS Family
srvprdpar1_SPP_00 753 1200 5 Linux (x86_64)
-
4.8.1 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://launchpad.support.sap.com/#/softwarecenter/support/index (Support Packages &

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
KRNL753PL1200 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 SPP
-
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.
Server Max. CPU Date Rating RAM Max. Date Rating Analysis Analysis
load [%] [MB] Paging Start End
[% of
RAM]
srvprdpar1 4 03.10.2023 515.464 0 - 02.10.2023 08.10.2023
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).
Confidential Hardware Capacity 13/120

6 Workload of System SPP

-
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 27,9 0,0 8,7 9,7 10,3
RFC 13,6 0,0 0,7 0,9 0,0
BATCH 5,3 0,0 1,2 1,2 0,0
Others 0,9 0,3 0,1 0,1 0,0
-
6.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 Low Activity Medium Activity High Activity Total Users
dialog steps per week 1 to 399 400 to 4799 4800 or more -
measured in system 62 92 25 179
-
6.2 Workload Distribution SPP
-
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.
-
6.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
- Database time: total database load generated by the application
All programs that are not classified in the Application Hierarchy are summarized in the "Unassigned" category. Customer
Confidential Workload of System SPP 14/120

programs, industry solutions, and third-party add-on developments may fall into this category.
The Application Hierarchy can be found in the Repository Browser (transaction SE80): in the "Object Category" selection
field choose "Application Hierarchy".
-
6.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.

7 Performance Overview SPP

-
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.
Note: To access the response time statistics in SAP EarlyWatch Alert Workspace, click system response time
The following table shows the average response times for various task types:
Averages of Response Time Components in ms
-
Task type Dialog Steps Response Time CPU Time Wait Time Load Time DB Time GUI Time
DIALOG 345.944 290,5 90,4 0,1 1,0 100,5 107,7
RFC 158.244 307,5 15,7 0,0 0,1 19,7 0,0
UPDATE 19.460 51,8 25,8 0,1 1,2 26,6 0,0
UPDATE2 6.263 33,0 8,7 0,1 0,7 24,3 0,0
BATCH 96.279 197,9 44,3 0,0 1,1 45,4 0,0
SPOOL 12.059 216,4 5,7 76,6 0,2 6,1 0,0
HTTP 10.083 1,7 1,5 0,0 0,2 0,0 0,0
HTTPS 10.130 3,0 2,1 0,1 0,2 0,1 0,0
-
7.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 345.943
Upd 19.460
HTTP 10.083
HTTPS 10.130
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.
Task Reference for Avg. Response Time Reference for Avg. Reference for Avg. Reference for Avg.
(ms) Yellow Rating Response Time (ms) DB time (ms) Yellow DB time (ms) Red
Red Rating Rating Rating
Dia 1.200 3.600 600 1.800
Upd 2.400 3.600 1.200 1.800
HTTP 1.200 3.600 600 1.800
HTTPS 1.200 3.600 600 1.800
-
7.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.
Confidential Performance Overview SPP 17/120

-
7.2.1 Transactions by Total Workload
-
To access the transaction response time in SAP EarlyWatch Alert Workspace, click here .
The following tables list the activities with the highest contribution to the total workload.
Workload by Transaction (Dialog/HTTP(S)/WS-HTTP )
-
Transaction Type Dialog Steps Total Resp. Avg. Resp. Avg. CPU Avg. DB Avg. GUI
Time in % Time in ms Time in ms Time in ms Time in ms
FBL3N DIA 42.239 20,9 605,9 184,7 430,7 55,2
IDCP DIA 1.914 6,7 4.256,4 1.419,7 3.137,8 228,1
FBL5N DIA 59.664 6,1 124,9 42,9 62,0 30,0
ZF02 DIA 637 5,4 10.347,5 10.241,3 38,2 68,4
SESSION_MANAGER DIA 11.920 4,4 449,0 16,7 5,7 425,6
VA01 DIA 21.734 3,8 215,6 24,6 8,6 169,2
ZC04 DIA 2.658 2,4 1.106,9 225,3 611,7 349,8
SQ01 DIA 2.028 2,4 1.421,2 801,6 201,5 465,4
FBL1N DIA 25.603 2,3 111,5 31,1 23,6 60,2
FAGLB03 DIA 3.730 1,8 598,5 55,4 30,4 500,4
7.8% of the total response time in the above table is caused by customer transactions.
If response 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-PERF if
required.
Workload by Transaction (Batch)
-
Transaction Dialog Steps Total Resp. Time Total Resp. Time Total CPU Time Total DB Time in
in % ins ins s
SWNC_TCOLL_S 22.715 6,2 7.598,0 1.440,0 1.379,5
TARTER
/BDL/TASK_SCH 170 2,9 3.548,0 23,0 48,1
EDULER
(BATCH) 38.777 1,2 1.452,0 546,0 964,1
RSDBAJOB 2 1,0 1.266,0 0,0 0,4
Z0MI0004 1 0,9 1.153,0 1.049,0 798,8
Z0FC010 14 0,8 974,0 63,0 56,1
RSBTCRTE 28.667 0,4 498,0 206,0 200,5
RSCONN01 1.008 0,4 479,0 13,0 15,7
Z0FI0020 1.006 0,2 289,0 211,0 86,7
RFWT0010 7 0,2 278,0 173,0 116,6
1.9% of the total response time in the above table is caused by customer transactions.
-
7.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) )
-
Transaction Type Dialog Steps Total DB Time in % Avg. DB Time in ms
FBL3N DIA 42.239 46,3 430,7
IDCP DIA 1.914 15,3 3.137,8
FBL5N DIA 59.664 9,4 62,0
ZC04 DIA 2.658 4,1 611,7
ME2L DIA 2.666 1,8 271,8
FBL1N DIA 25.603 1,5 23,6
Transaction Type Dialog Steps Total DB Time in % Avg. DB Time in ms
SQ01 DIA 2.028 1,0 201,5
KKS1 DIA 21 0,8 14.915,8
KKAO DIA 33 0,6 7.504,2
VA01 DIA 21.734 0,5 8,6
4.1% 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-PERF if
required.
Database Load by Transactions (Batch)
-
Transaction Dialog Steps Total DB Time in % Total DB Time ins
SWNC_TCOLL_STARTER 22.715 3,5 1.379,0
(BATCH) 38.777 2,5 964,0
Z0MI0004 1 2,0 799,0
RSBTCRTE 28.667 0,5 200,0
RFWT0010 7 0,3 117,0
/SSA/EBP 1 0,3 100,0
Z0FI0020 1.006 0,2 87,0
Z0FC010 14 0,1 56,0
/BDL/TASK_SCHEDULER 170 0,1 48,0
ZFIRE_RECLASIFICACIONIVA 1.344 0,1 43,0
2.4% of the total database time in the above table is caused by customer transactions.

8 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 Load [s] Load %
Local system SPP 13.718 83,97
Sum of external systems 2.619 16,03
RFC load (sum of above) 16.336 100,00
RFC load in Performance Overview 48.656 297,84
Load of all task types in Performance Overview 177.051 1.083,79
Top 20 RFC Calls From External Systems - Average Times [ms]

-
Initial Initial Action Total Resp. % of RFC Avg. Avg. CPU Avg. DB Avg. Roll
System Time ins Load Response Time Time Wait Time
Time
WD_SISE_M EFWK 2.454 15,02 31,6 10,0 7,3 0,0
AIN_APP RESOURCE
MANAGER
WD_SISE_M DIAGLS_CO 96 0,59 570,1 236,7 342,5 0,0
AIN_APP MPUTE_STA
TUS
WD_SISE_M SM:SCMON_ 47 0,29 840,0 229,3 366,7 0,1
AIN_APP CONTROL
WD_SISE_M SM:USR_ST 12 0,07 11,8 2,4 2,1 0,0
AIN_APP ATUS_UPDA
TE
SPQ STMS 6 0,04 529,8 50,0 85,7 0,0
WD_SISE_M SM:AGSSIS 1 0,01 9,7 1,9 1,2 0,0
AIN_APP E_USER_CL
EANUP
SPD STMS 1 0,01 553,5 15,0 14,0 0,0
WD_SISE_M SM:SYSTEM 1 0,01 980,0 160,0 359,0 0,0
AIN_APP RECOMMEN
DATIONS
SPQ ZM28 1 0,00 540,0 10,0 17,0 0,0
WD_SISE_M SM:EXEC_S 1 0,00 538,0 10,0 27,0 0,0
AIN_APP ESS_6_001
0000000113
Top 20 RFC Calls From Local System - Average Times [ms]

-
Time
SPP /BDL/TAS 6.185 37,86 25.038,8 862,1 3.160,7 0,1
K_PROCES
SOR
Confidential RFC Load by Initiating Action 20/120

Time
SPP /BDL/TA 2.809 17,20 22.295,2 440,6 5.162,9 0,1
SK_PROC
ESSOR00
00007449
SPP SAP_COLL 2.107 12,90 2.063,7 302,6 705,3 0,1
ECTOR_PE
RFMON_RS
DOOS_MSC
SPP /UI5/AP 1.047 6,41 478,5 18,6 17,8 0,0
P_INDEX
_CALCUL
ATE
SPP SAP_COLL 779 4,77 162,2 124,1 37,6 0,0
ECTOR_PE
RFMON_SW
NCCOLL
SPP SAP_COLL 590 3,61 502,1 1,9 0,6 0,1
ECTOR_PE
RFMON_RS
AMON40
SPP <AUTO 85 0,52 21,2 10,1 8,6 0,1
ABAP
PROCESSIN
G>
SPP /BDL/TA 68 0,41 33.862,5 10,0 29,0 0,0
SK_PROC
ESSOR00
00007445
SPP /UI5/UP 19 0,12 114,8 12,3 3,2 0,1
D_ODATA
_METADA
TA_CACHE
SPP STMS 11 0,07 218,5 44,3 82,0 0,1
SPP KSU5 5 0,03 62,8 16,1 45,9 0,1
SPP ME23N 4 0,02 981,3 65,0 15,8 0,0
SPP RFITEMAR 2 0,01 467,8 22,5 24,5 0,0
SPP SDCCN 1 0,01 618,5 45,0 66,0 0,0
SPP SESSION_M 1 0,01 56,2 11,3 28,6 0,0
ANAGER
SPP MIGO 1 0,01 846,0 90,0 35,0 0,0
SPP RFITEMGL 1 0,00 400,5 25,0 36,5 0,0
SPP FBL3N 1 0,00 386,0 20,0 25,5 0,0
SPP VA05 1 0,00 377,0 20,0 19,5 0,0
SPP SBWP 1 0,00 561,0 20,0 39,0 0,0
Confidential RFC Load by Initiating Action 21/120

9 SAP System Operating SPP

-
The daily operation of your system was analyzed. We detected some problems that
may impair system operation and stability.
Rating Check
Availability based on Collector Protocols
Program Errors (ABAP Dumps)
Update Errors
Table Reorganization
Critical Number Ranges
-
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
Confidential SAP System Operating SPP 22/120
-
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.

-
9.3 Table Reorganization
-
The largest tables and/or rapidly growing tables of system SPP were checked. No standard SAP recommendations for the
applicable data volume management were found.
-
9.4 Program Errors (ABAP Dumps)
-
120 ABAP dumps have been recorded in your system in the period 02.10.2023 to 09.10.2023. 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
02.10.2023 14
03.10.2023 15
04.10.2023 14
05.10.2023 20
06.10.2023 17
07.10.2023 17
08.10.2023 14
09.10.2023 9
Name of Runtime Error Dumps Server (e.g.) Date (e.g.) Time (e.g.)
CONVT_NO_NUMBER 1 srvprdpar1_SPP_00 03.10.2023 10:07:16
DBSQL_DUPLICATE_KEY_ERROR 2 srvprdpar1_SPP_00 05.10.2023 09:35:30
TSV_TNEW_PAGE_ALLOC_FAILED 3 srvprdpar1_SPP_00 07.10.2023 05:49:29
RAISE_EXCEPTION 9 srvprdpar1_SPP_00 09.10.2023 11:18:49
LOAD_PROGRAM_NOT_FOUND 105 srvprdpar1_SPP_00 09.10.2023 12:55:49
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.
-
9.5 Critical Number Ranges
-
We have checked the usage of ABAP number ranges and found no issues.

10 Security
-
Critical security issues were found in your system. See the information in the
following sections.
Rating Check System ID

System Recommendations (HANA) HPP
Maintenance Status of current SAP HANA Database Revision HPP
SAP HANA System Privilege DATA ADMIN HPP
SAP HANA Password Policy HPP
SAP HANA Audit Trail HPP
SAP HANA SQL Trace Level HPP
SAP HANA Network Settings for Internal Services HPP
SAP HANA SSFS Master Encryption Key HPP
Activation Status and Validity of User SYSTEM HPP
System Recommendations (ABAP) SPP
Age of Support Packages SPP
Default Passwords of Standard Users SPP
Control of the Automatic Login User SAP* SPP
Protection of Passwords in Database Connections SPP
ABAP Password Policy SPP
RFC Gateway Security SPP
Message Server Security SPP
Critical authorizations, which allow to do anything SPP
Critical authorizations, which should not be used in production SPP
Critical authorizations, which should only see very limited use in production SPP
-
10.1 SAP HANA Database HPP
-
10.1.1 System Recommendations (HANA)
-
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,
refer to https://support.sap.com/sysrec .
-
10.1.2 SAP HANA Audit Trail
-
Sources of information for the SAP HANA audit trail:
- SAP HANA Security Guide - SAP HANA Administration Guide - SAP HANA Audit Trail Best Practice in the SCN
-
10.1.2.1 Auditing Status
-
Auditing is disabled in the security settings of your SAP HANA database.
Recommendation: Activate the SAP HANA audit trail and define appropriate audit policies.
Confidential Security 25/120

-
10.1.2.2 Audit Policies
-
No customer-defined audit policies are enabled.
Recommendation: Define audit policies according to your needs.
-
10.1.3 Activation Status and Validity of User SYSTEM
-
The activation status and validity dates (VALID FROM and VALID TO) of user SYSTEM have been checked in system
table USERS.
Rating Check
User SYSTEM is currently active and valid.
Active standard users are an easy and widely used target for hacking attacks since they are available in every system.
Furthermore, the user SYSTEM is like a super user with very powerful user authorizations that cannot be revoked.
Recommendation: Review the current usage of user SYSTEM and set up and test a user and role concept, so that
the use of user SYSTEM becomes obsolete.
Deactivate the user account with the SQL statement:

ALTER USER SYSTEM DEACTIVATE USER NOW.
To prevent misuse of user SYSTEM, activate related audit policies in your SAP HANA system as described in the
SAP HANA Administration Guide.
-
10.2 ABAP Stack of SPP
-
10.2.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,
refer to https://support.sap.com/sysrec .
-
10.2.2 Default Passwords of Standard Users
-
Standard users have default passwords.
Recommendation: Run report RSUSR003 to check for standard users having default passwords in some clients.
Ensure that user SAP* exists in all clients and has a non-default password even if profile parameter
login/no_automatic_user_sapstar is set to 1.
Ensure that user SAPCPIC has a non-default password in all clients.
User EARLYWATCH was used in client 066 only. This client should no longer exist, and therefore, this user should
not exist either in any client.
SAP Note 1749142 describes how to remove an obsolete client 066.
Make sure that user TMSADM exists only in client 000 and that the standard password has been changed. SAP Note
1414256 describes a support tool for changing the password of user TMSADM in all systems of the transport domain.
For more information, see "Protecting Special Users" either on SAP Help Portal or in the SAP NetWeaver AS ABAP
Security Guide.
-
10.2.3 ABAP Password Policy
-
If password login is allowed for specific instances only, the password policy is checked only for these instances.

-
10.2.3.1 Validity of Initial Passwords
-
Rating Parameter Instance Current Value(s)
login/password_max_idle_initial srvprdpar1_SPP_00 0
Initial passwords are valid for more than 14 days.
Recommendation: Proceed as follows:
-- Handle users of type C (Communication) with initial passwords because they will be locked if the above profile
parameter is set.
Use transaction SUIM/report RSUSR200 in each client to find users of type C (Communication).
If these users are active and in use, switch the user type to B (System). This has no negative effect.
– Restrict the password validity to 14 days or less. Note that the value 0 grants unlimited validity.
- For more information, see SAP Note 862989 and the Profile Parameters for Logon and Password (Login
Parameters) section, either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.
-
10.2.4 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.2.4.1 Critical authorizations, which allow to do anything
-
10.2.4.1.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 No. of Valid Users Rating
000 7 9
001 2 3
Authorization profile: SAP_ALL
-
10.2.4.1.2 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 specified
number of users for each client have the checked authorization.
200 8 243
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 authorization for
OBJTYPE=DEBUG with ACTVT=02 from roles and only allow any other object type for S_DEVELOP. This means that
development and debugging with visualization is still possible.
You can achieve this by adding two 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.
-
10.2.4.2 Critical authorizations, which should not be used in production
-
10.2.4.2.1 Users Authorized to Change or Display all Tables
-
Unauthorized access to sensitive data is possible if too many users have this authorization. The specified number of users
for each client have the checked authorization.
200 101 243
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 DICBERCLS = *

11 Software Change and Transport

Management of SPP
-
Software change management issues were found in your system. See the information
in the following sections.
-
11.1 SAP Netweaver Application Server ABAP of SPP
-
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 1265070 .
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.
Confidential Software Change and Transport 29/120

Management of SPP
Date Workbench and Relocation Requests Customizing Requests Transport of Copies
03.10.2023 0 1 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.
Date Objects in Workbench and Relocation Objects in Customizing Objects in Transport of

Requests Requests Copies
03.10.2023 0 1 0
-
11.1.4 Emergency Changes
-
We analyzed the number of emergency changes in system SPP in the last week.
Rating Item Value Explanation
Transport requests created in 0 Number of transport requests; created or released in production.
production
Transport requests with short transition 1 The duration between the export from the development system
time and the import into the production system was shorter than one
day.
Total number of transport requests 1 Total number of transport requests in production.
-
11.1.4.1 Transport Requests with a short Transition Time
-
Request Export from DEV Import in PRD
SPDK900604 03.10.2023 10:09:21 03.10.2023 15:57:12
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 SPP during the last week.
Management of SPP
Rating Item Value Explanation

Transport requests with import errors 0 Number of transport requests with import errors that were not
resolved within one hour.
Overtakers and bypassed transport 0 If an old object version overwrites a newer one we count this as a
requests transport sequence error. We count both the overtaker transport
and the bypassed transport. Each transport is only counted once.
Total number of transport requests 1 Total number of transport requests that were imported or
released in production within the last week.

Management of SPP
12 Financial Data Quality

-
After execution of the “quick” consistency checks and execution of
the main reconciliation report, issues were identified that require
your attention.
However, the FIN_CORR_RECONCILE program has not yet been
executed OR your system was not fully scanned. Refer to the
“Reconciliation Run Results” for more information if your system
was not fully scanned.
The current Financial Data Quality chapter contains essential information about the quality and consistency of your
financial data.
This chapter is structured with three subchapters: “Financial Data Integrity”, “Financial Data Management”, “Reconciliation
of ECC Systems (prior to S/4HANA)”. The first two chapters are based on “quick” checks of different financial modules. The
latter chapter displays the status and results of the main reconciliation checks.
It is important to understand that, due to the technical limitation of the automated data collection, we can cover only a
limited result list in your system using the “quick” consistency checks. The reconciliation checks are the main sources of
data for our financial data quality analysis and should be executed. These checks ensure full transparency at the
consistency level of your financial data.
The Financial Data Quality topic is crucial for various daily business operations (for example, before month-end-closing), as
well as in terms of SAP S/4HANA. Resolving inconsistency issues early on will help you to accelerate the System
Conversion, Greenfield Implementation or Selective Data Transition to SAP S/4HANA and avoid unexpected
showstoppers. We strongly advise you to study the information displayed in this chapter and take appropriate action.
Additional Benefits (FDQ)
The relevant data for Financial Data Quality was collected in the system and stored in the SDCCN download. If you gave
your consent, this data has been sent to SAP for further analysis. The analysis contains several checks regarding financial
data inconsistencies. After the analysis has finished, the results will be provided in SAP Support Launchpad via the link
displayed in the "Link to SAP Support Launchpad" column in the table below. Analyses may not be included in the FDQ
Dashboard since some analyses are filtered out. (For example, No data for BKPF or the analysis is deprecated).
Note:
For more information about how to activate content for FDQ, see https://launchpad.support.sap.com/#/notes/2980796
[Knowledge Base Article 2980796.]
-
12.1 Financial Data Integrity
-
This chapter shows whether specific financial data quality issues exist in your SAP ERP system system. Resolution of the
identified issues is not time-critical, unless an SAP S/4HANA project is planned. It is generally recommended to unravel
them as soon as possible, in order to avoid problems with your business operations in the future. Please keep in mind that
this EarlyWatch Alert chapter is focused on checking certain common financial data quality issues. A comprehensive data
quality check must be performed using the available SAP standard reconciliation check reports. For Enterprise Support,
Premium Engagement, New MaxAttention, ActiveAttention, and Active Embedded Attention customers, it is possible to
order a Financial Data Quality service, which checks the entire system and evaluates all data consistency issues.
-
12.1.1 Mismatch of Function Setting between Master Data and Items
-
The issues below are inconsistencies between the settings at item level and master data level of a G/L account. A
mismatch of configuration between master data level and item level can have a negative impact on activities such as
clearing or archiving. Such mismatches are usually caused by changes of the configuration of G/L account beyond the
official guidelines and recommendations.
The following FI-GL issues have been identified in your system:
Type 1: Mismatch of function setting between master data (marked as open item managed) and items (marked as
Confidential Financial Data Quality 32/120
not open item managed)
Impact on Business:
Account contains items that cannot be cleared.
Furthermore, such errors can endanger future migration into a green field system, migration to NewGL requires the
correctness of sum of open items, otherwise the balance carry forward of the migration year will be created in the wrong
way and the balance sheet might not balance to zero any more. This fact means, that the data correctness of the migration
into a green field system is endangered. Please note, that the correction of this error is a prerequisite for future possible
conversion to SAP S/4HANA.
Recommendation: The errors are related to G/L accounts that are open-item-managed. Consider the consistency
between sum of open items and the balances of the current fiscal year when correcting open-item-managed
accounts.
Type 2: Mismatch of function setting between master data (marked as not open item managed) data and items
(marked as open item managed).
Impact on Business:
Account contains items that are never to be archived.
Furthermore, such errors can endanger future migration into a green field system, migration to NewGL requires the
correctness of sum of open items, otherwise the balance carry forward of the migration year will be created in the wrong
way and the balance sheet might not balance to zero any more. This fact means, that the data correctness of the migration
into a green field system is endangered. Please note, that the correction of this error is a prerequisite for future possible
conversion to SAP S/4HANA.
Recommendation: This issue can be solved by implementing and executing the report ZF_SWITCH_OFF_XOPVW
of SAP Note 175960 .
The following list shows G/L accounts that have a mismatch between master data and item settings:
Error Type Company Code G/L Account Fiscal Year Analysis Date Error Description
1 INDU 1901016021 2011 09.10.2023 -
1 INDU 1901016021 2014 09.10.2023 -
-
12.2 Financial Data Management
-
This chapter contains issues that might have a negative impact on data volume and total cost of ownership.
-
12.2.1 G/L Accounts with Open Items older than 10 Years old
-
Issue Description: There is a high number of open items within G/L accounts that are more than 10 years old.
Impact on Business:
Documents that contain open items that are never cleared can never be archived. Documents that cannot be archived
increase the data volume and the Total
Costs of Ownership.
Examples of identified accounts in the old fiscal years:
Company Codeÿ G/L Account Year Number of Entries
INDU 0019000107 2011 1971
INDU 0019000107 2012 2418
INDU 0019000104 2012 1734
INDU 0019000105 2012 1699
INDU 0019000106 2012 1240
INDU 0019000107 2013 2900
INDU 0019000105 2013 2091
INDU 0019000104 2013 1632
INDU 0019000106 2013 1313
INDU 0019000114 2013 1197
Recommendation: Clear as many open items as possible.
-
12.2.2 Customers with Open Items older than 10 Years old

-
Issue Description: There is a high number of open items within customer accounts that are more than 10 years old.
Impact on Business:
increase the data volume and the Total
Costs of Ownership.
Examples of identified customer accounts in the old fiscal years:
Company Codeÿ Customer Year Number of Entries
INDU 0000082321 2011 61
INDU 0000082754 2011 35
QUEN 0000172008 2011 12
QUEN 0000143017 2011 8
INDU 0000062921 2011 2
QUEN 0000173021 2011 1
QUEN 0000193007 2011 1
QUEN 0000171022 2011 1
QUEN 0000172045 2011 1
-
12.2.3 Vendors with Open Items older than 10 Years old
-
Issue Description: There is a high number of open items within vendor accounts that are more than 10 years old.
Impact on Business:
increase the data volume and the Total Costs of Ownership.
Examples of identified vendor accounts in the old fiscal years:
Company Codeÿ Vendors Year Number of Entries
INDU 0001000056 2011 2
INDU 0001000005 2011 2
INDU 0001000055 2011 1
QUEN 0001000063 2011 1
INDU 0001000028 2011 1
INDU 0001000015 2011 1
INDU 0001000047 2011 1
INDU 0001000049 2011 1
INDU 0001000058 2011 1
INDU 0001000056 2012 1
-
12.3 Reconciliation of ECC Systems (prior to S/4HANA)
-
This section displays data from the reconciliation checks in the area of Finance. For ECC customers we provide checks in
the area of General Ledger and Asset Accounting.
-
12.3.1 Reconciliation for Asset Accounting
-
The data displayed in this chapter is a result of execution of the FIN_AA_CORR_RECON transaction. It contains various
consistency checks of the Asset Accounting application. Identified inconsistencies might have a negative impact on your
daily business and digital transformation projects. It is especially crucial to analyze and resolve listed issues in detail prior

to SAP S/4HANA conversion. Please note that, when estimating the resolution effort of the identified inconsistencies, you
should refer to the number of different error types, but not the total number of errors.
This transaction had not been executed or not fully executed. Please make sure to fully scan your system for possible
further inconsistencies in your financial data. For more information, refer to SAP Note 3038014 .
Prerequisites
-
Note Description
2896400 Reconciliation of Asset Accounting Inconsistencies in ECC prior to S/4HANA Conversion
3026403 FIN_AA_CORR_DISPLAY: false positive error message FIN_AA_RECON 764
3075335 DDIC objects for note 2896400 - Reconciliation of Asset Accounting Inconsistencies in ECC prior to S/4HANA
Conversion
3002026 Recon. of AA in ECC prior to S/4HANA conv.: asset numbers in multiple company code
-
12.3.2 Reconciliation for General Ledger
-
The data displayed in this chapter is a result of execution of the FIN_CORR_RECONCILE transaction. This reconciliation
check is the main source of the financial data quality analysis. It contains various consistency checks of the General Ledger
application. Identified inconsistencies might have a negative impact on your daily business and digital transformation
projects. It is especially crucial to analyze and resolve listed issues in detail prior to SAP S/4HANA conversion. Please note
that, when estimating the resolution effort of the identified inconsistencies, you should refer to the number of different error
types, but not the total number of errors.
In your case, this transaction had been executed, but the system was not scanned completely. Please make sure to fully
scan your system for possible further inconsistencies in your financial data. For more information, refer to SAP Note
2755360 .
Please see the coverage and the error counter of the executed checks in the tables below. Refer to SAP Note 2714344 for
more information about the identified error types.
Note Description
2755360 Reconciliation prior to S/4HANA Conversion
2906603 Financial Data Quality: Central Preparation Note
Please note that the displayed results in the following tables concern the Run IDs mentioned above.

13 Data Volume Management (DVM)

-
Data relevant for Data Volume Management was collected on system SPP and stored in the SDCCN download. If you gave
your consent, this data has been sent to SAP for further analysis. After the analysis has finished, you can find the analysis
result in SAP Support Launchpad via the link shown in the "Link to SAP Support Launchpad" column in the table below.
Note: For more information about DVM cloud-based service delivery, see Knowledge Base Article 2716655 .
Link to SAP Support Launchpad
https://launchpad.support.sap.com/#/dataoverview
Confidential Data Volume Management (DVM) 36/120

14 SAP HANA Database HPP

-
We have checked your SAP HANA environment and found some issues that might
have a negative impact on your overall system stability. Review the report carefully
and implement our recommendations.
Rating Check
SAP HANA Stability and Alerts
SAP HANA Database Configuration
SAP HANA Resource Consumption
SAP HANA Workload and Performance
Size and Growth
Administration
-
14.1 Overview
-
The tables below provide an overview of your current SAP HANA database configuration.
DB Version / Start Time
-
Current SAP HANA DB Version Build Branch Start Time
2.00.066.00 fa/hana2sp06 25.03.2023 15:06:46
Technical Instances
-
Host Database System Instance Active Daemon Start Time Time Nameser Indexserv
Name ID Zone ver Role er Role
srvprdpar1 HPP HPP 10 yes yes 2023-02-2 8 -04 MASTER MASTER
11:14:14.8 36
Hardware Settings - General Data

-
Host Physical Hostname Manufacturer Model
srvprdpar1 srvprdpar1 VMware, Inc. VMware7,1
Hardware Settings - CPU and Memory Data

-
Host CPU Type CPU CPU Cores Threads Sockets NUMA Physical Allocatio Swap
Frequency Nodes Memory n Limit Space
[GB] [GB] [GB]
srvprdpar1 Intel(R) 2.194 24 24 2 1 503,4 483,7 80,0
Xeon(R)
Gold
6338N
CPU @
2.20GHz
Operating System Details

-
Host Operating System PPMS Operating Operating System NOFILES Limit OPEN_FILE Limit
Name System Version Kernel
srvprdpar1 LINUX_X86_64 SUSE Linux 5.3.18-150200.24. 1.048.576 52.778.392
Enterprise Server 139-default
15 SP2
Confidential SAP HANA Database HPP 37/120
HANA Feature Usage
-
Usage Installed / used Additional data SAP Note
Multitenant Database Containers (MDC) Yes System ID: HPP 2101244
Dynamic Tiering No - 2140959
Enterprise Performance Management Add-On (EPM MDS) No - 2456225
Embedded liveCache No - 2593571
Streaming Server No - -
Advanced Function Libraries No - -
XS Advanced No - -
Embedded Statisticsserver active Yes - 2147247
System Replication No - 1999880
Smart Data Access (SDA) No - 2180119
Smart Data Integration (SDI) No - 2400022
Smart Data Streaming (SDS) No - 2367236
Persistent Memory No - 2700084
Fast Restart Option No - 2700084
Data Aging No - 2416490
Extension Node No - 2741690
Workload Classes Yes - 2222250
Native Storage Extension (NSE) No - 2775588
Multi Dimensional Expressions (MDX) No - -
Multi Dimensional Services (MDS) No - 2670064
HANA Update Information

-
Date Version
28.02.2023 2.00.066.00.1671096120
-
14.2 SAP HANA Stability and Alerts
-
14.2.1 SAP HANA Alerts
-
SAP HANA alerts have been issued for the monitored timeframe.
SAP HANA collects system information periodically and issues alerts of different priority levels according to predefined
thresholds. These alerts can be used to monitor the performance and stability of the SAP HANA database. Possible alert
priorities are:
1 – Information
2 – Low
3 – Medium
4 – High
5 – Statistics Server Alert
The following "Alerts" table shows SAP HANA alerts that reached at least medium priority during the monitored timeframe.
It also shows how often an alert was created and the highest priority for this particular alert.
The "Recommendations" table lists recommendations for the alerts found and refers to SAP KBA Notes if available. Further
details and recommendations for SAP HANA alerts are available in the relevant sections of the report.
Alerts
-
Alert ID Alert No. of Occurrences Highest Rating
37 Determines the age of the most recent successful data backup. 5 4
130 Determines if there are any own or chain certificates that will expire 7 3
soon or have already expired.
2 Determines what percentage of each disk containing data, log, and trace 2 3
files is used. This includes space used by non-SAP HANA files.
Recommendations
-
Alert ID General Recommendation KBA
2 Investigate disk usage of processes. Increase disk space, for example by shrinking volumes, deleting 1870858
diagnosis files, or adding additional storage. See SAP Note 1900643. For details please refer to the
chapter "Size and Growth".
37 Perform a data backup as soon as possible. See SAP Note 1900730. For details please refer to the 1900730
chapter "Administration".
130 Replace the certificates. -
Recommendation: Monitor SAP HANA alerts in the system closely to get an overview of the SAP HANA system
status. React to warnings and problems visible in the alerts in due time. If you require support, open a message on
component HAN-DB*.
For details, refer to the SAP HANA Administration Guide and to the SAP Note 2445867 How-To: Interpreting and
Resolving SAP HANA Alerts .
-
14.2.2 SAP HANA Service Restarts
-
No critical issues with SAP HANA service restarts were detected.
We did not find critical issues with SAP HANA service restarts.
-
14.2.3 SAP HANA DB Availability
-
The SAP HANA DB availability was based on the availability of the index server as logged in the daemon trace file.
No critical problems occurred regarding the availability of SAP HANA services.
-
14.3 SAP HANA Database Configuration
-
14.3.1 Parameter Recommendation
-
Check parameter settings
Some parameters are not set as recommended, or there are parameters deviating from default values.
This table highlights the parameters that were checked with regard to their impact on system performance and stability.
Important SAP HANA Parameters
-
Location Parameter Layername Current Value Recommended Value Rating SAP Note
global.ini log_mode HOST - overwrite normal -
[persistence] srvprdpar1
indexserver.ini smart_merge_d DEFAULT (MMS<1000 or (DMS>1000 or 2057046
[mergedog] ecision_func DMS>1000 or DRC>0.1*MRC or
DRC>0.1*MRC DMR>0.1*MRC )
or
DMR>0.1*MRC )
Recommendation: Set the SAP HANA parameters to the recommended value in the table.
Be aware that for a proper tenant DB parameter setting, the parameters configured on the system DB side must also be
double-checked. Otherwise, critical parameters can be set in the system DB that appear as default values on the tenant
side. Default values are only reported by the parameter check if an explicit recommendation exists, therefore, critical
settings can be missed by focusing only on the tenant DB parameter check.
-
14.3.2 SAP HANA Workload Management
-
SAP HANA workload parameters are set in the recommended range.
Workload management in SAP HANA allows you to balance and manage all workload types for optimal throughput and
response times. The available workload management parameters limit resource consumption (e.g. CPU, threads, memory)
for certain operations. The recommended values depend on available memory resources and on the number of CPU
threads of the database server (also referred to as number of logical CPUs). For general information, refer to SAP Note
2222250 (FAQ: SAP HANA Workload Management).
-
14.3.3 Disk Configuration
-
There are no disk configuration issues.
Disk ID Device ID File system Host Path Usage

2 774998 xfs srvprdpar1 /hana/data/ DATA
3 801243 xfs srvprdpar1 /backup/BCK/ DATA_BACKUP
4 780820 xfs srvprdpar1 /hana/log/ LOG
5 801243 xfs srvprdpar1 /backup/ARC/ LOG_BACKUP
6 302026 xfs srvprdpar1 /usr/sap/HPP/HDB10/srvprdpar1/ TRACE
1 302026 xfs srvprdpar1 /usr/sap/HPP/HDB10/backup/log/ CATALOG_BACKUP
There are no disk configuration issues. Data and log data is stored on separate physical devices.
-
14.4 Size and Growth
-
Monitoring the size and growth of the HANA database is crucial for system stability and performance. In terms of stability,
the growth on disk is shown. In terms of performance, the size of row and column tables as well as the size of delta areas
in column tables are analyzed.
-
14.4.1 Disk Usage
-
Percentage of free disk space > 20%
The table below shows the disk occupancy with respect to the partitions and their usage types. If the percentage of free
disk space falls below 10%, an intermediate action has to be performed. Otherwise, there is a risk of standstill in the SAP
HANA database.
Disk Space
-
Host Available Disk Space Used Disk Percentage of Usage Types File system Rating
[GB] Space [GB] free Disk Space
srvprdpar1 499,75 241,11 51,8 DATA xfs
srvprdpar1 199,90 41,80 79,1 LOG xfs
srvprdpar1 599,70 284,71 52,5 DATA_BACKU xfs
P+LOG_BACKUP
srvprdpar1 499,75 16,68 96,7 CATALOG_BA xfs
CKUP+TRACE
The graph shows the history of disk space usage.

-
14.4.2 Database Growth
-
The graph shows the database size and growth based on the size of data volumes.
Total Size: Amount of data allocated by SAP HANA database on data volumes.
Used Size: Amount of used data by SAP HANA database on data volumes.
To access the database growth chart in SAP EarlyWatch Alert Workspace, click here .
-
14.4.3 Tables and Indexes
-
The table below displays the number of column and row tables together with their indexes.
Tables and Indexes
-
Objects Number
Column Tables 111.093
Indexes of Colum Tables 116.015
Row Tables 1.296
Objects Number
Indexes of Row Tables 788
-
14.4.4 Size of Database Schemas
-
The following table lists the size of schemas in the SAP HANA database.
Size of HANA schemas
-
Host Schema name Size in MB Store type
srvprdpar1 SAPABAP1 55.960 Column store
srvprdpar1 _SYS_REPO 957 Column store
srvprdpar1 _SYS_STATISTICS 356 Column store
srvprdpar1 _SYS_RT 4 Column store
srvprdpar1 _SYS_BI 2 Column store
srvprdpar1 _SYS_TASK 2 Column store
srvprdpar1 _SYS_DI 1 Column store
srvprdpar1 _SYS_XS 1 Column store
srvprdpar1 SAP_XS_LM 1 Column store
srvprdpar1 SAP_XS_LM_PE 1 Column store
srvprdpar1 SAPABAP1 1.290 Row store
srvprdpar1 SYS 702 Row store
srvprdpar1 _SYS_STATISTICS 4 Row store
-
14.4.5 SAP HANA Row Store
-
14.4.5.1 Row Store Size
-
The allocated row store size is below the technical limit.
The table below shows the size of the SAP HANA row store. The row store contains mainly SAP Basis and application
statistics tables. The rating indicates whether the technical size limit will be reached in the near future.
The size of the row store generally has a direct impact on the start-up time of the SAP HANA database. This is relevant for
system start-up and for recovery. We recommend that you keep the row store at an optimum size by performing
housekeeping for large Basis tables (SAP Note 2388483) and, where feasible, moving large application tables from row
store to column store.
Row Store Size (MB)
-
Host Port Allocated Size (MB) Rating
srvprdpar1 31003 2.560
-
14.4.5.2 Row Store Fragmentation
-
The fragmentation of the row store is not critical.
The following table shows the allocated size and free page ratio (fragmentation) of the row store. The term 'fragmentation'
refers to unused space in the SAP HANA row store that cannot be used for technical reasons. High fragmentation can
cause performance issues and longer backup times. Row store reorganization is generally recommended if the allocated
row store size is larger than 10 GB and the free page ratio is greater than 30%.
Row Store Size and Fragmentation
-
Host Port Allocated Size [MB] Free Size [MB] Free Page Ratio [%] Row Store Reorganization
Recommended
srvprdpar1 31003 2.560 1.178 46 No
-
14.4.5.3 Largest Row Store Tables
-
The table lists the largest tables according to total disk size. The size of the memory and the number and type of LoBs are
also shown. The LOBs are marked with either "H" (Hybrid) or "M" (Memory) and the number of the existing LoB columns.
Schema Table Name Total Disk Size in Max Size in Nr. of LOB Size LOB Details
Name Size (MB) Memory Memory Records (MB)
(MB) (MB)
SAPABAP1 DDNTF 2.668 279 330 1.156.629 2.338 H1
SAPABAP1 FPLAYOUTT 2.494 1 1 9.604 2.493 H2
SAPABAP1 FPCONTEXT 785 1 1 5.255 784 H1
SAPABAP1 ENHHEADER 567 3 3 24.758 564 H1
SYS CS_COLUM 436 402 436 1.489.853 0 0
NS_
SAPABAP1 TST03 389 3 4 39.944 385 H1
SAPABAP1 LTEX 333 305 333 109.610 0 0
SAPABAP1 ENHSPOTH 134 2 2 12.898 132 H1
EADER
SAPABAP1 TBTCO 108 94 108 267.168 0 0
SAPABAP1 TBTCP 94 85 94 267.189 0 0
For large SAP Basis tables, remove obsolete data regularly according to SAP Note 2388483 .
-
14.4.6 SAP HANA Column Store
-
14.4.6.1 Largest Column Tables (Size)
-
The table lists the largest tables according to total disk size. The size of the memory and the number and type of LoBs are
also shown. The LOBs are marked with either "H" (Hybrid) or "M" (Memory) and the number of the existing LoB columns.
Schema Table Name Nr. of Total Disk Size in Max. Size in LOB Size LOB Details
Name Partitions Size (MB) Memory Memory (MB)
(MB) (MB)
SAPABAP1 SOFFCONT1 1 53.532 170 170 53.363 H1
SAPABAP1 REPOLOAD 1 23.527 95 95 23.432 H2
SAPABAP1 REPOSRC 1 8.669 1.542 1.542 7.123 H1
SAPABAP1 ECTD_XML_ 1 5.321 5 8 5.313 H1
STR
SAPABAP1 WBCROSSG 1 3.757 1.649 3.770 0 0
T
SAPABAP1 ACCTCR 1 2.786 2.829 2.829 0 0
SAPABAP1 FAGLFLEXA 1 2.272 2.411 2.411 0 0
SAPABAP1 CDPOS 1 2.209 2.204 2.204 0 0
_SYS_REPO ACTIVE_OBJ 1 2.186 952 952 1.289 H2
ECT
SAPABAP1 DOKTL 1 2.098 2.086 2.086 0 0
For large SAP Basis tables, remove obsolete data regularly according to SAP Note 2388483 .
-
14.4.6.2 Largest Non-partitioned Column Tables (Records)
-
The number of records in column-based table partitions is not critical.
The table below shows the largest non-partitioned column tables in terms of the number of records.
Largest Non-partitioned Column Tables According To Records
-
Schema Name Table Name Records (Total) Rating
SAPABAP1 WBCROSSGT 81.065.693
SAPABAP1 ACCTCR 78.574.108
SAPABAP1 D010TAB 66.305.367
Schema Name Table Name Records (Total) Rating
SAPABAP1 MLCR 44.619.123
SAPABAP1 DOKTL 43.596.132
SAPABAP1 BSEG 38.143.697
SAPABAP1 CDPOS 38.091.381
SAPABAP1 CMFP 37.686.405
SAPABAP1 FAGLFLEXA 37.566.422
SAPABAP1 BSIS 30.709.685
The table partitions can handle the number of the records.
-
14.5 SAP HANA Resource Consumption
-
The following table shows an overview of the resource consumption of the SAP HANA instances in the monitored
timeframe.
HANA Instances Overview
-
HANA Instance Role CPU Usage Memory Usage of Memory Memory Memory
HANA server Usage of SAP Allocation of Consumption
HANA Tables Indexserver
Instance
srvprdpar1_HP MASTER
P_10
The SAP HANA hardware resources are sufficient for the current workload.
-
14.5.1 Memory Utilization Overview for SAP HANA Instances
-
The following table shows the memory usage of the SAP HANA database. The table displays weekly average values for
the SAP HANA memory areas:
'Memory usage of the HANA database' corresponds to the memory used by the entire SAP HANA database (comparable
to 'DB used memory' in SAP HANA studio).
'Global allocation limit' is the limit for the overall memory usage of the SAP HANA instance defined by the
global_allocation_limit parameter.
'Row store size' shows the average size of row store tables in SAP HANA memory.
'Column store size' shows the average size of column store tables in SAP HANA memory.
The main SAP HANA workload is handled by the SAP HANA index server. The weekly average of the hourly maximum
values of the 'Memory usage of the index server' and the 'Effective allocation limit' of the index server are listed.
More detailed information about memory shortage on an SAP HANA instance is provided in the sections below.
Avg. memory usage by SAP HANA Instances
-
HANA Memory usage Global Row store size Column store Memory usage Effective
instance of SAP HANA allocation limit [GB] size [GB] of indexserver allocation limit
[GB] [GB] [GB] of indexserver
[GB]
srvprdpar1_HP 181 484 4 54 175 477
P_10
-
14.5.2 SAP HANA Instance srvprdpar1_HPP_10
-
14.5.2.1 CPU Usage of SAP HANA Server
-
No CPU bottlenecks were detected.
To access the CPU usage charts in SAP EarlyWatch Alert Workspace, click here .
The graphics below show the average and maximum CPU consumption per hour.

The data is obtained from the statistics tables of the SAP HANA database. If the average CPU consumption exceeds 75%,
a YELLOW rating is assigned. If it exceeds the threshold of 90%, a RED rating is assigned.
We did not find any critical issues in this area.

-
14.5.2.2 Memory Usage of SAP HANA Server
-
No memory bottlenecks were detected.
To access the memory usage chart in SAP EarlyWatch Alert Workspace, click here .
The following graph shows the physical memory usage during the monitored timeframe. The average and maximum
memory used by SAP HANA (and possibly other processes) is compared with the available physical memory of the SAP
HANA server.

No critical issues were detected in this area.

-
14.5.2.3 Memory Usage of SAP HANA Instance
-
The memory consumption of the SAP HANA instance is not critical.
The following graph shows the memory usage of the SAP HANA database instance during the monitored timeframe. The
memory used by SAP HANA on the SAP HANA host is compared with the global allocation limit of the SAP HANA
instance.
If the "Used SAP HANA Instance Memory" approaches the "Global Allocation Limit", data has to be unloaded from SAP
HANA memory. This may affect the overall performance and stability of the SAP HANA database.
The SAP HANA memory usage should not exceed 90% of the "Global Allocation Limit".
The memory consumption of the SAP HANA instance is not critical.

-
14.5.2.4 Memory Allocation of Tables
-
The memory consumption of tables is below any critical threshold.
This graphic shows the average memory consumption for storing row and column tables, and the memory available for
temporary calculations and other operations.
From a SAP HANA sizing perspective, it is recommended that the memory usage for SAP HANA tables remains below
50% of the global allocation limit.
If the memory usage for SAP HANA tables reaches 70% of the global allocation limit, the remaining memory resources for
temporary calculations may be too small.
-
14.5.2.5 Memory Consumption of Indexserver
-
The memory consumption of the index server was not critical.
The index server is the most critical component with regard to SAP HANA memory consumption and must be monitored
regularly. If the memory consumption of the index server approaches the effective allocation limit, table unloads or even
out-of-memory dumps may occur.
The following graph shows the memory consumption of the index server in relation to its effective allocation limit.
The memory consumption of the index server was not critical.

-
14.5.2.6 Main Memory Areas of SAP HANA

-
The following graph shows the top 5 consumers of SAP HANA memory. Additional allocators are summed up in the
"Others" category. Refer to SAP Note 1999997 - FAQ: SAP HANA Memory for a more detailed explanation of SAP HANA
memory allocation.
-
14.6 SAP HANA Workload and Performance
-
14.6.1 SAP HANA Workload
-
The table shows the number of SQL requests executed per second and per node (maximum 23 nodes) in your SAP HANA
system in the monitored timeframe.
-
14.6.2 SAP HANA Response Times
-
The following graph shows the execution times of the SAP HANA system in the monitored timeframe aggregated from all
SAP HANA nodes. The displayed "Execution Time" is the hourly average execution time obtained by the historized SQL
Plan Cache.
Since the "Execution Time" in the SQL Plan Cache does not contain all response time parts, we also show in the graph
below the "Sum Execution Time", which is the sum of the "Execution Time" plus preparation time and table load time. For
more information, see SAP Note 2000002 .
The following graph shows the response time distribution of the SAP HANA system. The data is collected from the history
data of the SQL Plan Cache.
Explanation of the SAP HANA response time shares:

- Preparation time – time share for plan preparation
- Open time – time share for cursor open and select
- Fetch time – time share for cursor fetch
- Lock wait time - lock wait time share for the plan
- Table load time – time share for loading tables during plan preparation (available as of SAP HANA rev. 50)
-
14.6.3 Delta Merges
-
14.6.3.1 Column Tables with Largest Delta Stores
-
No problems with the delta size of column store tables were detected.
The separation into main and delta storage allows high compression and high write performance at the same time. Write
operations are performed on the delta store and changes are transferred from the delta store to the main store
asynchronously during delta merge.
The column store automatically performs a delta merge according to several technical limits that are defined by
parameters.
If applications require more direct control over the merge process, the smart merge function can be used for certain tables
(for example, BW prevents delta merges during data loading for performance reasons).
Largest Column Tables in terms of Delta size
-
Schema Table Partition ID Memorysiz Memorysiz Records in Sum of Days since Auto
Name Name e in Main e in Delta Delta Store Records last Merge Merge On
Store [MB] Store [MB]
SAPABAP1 CMFP 0 956,5 34,3 165.070 37.686.405 7 TRUE
SAPABAP1 CDPOS 0 2.189,1 14,9 58.591 38.091.342 6 TRUE
SAPABAP1 KONV 0 238,2 7,5 36.095 5.319.542 4 TRUE
SAPABAP1 BSEG 0 1.972,6 6,3 5.210 38.143.533 1 TRUE
_SYS_STA HOST_SQL 0 70,3 6,3 8.354 471.735 1 TRUE
TISTICS _PLAN_CA
CHE_BASE
SAPABAP1 COSS 0 208,2 5,1 5.567 1.962.798 7 TRUE
SAPABAP1 COSB 0 0,6 4,9 5.510 2.442.208 6 TRUE
SAPABAP1 FAGLFLEX 0 84,2 4,6 5.147 382.823 3 TRUE
T
SAPABAP1 LIPS 0 33,3 4,2 1.157 451.507 3 TRUE
SAPABAP1 VBAP 0 23,0 3,8 804 344.007 2 TRUE
-
14.6.3.2 Delta Merge Statistics
-
The SAP HANA database column store uses efficient compression algorithms to keep relevant application data in memory.
Write operations on the compressed data are costly since they require the storage structure to be reorganized and the
compression to be recalculated. Therefore, write operations in the column store do not directly modify the compressed data
structure in the "main storage".
Instead, all changes are first written into a separate data structure called "delta storage" and synchronized with the main
storage at a later point in time. This synchronization operation is called a delta merge.
Performance issues may occur in SAP HANA if there is a large amount of data in the delta storage, because read times
from delta storage are considerably slower than reads from main storage.
In addition, the merge operation on a large data volume may cause bottleneck situations, since the data to be merged is
held in memory twice during the merge operation.
The following graph shows the number of successful and failed delta merges in the monitored timeframe.

The following graph shows the delta merge volume from all merge types and the average delta merge time per record in
the monitored timeframe:
Note: High merge duration can be a result of a high number of records to be merged or of a high-load situation in the
system.
-
14.7 Administration
-
14.7.1 Diagnosis Files
-
The number and size of diagnosis files is uncritical.
During operation, the SAP HANA database service writes messages and information to log files in its trace directory. The
system administrator should check these files regularly and react to error messages accordingly. A large number of files
may be generated, which can take up a lot of disk space and impair performance. The following table shows the number of
files contained in the trace directory.

Diagnosis Files
-
Server Measured Time Period Type Number of Files Total Size in MB
srvprdpar1 Weekly Log 1 4,03
srvprdpar1 Weekly Trace 27 224,35
srvprdpar1 Unlimited TOTAL 53 353,05
We did not detect any issues with the number or size of these files.
Nevertheless, we recommend that you check the content of the trace folder in the SAP HANA database installation
directory on a regular basis and delete any files that are no longer required.
-
14.7.2 Backup and Recovery
-
Severe issues for operating or administration in terms of backup/recovery have been detected.
-
14.7.2.1 Log Backup
-
Date Weekday Successful Log Backups Unsuccessful Log Backups
06.10.2023 Friday 2 0
The log backup operating appears to be critical. Frequent log backups could not be detected.
Recommendation: SAP HANA database logs should be backed up automatically by setting SAP HANA parameters
correctly. For more information, see SAP Note 1642148 (FAQ: SAP HANA Database Backup & Recovery).
-
14.7.2.2 Data Backup
-
Date Weekday Successful Data Backups Unsuccessful Data Backups
06.10.2023 Friday 2 1
The data backup frequency or operating were not optimal within the monitoring period.
Recommendation: A successful data backup should be performed after each working day. For more information,
see SAP Note 1642148 (FAQ: SAP HANA Database Backup & Recovery).
-
14.7.2.3 Number of Log Segments
-
This graph shows the number of log segments residing on your log volume.

We found no issues related to log segments.
-
14.7.3 Global Consistency Check Run
-
Global consistency check runs at least once per month.
The tables below show your setup of the consistency check runs. We differentiate between consistency check runs
executed on all levels (CHECK_TABLE_CONSISTENCY(CHECK,'NULL','NULL')) and consistency check runs executed on
table level (CHECK_TABLE_CONSISTENCY(CHECK,<SCHEMA_NAME>,<TABLE_NAME>)) or executed by the statistics
server.
Consistency Check Runs on all Levels with Action 'CHECK'
-
Number of successful Executions Last Start Date
1 06.10.2023
Consistency Check Runs on Table Level with Action 'CHECK'

-
Number of checked Tables Number of not verified Tables Last Start Date
0 32543 -
Table Consistency Check by Statisticsserver

-
Action Time since last Run
check_delta_log, check_variable_part_sanity, check_data_container, 33 Days, 4 Hours
check_variable_part_double_reference_global, check_partitioning, check_replication,
check_table_container_no_load
The setup is in agreement with SAP's recommendation.
-
14.7.4 License Information
-
Your license is permanent and valid.
The following table shows information about the validity of your license. The license should be permanent and valid.
License Information
-
System ID Installation Number Expiration Date Permanent Valid Product Name Product Limit
HPP 0020610116 - TRUE TRUE SAP-HANA 160
-
14.7.5 Statisticsserver and Monitoring
-
No issues with the statistics server were detected.
The table below shows KPIs relevant for monitoring stability with the embedded statistics server.
KPI Current value Rating
Status of the embedded Statisticsserver Okay
Alerts in the Statisticsserver are not scheduled in the expected timeframe. 0
Number of tables not located on the master server 0
Number of disabled alert collectors 0
Number of disabled statistic collectors 0
Collector_Global_Table_Persistence_S tatistics idle Idle
Number of collectors with retention times < 42 days 0
High number of unprocessed e-Mails 109
Status of Collector HOST_CS_UNLOADS Inactive
Number of relevant inactive actions 0
Number of actions with unknown state 0
Number of Statisticsserver worker threads 5

KPI Current value Rating
Historic thread samples save interval (s) 600
History of M_RECORD_LOCKS collected no
-
14.8 Important SAP Notes for SAP HANA
-
Important information is available in the SAP Notes below.
The following tables list important SAP Notes for SAP HANA.
SAP Notes for SAP HANA
-
1514967 SAP HANA: Central Note
2380229 SAP HANA Platform 2.0 - Central Note
2091951 Best Practice: SAP HANA Database Backup & Restore
2021789 SAP HANA Revision and Maintenance Strategy
2000003 FAQ: SAP HANA
2600030 Parameter Recommendations in SAP HANA Environments
1911180 HANA EarlyWatch Alerts (EWA) Issues
1592925 SAP HANA Database service connections
1642148 FAQ: SAP HANA Database Backup & Recovery
1664432 DBA Cockpit: SAP HANA database as remote database
1681092 Multiple SAP HANA databases on one appliance
1661202 Support for multiple applications on SAP HANA
1650394 SAP HANA DB: Partitioning and Distribution of Large Tables
1953429 SAP HANA and SAP NetWeaver AS ABAP on one Server
1761546 SAP ERP powered by SAP HANA - Optimizations
1872170 Suite on HANA and S/4 HANA sizing report
1794297 Secondary Indexes for the business suite on HANA
SAP Notes for operating system

-
2684254 SAP HANA DB: Recommended OS settings for SLES 15 / SLES for SAP Applications 15

15 SAP HANA SQL Statements in HPP

-
This section provides an overview of the "most expensive SQL statements". When possible, a recommendation is provided.
A more detailed analysis of the SQL statements (including the possibility to choose different time windows) is supported by
the "Self-Service SQL Statement Tuning" (see SAP Note 1601951 ). For general information on dealing with expensive
SQL statements in SAP HANA, see SAP Note 2000002 .
-
15.1 Data Quality
-
A download-based SQL statement analysis can be performed.
The following table provides information about the data in the SDCC download. For details, see SAP Note 2344673 .
Observation Comment Rating
Version of ST-PI function module: 39 This is the most recent version
-
15.2 Top Statements (Elapsed Time)
-
This section shows the top non-internal statements according to "Total Elapsed Time". The "Total Elapsed Time" is the
sum of the "Total Execution Time" and the "Total Preparation Time" from the SQL PLAN CACHE. It has a direct impact on
the response time of the application calling the statement.
See the following table for details of the selection:
Database Start 25.03.2023 -- 15:06:46
Data Collection 09.10.2023 -- 15:13:13
Analysis Type Analysis of Plan Cache
Data Source HOST_SQL_PLAN_CACHE
Begin of Time Interval 01.10.2023 -- 23:06:59
End of Time Interval 09.10.2023 -- 00:07:07
The selected statements - identified by their "Statement Hash" - are listed in the following table. Further details of these
statements can be found in the subsections.
Statement Hash Total Elapsed Number of Time / Execution Records / Time / Record
Time [s] Executions [us] Execution [us]
59a8aa9b59f3b52 2.062,0 10.037.544 205,4 1,0 205,5
78a05aa583b7d34
6b
33af180cf0874a5f 1.929,6 19.351.069 99,7 0,0 13.471,1
432fe90fc0e76480
093df47208b3914 1.325,6 10.584.510 125,2 0,2 572,2
f89da8424df29a7
09
ce7a5b93a546507 1.125,1 10.135.045 111,0 1,0 111,0
16147164130ecd5
2c
eb54f7641ea40ed 1.001,4 1 1.001.419.250,0 0,0 0,0
df456604ecc100f
46
-
15.2.1 SQL Statement 59a8aa9b59f3b5278a05aa583b7d346 b
-
SELECT
*
FROM
"BSEG"
Confidential SAP HANA SQL Statements in 55/120
HPP
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BELNR" = ? AND "GJAHR" = ? AND "BUZEI" = ? LIMIT 1 WITH
RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
Contribution to Total CPU Load [%] 1,55
Contribution to Total Execution Time [%] 3,38
Maximal CPU Consumption per Hour [%] ( 05.10.2023 between 12:00 and 13:00 ) 0,58
Note: The statement as identified by its statement hash can also be found in other sections of this report:
Other Sections Dealing with this Statement
SAP HANA SQL Statements in HPP -> Top Statements (Thread Samples)
SAP HANA SQL Statements in HPP -> Statements on Top Scanned Table
SAP HANA SQL Statements in HPP -> Top Statements (CPU Peak Hour)
-
15.2.1.1 Analysis of Where Clause
-
Table Field Operator SCANNED RECORD COUNT INDEX LOOKUP COUNT
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG BUZEI = 5.150.245.884 1
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
15.2.1.2 Time Consumption
-
The following table gives an overview of the time consumption of the analyzed SQL statement.
Activity Total Time [s] Average Time [us] Minimal Time [us] Maximal Time [us]
TOTAL EXECUTION 2.062 205 43 37.054
PREPARATION 0 0 - -
LOCK DURATION 0 0 - -
-
15.2.1.3 Statement History (Thread Sample 'Running')
-
The following graph shows the number of observed thread samples (in state "running") related to this SQL statement
together with the contribution of those samples to all thread samples (in state "running") active in the system.

HPP
-
15.2.1.4 Correlation with Index Server Rescource Consumption
-
The distribution of thread samples with the status "Running" correlates strongly with the overall CPU or memory
consumption of the system. Such a correlation indicates that this statement might be responsible for peaks in the memory
or CPU consumption.
Distiribution Correlation Coefficient Comment
CPU consumption index server(s) - Threads (running) from this SQL 0,64 strong correlation
statement
Memory consumption index server(s) - Threads (running) from this -0,21 weak negative correlation
SQL Statement
-
15.2.1.5 Tables
-
In the following, the tables involved in the SQL statement are listed (maximum of 20), sorted by the number of records.
Table Name Schema Name Table Type Partition Type Number of Records Host
BSEG SAPABAP1 COLUMN Table not partitioned 38.143.660 srvprdpar1
-
15.2.1.6 Origin of SQL Statement
-
The following table shows details of the applications responsible for the statement. This information is based on the
information provided by SAP HANA in the "application source" connected to the statement in the "thread samples" or the
list of "prepared" or "active" statements, and is not necessarily complete.
SID Report Line Last Changed on: SAP Coding Application Component Description
SPP LZITEM_CTASUBU01 106 12.05.2016 - FI Gestión financiera
-
15.2.2 SQL Statement 33af180cf0874a5f432fe90fc0e7648 0
-
SELECT
*
FROM
"NAST"
WHERE
"MANDT" = ? AND "OBJKY" = ? AND "KAPPL" = ? AND "KSCHL" = ? AND "NACHA" = N'1' AND "VSTAT" <= ? LIMIT 1
HPP
WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
-
-
NAST KAPPL = 96.239.553 3.082
NAST KSCHL = 87.861.629 2
NAST MANDT = 1.442 1
NAST NACHA = 0 0
NAST OBJKY = 126.736.979 1
NAST VSTAT <= 2.367.144 0
-
-
PREPARATION 0 0 - -
-
-
-
HPP

-
The distribution of thread samples with the status "Running" correlates with the overall CPU or memory consumption of the
system. Such a correlation indicates that this statement might be responsible for peaks in the memory or CPU
consumption.
CPU consumption index server(s) - Threads (running) from this SQL 0,30 weak correlation
statement
SQL Statement
-
15.2.2.5 Tables
-
NAST SAPABAP1 COLUMN Table not partitioned 639.574 srvprdpar1
-
-
SID Transaction / Report Line Last Changed on: SAP Coding Application Description
Jobaname Component
SPP IDCP IDPRCNINV 2.095 24.03.2023 FI-LOC-SD-CN Ventas y
OICE distribución
para China
SPP IDPRCNINVOICE IDPRCNINV 2.095 24.03.2023 FI-LOC-SD-CN Ventas y
OICE distribución
para China
-
15.2.3 SQL Statement 093df47208b3914f89da8424df29a70 9
-
SELECT
"KUNNR"
FROM
"BSEG"
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BELNR" = ? AND "GJAHR" = ? AND "KUNNR" <> N'' LIMIT 1 WITH
Statement Impact
-
Indicator Value
-
HPP
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG GJAHR = 5.222.615.176 34
BSEG KUNNR <> 6.271.420.408 0
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
-
-
-
or CPU consumption.
statement
SQL Statement
-
15.2.3.5 Tables
-
HPP
-
-
-
15.2.4 SQL Statement ce7a5b93a54650716147164130ecd52 c
-
SELECT
/* FDA READ */ "MANDT" , "SETCLASS" , "SUBCLASS" , "SETNAME" , "LINEID" , "VALSIGN" , "VALOPTION" ,
"VALFROM" , "VALTO", "SEQNR"
FROM
"SETLEAF"
WHERE
"MANDT" = ? AND "SETNAME" = ? WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
-
-
SETLEAF MANDT = 90.429 0
SETLEAF SETNAME = 110.081.740 622.959
-
-
PREPARATION 0 0 - -
-
-

HPP
-
-
or CPU consumption.
statement
SQL Statement
-
15.2.4.5 Tables
-
SETLEAF SAPABAP1 COLUMN Table not partitioned 724.090 srvprdpar1
-
-
SPP LZ0_REPORTEU01 122 11.04.2022 - FI Gestión financiera
-
15.2.5 SQL Statement eb54f7641ea40eddf456604ecc100f4 6
-
CALL "CHECK_TABLE_CONSISTENCY"( ?, ?, ? ) WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value

HPP
Indicator Value
Maximal Memory Consumption [%] ( 06.10.2023 -- 17:40:25 ) 0,45
SAP HANA SQL Statements in HPP -> Top Statements (Total Memory)
-
-
TOTAL EXECUTION 1.001 1.001.417.686 1.001.417.686 1.001.417.686
PREPARATION 0 1.564 - -
-
-
-
-
Jobaname Component
SPP DBA:CHECK_________ CL_SQL_ST 22 24.03.2023 BC-DB-DBI Interface de
__@000000/1007 ATEMENT== base de
========= datos
===CM004 independient
e de ésta

HPP
Jobaname Component
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
-
15.3 Statements on Top Scanned Table
-
This section shows the top non-internal statements according to "Total Elapsed Time". The "Total Elapsed Time" is the
sum of the "Total Execution Time" and the "Total Preparation Time" from the SQL PLAN CACHE. It has a direct impact on
the response time of the application calling the statement.
Only SQL Statement accessing the "top scanned table" are shown. The "top scanned table" is the table that contains the
column with the highest number of "SCANNED_RECORDS" in M_CS_ALL_COLUMN_STATISTICS (see the following
table). IN many cases, creating an index on that column might improve the accesses.
Schema Table Column
SAPABAP1 BSEG ZUONR
Database Start 25.03.2023 -- 15:06:46
Data Collection 09.10.2023 -- 15:13:13
Data Source HOST_SQL_PLAN_CACHE
Begin of Time Interval 01.10.2023 -- 23:06:59
End of Time Interval 09.10.2023 -- 00:07:07
59a8aa9b59f3b52 2.062,0 10.037.544 205,4 1,0 205,5
78a05aa583b7d34
6b
093df47208b3914 1.325,6 10.584.510 125,2 0,2 572,2
f89da8424df29a7
09
35a2955f66943d1 646,9 10.075.634 64,2 1,0 64,2
49d47184a82a8c4
e1
HPP
ab43417b5314389 26,0 203.589 127,9 1,0 127,9
3b1917e975a6fb1
e9
59efaad81fd398bf 12,9 13.725 940,6 4,9 192,1
e78f184b3cfb9206
-
-
SELECT
*
FROM
"BSEG"
WHERE
Statement Impact
-
Indicator Value
SAP HANA SQL Statements in HPP -> Top Statements (Elapsed Time)
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG BUZEI = 5.150.245.884 1
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
-

HPP
-
-
or CPU consumption.
statement
SQL Statement
-
15.3.1.5 Tables
-
-
-
-
-
SELECT
"KUNNR"
FROM
"BSEG"
WHERE
HPP
Statement Impact
-
Indicator Value
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG GJAHR = 5.222.615.176 34
BSEG KUNNR <> 6.271.420.408 0
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
-
-
HPP

-
or CPU consumption.
statement
SQL Statement
-
15.3.2.5 Tables
-
-
-
-
15.3.3 SQL Statement 35a2955f66943d149d47184a82a8c4e 1
-
SELECT
"MATNR"
FROM
"BSEG"
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BUZEI" = ? AND "BELNR" = ? AND "GJAHR" = ? LIMIT 1 WITH
Statement Impact
-
Indicator Value
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG BUZEI = 5.150.245.884 1
BSEG GJAHR = 5.222.615.176 34

HPP
BSEG MANDT = 471 0
-
-
TOTAL EXECUTION 647 64 45 29.060
PREPARATION 0 0 - -
-
-
-
-
or CPU consumption.
statement
SQL Statement
-
15.3.3.5 Tables
-
-
HPP
-
-
15.3.4 SQL Statement ab43417b53143893b1917e975a6fb1e 9
-
SELECT
"FDLEV"
FROM
"BSEG"
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BELNR" = ? AND "GJAHR" = ? AND "AUGBL" = ? LIMIT 1 WITH
-
-
BSEG AUGBL = 2.745.211.384 0
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
15.3.4.3 Tables
-
-
-
SID Transaction / Jobaname Report Line Last Changed SAP Coding Application Description
on: Component
SPP RFITEMAP LZ0_REPORTEU01 138 11.04.2022 - FI Gestión
financiera
-
HPP
15.3.5 SQL Statement 59efaad81fd398bfe78f184b3cfb920 6

-
SELECT
/* FDA READ */ *
FROM
"BSEG"
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BELNR" = ? AND "GJAHR" = ?
ORDER BY
"BSEG" . "MANDT" , "BSEG" . "BUKRS" , "BSEG" . "BELNR" , "BSEG" . "GJAHR" , "BSEG" . "BUZEI" WITH
Statement Impact
-
Indicator Value
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
-

HPP
-
15.3.5.4 Tables
-
-
-
SPP LFAGL_BSEGU03 40 31.05.2013 FI-GL Contabilidad principal
-
15.4 Top Statements (Total Memory)
-
This section shows the top statements according to memory consumption as obtained from the SQL PLAN CACHE. It
considers the product of the number of executions and the average memory consumption per execution.
Database Start 25.03.2023 -- 15:06:46
Data Collection 09.10.2023 -- 15:13:13
Data Source M_SQL_PLAN_CACHE
Statement Hash Number of Time / Execution Records / Executionsx Avg Memory /
Executions [us] Execution Memx Avg Execution [MB]
Time[GBx s]
eb54f7641ea40ed 137 865.398.279,0 0,0 261.855 2.261,6
df456604ecc100f
46

HPP
Statement Hash Number of Time / Execution Records / Executionsx Avg Memory /
Executions [us] Execution Memx Avg Execution [MB]
Time[GBx s]
fbdfb43bd40beac 18.432 4.473.808,1 2.272,5 105.526 1.310,4
be0a4bfd32078a4
9e
77923757c5fbbc1 2.376 10.720.733,3 43.467,7 82.930 3.333,8
c4ecae4c1be2575
3f
b84d101d4a23db3 1.349 8.613.764,9 38.936,7 30.426 2.681,3
3393cf055c74186
5e
075f8774ea136ec 4.752 2.689.881,6 4.979,9 8.396 672,6
a598e8d20322f3f
75
-
15.4.1 SQL Statement eb54f7641ea40eddf456604ecc100f4 6
-
CALL "CHECK_TABLE_CONSISTENCY"( ?, ?, ? ) WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
-
-
TOTAL EXECUTION 118.560 865.398.151 692.312.637 1.220.765.797
PREPARATION 0 128 - -
-
-

HPP
-
-
Jobaname Component
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta

HPP
15.4.2 SQL Statement fbdfb43bd40beacbe0a4bfd32078a49 e

-
SELECT
*
FROM
"BSEG"
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BELNR" > ?
ORDER BY
"MANDT" , "BUKRS" , "BELNR" , "GJAHR" , "BUZEI" WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
Maximal Memory Consumption [%] 0,60
-
-
BSEG BELNR > 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG MANDT = 471 0
-
-
TOTAL EXECUTION 82.461 4.473.807 33.092 12.935.394
PREPARATION 0 1 - -
-
15.4.2.3 Tables
-
-
-
SPP LSDBI_DYNSQLU04 81 18.05.2004 BC-DB-DBI Interface de base de
datos independiente de
ésta
-
15.4.3 SQL Statement 77923757c5fbbc1c4ecae4c1be25753 f
-
SELECT

HPP
*
FROM
"ACCTCR"
WHERE
"MANDT" = ? AND "AWTYP" = ? AND "AWREF" > ?
ORDER BY
"MANDT" , "AWTYP" , "AWREF" , "AWORG" , "POSNR" , "CURTP" , "WAERS" WITH
Statement Impact
-
Indicator Value
-
-
ACCTCR AWREF > 169.620.997.680 0
ACCTCR AWTYP = 28.498.892.042 0
ACCTCR MANDT = 2.572 0
-
-
TOTAL EXECUTION 25.472 10.720.730 5.612 29.970.760
PREPARATION 0 3 - -
-
15.4.3.3 Tables
-
ACCTCR SAPABAP1 COLUMN Table not partitioned 78.574.020 srvprdpar1
-
-
ésta
-
15.4.4 SQL Statement b84d101d4a23db33393cf055c741865 e
-
SELECT
*
FROM
"MLCR"

HPP
WHERE
"MANDT" = ? AND "BELNR" > ?

ORDER BY
"MANDT" , "BELNR" , "KJAHR" , "POSNR" , "BDATJ" , "POPER" , "CURTP" WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
-
-
MLCR BELNR > 63.373.634.844 0
MLCR MANDT = 1.487 0
-
-
TOTAL EXECUTION 11.620 8.613.758 50.926 19.028.525
PREPARATION 0 7 - -
-
15.4.4.3 Tables
-
MLCR SAPABAP1 COLUMN Table not partitioned 44.619.069 srvprdpar1
-
-
ésta
-
15.4.5 SQL Statement 075f8774ea136eca598e8d20322f3f7 5
-
SELECT
*
FROM
"ACCTIT"
WHERE
"MANDT" = ? AND "AWTYP" = ? AND "AWREF" > ?
ORDER BY
"MANDT" , "AWTYP" , "AWREF" , "AWORG" , "POSNR" WITH RANGE_RESTRICTION('CURRENT')
Statement Impact

HPP
-
Indicator Value
-
-
ACCTIT AWREF > 83.954.700.892 0
ACCTIT AWTYP = 17.976.761.482 0
ACCTIT MANDT = 4.869 0
-
-
TOTAL EXECUTION 12.782 2.689.878 11.519 8.498.817
PREPARATION 0 3 - -
-
15.4.5.3 Tables
-
ACCTIT SAPABAP1 COLUMN Table not partitioned 19.643.505 srvprdpar1
-
-
ésta
-
15.5 Top Statement (Maximal Memory in Trace)
-
This section shows the top statements according to the maximal memory usage as of observed in the expensive statement
trace, i.e. M_EXPENSIVE_STATEMENTS.
Database Start 25.03.2023 -- 15:06:46
Data Collection 09.10.2023 -- 15:13:13
Analysis Type Analysis of Expensive Statement Trace
Data Source M_EXPENSIVE_STATEMENTS
First Day 02.10.2023
Last Day 08.10.2023

HPP
Statement Hash Time / Execution [us] Records / Execution Time / Record [us] Maximum Memory
[MB]
9b7f80dbffbccf31443e 0,0 0,0 0,0 17.098,0
19fff37b8ad5
ba0904efeb97c0b3df6 0,0 0,0 0,0 16.910,0
04f87a68ce183
d3cc54dc40b2e1e84f1 28.679.976,0 20,0 1.433.998,8 6.090,0
f49cd926ce6e8
e30e22893638b08569 0,0 0,0 0,0 4.114,0
f337d0fa088f71
980cd097466e6f63e91 0,0 0,0 0,0 4.083,0
bec129ae348f6
-
15.5.1 SQL Statement 9b7f80dbffbccf31443e19fff37b8ad5
-
SELECT
ZZHDBSSA1.*
FROM
(WITH /* [NAME] - HANA_Configuration_MiniChecks_2.00.059.01+ [DESCRIPTION] - General SAP HANA checks [VALID
FOR] - Revisions: >= 2.00.059.01 */ BASIS_INFO AS ( SELECT HOST,
ONLY_POTENTIALLY_CRITICAL_RESULTS,SKIP_LESS_RELEVANT_CHECKS_IN_SYSTEMDB,
MAX_VALUE_LENGTH, CHECK_ID, CHECK_GROUP, CHECK_ID_PREFIX, MAP(SHORTTERM_DAYS, -1, 99999,
SHORTTERM_DAYS) SHORTTERM_DAYS, MAP(MIDTERM_DAYS, -1, 99999, MIDTERM_DAYS) MIDTERM_DAYS,
MAP(LONGTERM_DAYS, -1, 99999, LONGTERM_DAYS) LONGTERM_DAYS, ORDER_BY
FROM
( SELECT /* Modification section */ '%' HOST, ' ' ONLY_POTENTIALLY_CRITICAL_RESULTS, 'X'
SKIP_LESS_RELEVANT_CHECKS_IN_SYSTEMDB, 60 MAX_VALUE_LENGTH, -1 CHECK_ID, '%' CHECK_GROUP, 'M'
CHECK_ID_PREFIX, 1 SHORTTERM_DAYS, 7 MIDTERM_DAYS, 31 LONGTERM_DAYS, 'CHECK' ORDER_BY /*
HOST, CHECK */
FROM DUMMY ) ), SQL_DATA_AREAS AS ( SELECT 'Pool/AttributeEngine/Transient' ALLOCATOR
FROMDUMMY UNION ALL SELECT 'Pool/AttributeEngine/Transient/updateContainerConcat'
FROMDUMMY UNION ALL SELECT 'Pool/CalculationEngine/ceQOExecutor'
FROMDUMMY UNION ALL SELECT 'Pool/CalculationEngine/query/pops'
FROMDUMMY UNION ALL SELECT 'Pool/ColumnStoreTables/Delta'
FROMDUMMY UNION ALL SELECT 'Pool/ColumnStoreTables/Main/Rowid/build-reverse-index'
FROMDUMMY UNION ALL SELECT 'Pool/CSPlanExecutor/PlanExecution'
FROMDUMMY UNION ALL SELECT 'Pool/DocidValueArray'
FROMDUMMY UNION ALL SELECT 'Pool/ESX'
FROMDUMMY UNION ALL SELECT 'Pool/ExecutorPlanExecution'
FROMDUMMY UNION ALL SELECT 'Pool/Filter'
FROMDUMMY UNION ALL SELECT 'Pool/itab'
FROMDUMMY UNION ALL SELECT 'Pool/itab/expr'
FROMDUMMY UNION ALL SELECT 'Pool/itab/FindBlocks2'
FROMDUMMY UNION ALL SELECT 'Pool/itab/VectorColumn'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/DictsAndDocs'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAggregate'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAggregate/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAssembleResults'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAssembleResults/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECalculate'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECalculate/TmpResults'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECalculate/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECreateNTuple'
HPP
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEEvalPrecond'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEPlanData/deserialized'

FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEPreAggregate'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JERequestedAttributes/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEStep1'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/NTuple'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/PlanDataAttrVals/Deserialized'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/ValueList'
FROMDUMMY UNION ALL SELECT 'Pool/L/llang/Runtime/Global'
FROMDUMMY UNION ALL SELECT 'Pool/L/llang/Runtime/Local'
FROMDUMMY UNION ALL SELECT 'Pool/LOBStorage'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcalcengine.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcalcengineapi.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcalcenginepops.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcs.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcswrapper.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbdistmetadata.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbevaluator.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbitab.so'
FROM
DUMMY UNION ALL SELECT 'Pool/malloc/libhdbolap.so'
...
Statement Impact
-
Indicator Value
-
-

HPP
-
15.5.1.2 Tables
-
CS_COLUMNS_ SYS ROW Table not partitioned 1.489.853 srvprdpar1
CS_TABLES_ SYS ROW Table not partitioned 111.172 srvprdpar1
CS_VIEW_ATTRIBUTES_ SYS ROW Table not partitioned 10.522 srvprdpar1
CS_CONCAT_ATTRIBUTES_ SYS ROW Table not partitioned 2.320 srvprdpar1
CS_HIERARCHY_DEFINITIONS_ SYS ROW Table not partitioned 493 srvprdpar1
CS_JOIN_INDEXES_ SYS ROW Table not partitioned 408 srvprdpar1
ADAPTER_LOCATIONS_ SYS ROW Table not partitioned 16 srvprdpar1
ADAPTERS_ SYS ROW Table not partitioned 16 srvprdpar1
CS_CALC_INDEXES_ SYS ROW Table not partitioned 8 srvprdpar1
CE_SCENARIOS_ SYS ROW Table not partitioned 5 srvprdpar1
... (further 18 tables)... ... ... ... - ...
-
-
Jobaname Component
SPP /BDL/TASK_PROCES CL_SQL_ST 22 24.03.2023 BC-DB-DBI Interface de
SOR ATEMENT== base de
========= datos
e de ésta
SPP /BDL/TASK_PROC CL_SQL_ST 22 24.03.2023 BC-DB-DBI Interface de
ESSOR0000007378 ATEMENT== base de
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
-
15.5.2 SQL Statement ba0904efeb97c0b3df604f87a68ce18 3
-
SELECT
ZZHDBSSA1.*
FROM
(WITH /* [NAME] - HANA_Configuration_MiniChecks_2.00.059.01+ [DESCRIPTION] - General SAP HANA checks [VALID
HPP
FOR] - Revisions: >= 2.00.059.01 */ BASIS_INFO AS ( SELECT HOST,
ONLY_POTENTIALLY_CRITICAL_RESULTS,SKIP_LESS_RELEVANT_CHECKS_IN_SYSTEMDB,
MAX_VALUE_LENGTH, CHECK_ID, CHECK_GROUP, CHECK_ID_PREFIX, MAP(SHORTTERM_DAYS, -1, 99999,
SHORTTERM_DAYS) SHORTTERM_DAYS, MAP(MIDTERM_DAYS, -1, 99999, MIDTERM_DAYS) MIDTERM_DAYS,
MAP(LONGTERM_DAYS, -1, 99999, LONGTERM_DAYS) LONGTERM_DAYS, ORDER_BY
FROM
( SELECT /* Modification section */ '%' HOST, ' ' ONLY_POTENTIALLY_CRITICAL_RESULTS, 'X'
SKIP_LESS_RELEVANT_CHECKS_IN_SYSTEMDB, 60 MAX_VALUE_LENGTH, -1 CHECK_ID, '%' CHECK_GROUP, 'M'
CHECK_ID_PREFIX, 1 SHORTTERM_DAYS, 7 MIDTERM_DAYS, 31 LONGTERM_DAYS, 'CHECK' ORDER_BY /*
HOST, CHECK */
FROM DUMMY ) ), SQL_DATA_AREAS AS ( SELECT 'Pool/AttributeEngine/Transient' ALLOCATOR
FROMDUMMY UNION ALL SELECT 'Pool/AttributeEngine/Transient/updateContainerConcat'
FROMDUMMY UNION ALL SELECT 'Pool/CalculationEngine/ceQOExecutor'
FROMDUMMY UNION ALL SELECT 'Pool/CalculationEngine/query/pops'
FROMDUMMY UNION ALL SELECT 'Pool/ColumnStoreTables/Delta'
FROMDUMMY UNION ALL SELECT 'Pool/ColumnStoreTables/Main/Rowid/build-reverse-index'
FROMDUMMY UNION ALL SELECT 'Pool/CSPlanExecutor/PlanExecution'
FROMDUMMY UNION ALL SELECT 'Pool/DocidValueArray'
FROMDUMMY UNION ALL SELECT 'Pool/ESX'
FROMDUMMY UNION ALL SELECT 'Pool/ExecutorPlanExecution'
FROMDUMMY UNION ALL SELECT 'Pool/Filter'
FROMDUMMY UNION ALL SELECT 'Pool/itab'
FROMDUMMY UNION ALL SELECT 'Pool/itab/expr'
FROMDUMMY UNION ALL SELECT 'Pool/itab/FindBlocks2'
FROMDUMMY UNION ALL SELECT 'Pool/itab/VectorColumn'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/DictsAndDocs'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAggregate'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAggregate/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAssembleResults'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEAssembleResults/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECalculate'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECalculate/TmpResults'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECalculate/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JECreateNTuple'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEEvalPrecond'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEPlanData/deserialized'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JEPreAggregate'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/JERequestedAttributes/Results'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/NTuple'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/PlanDataAttrVals/Deserialized'
FROMDUMMY UNION ALL SELECT 'Pool/JoinEvaluator/ValueList'
FROMDUMMY UNION ALL SELECT 'Pool/L/llang/Runtime/Global'
FROMDUMMY UNION ALL SELECT 'Pool/L/llang/Runtime/Local'
FROMDUMMY UNION ALL SELECT 'Pool/LOBStorage'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcalcengine.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcalcengineapi.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcalcenginepops.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcs.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbcswrapper.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbdistmetadata.so'
HPP
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbevaluator.so'
FROMDUMMY UNION ALL SELECT 'Pool/malloc/libhdbitab.so'

FROM
DUMMY UNION ALL SELECT 'Pool/malloc/libhdbolap.so'
...
Statement Impact
-
Indicator Value
-
-
-
15.5.2.2 Tables
-
CS_VIEW_ATTRIBUTES_ SYS ROW Table not partitioned 10.522 srvprdpar1
CS_HIERARCHY_DEFINITIONS_ SYS ROW Table not partitioned 493 srvprdpar1
ADAPTER_LOCATIONS_ SYS ROW Table not partitioned 16 srvprdpar1
ADAPTERS_ SYS ROW Table not partitioned 16 srvprdpar1
CS_CALC_INDEXES_ SYS ROW Table not partitioned 8 srvprdpar1
CE_SCENARIOS_ SYS ROW Table not partitioned 5 srvprdpar1
... (further 18 tables)... ... ... ... - ...
-
-
HPP
SID APPLICATION_SOURCE Transaction / Jobaname

SPA CL_SQL_STATEMENT==============CP:500 /BDL/TASK_PROCESSOR
-
15.5.3 SQL Statement d3cc54dc40b2e1e84f1f49cd926ce6e 8
-
SELECT
ZZHDBSSA1.*
FROM
(SELECT /* [NAME] HANA_Tables_ColumnStore_Columns_2.00.040+ [DESCRIPTION] - Provides information for columns
located in column store [SOURCE] - SAP Note 1969700 [DETAILS AND RESTRICTIONS] -
M_CS_ALL_COLUMN_STATISTICS available withSAP HANA >= 2.00.030 -
M_CS_ALL_COLUMNS.PERSISTENT_MEMORY_SIZE_IN_TOTAL available with SAP HANA >= 2.00.030 -
M_CS_ALL_COLUMNS.NUMA_NODE_INDEX available with SAP HANA >= 2.00.040 [VALID FOR] - Revisions: >=
2.00.040 [SQL COMMAND VERSION] - 2014/03/13: 1.0 (initial version) - 2014/04/02: 1.1 (NUM_DISTINCT included) -
2014/07/09: 1.2 (LOADED added) - 2014/10/20: 1.3 (OBJECT_LEVEL added) - 2015/01/17: 1.4 (FULLTEXT_INDEXES
included) - 2015/07/21: 1.5 (EXCLUDE_PK_AND_UNIQUE included) - 2017/03/21: 1.6 (LAST_LOAD_TIME included) -
2018/12/17: 1.7 (dedicated 2.00.030+ version including M_CS_ALL_COLUMN_STATISTICS) - 2019/03/16: 1.8
(PERSISTENT_MEMORY included) - 2019/06/05: 1.9 (persistent memory details considered) - 2019/06/26: 2.0
(COLUMN_NAME filter added) - 2019/11/03: 2.1 (ONLY_PK_AND_UNIQUE added) - 2020/09/24: 2.2 (dedicated
2.00.040+ version including NUMA node information, PART_ID filter added) - 2020/10/01: 2.3 (PERSISTENCY_TYPE and
LOAD_UNIT added) - 2020/12/05: 2.4 (MEM_PAGED_MB added) - 2021/06/15: 2.5 (DISK_MB and DISK_PAGE_MB
added) [INVOLVED TABLES] - CS_JOIN_CONDITIONS - CONSTRAINTS - INDEX_COLUMNS - INDEXES -
M_CS_ALL_COLUMNS - M_CS_ALL_COLUMN_STATISTICS - M_CS_COLUMNS_PERSISTENCE - TABLE_COLUMNS
[INPUT PARAMETERS] - HOST Host name 'saphana01' --> Specic host saphana01 'saphana%' --> All hosts starting with
saphana '%' --> All hosts - PORT Port number '30007' --> Port 30007 '%03' --> All ports ending with '03' '%' --> No
restriction to ports - SERVICE_NAME Service name 'indexserver' --> Specific service indexserver '%server' --> All services
ending with 'server' '%' --> All services - SCHEMA_NAME Schema name or pattern 'SAPSR3' --> Specific schema
SAPSR3 'SAP%' --> All schemata starting with 'SAP' '%' --> All schemata - TABLE_NAME Table name or pattern 'T000' -->
Specific table T000 'T%' --> All tables starting with 'T' '%' --> All tables - COLUMN_NAME Column name 'MATNR' -->
Column MATNR 'Z%' --> Columns starting with "Z" '%' --> No restriction related to columns - PART_ID Partition number 2
--> Only show information for partition number 2 -1 --> No restriction related to partition number - DATA_TYPE Column
data type 'NCLOB' --> Type 'NCLOB' '%LOB%' --> All types containing 'LOB' '%' --> All types -
COLUMN_NAME_LENGTH_LIMIT Maximum length of displayed column name (truncation if name is longer) 40 --> Display
a maximum of 40 characters of column name -1 --> Display complete column names - ATTRIBUTE_TYPE Column
attribute type 'ROWID' --> Restriction to columns with internal attribute type 'ROWID' 'TREX%' --> Restriction to columns
with internalattribute type starting with 'TREX' '%' --> No restriction by internal attribute type - LOADED Columnmemory
load state 'TRUE' --> Column loaded into memory 'FALSE' --> Columns not loaded into memory '%' --> No restriction
related to column load state - LOAD_UNIT Column load unit 'COLUMN' --> Load unit COLUMN (i.e. loading of complete
column) 'PAGE' --> Load unit PAGE (i.e. page-wise loads) - PAGEABLE Restriction to pageable / non-pageable columns
(paged attributes, see SAP Note 1871386) 'YES' --> Only show columns that can be defined as paged attributes 'NO' -->
Only show columns that cannot be definedas paged attributes '%' --> No restriction related to paged attributes -
PERSISTENT_MEMORY Utilization of persistent memory (SAP Note 2700084) 'TRUE' --> Only show tables using
persistent memory 'FALSE' --> Only show tables not using persistent memory '%' --> No restriction related to persistent
memory - PERSISTENCE_TYPE Persistence type of column 'SINGLE' --> Persistence type SINGLE 'VIRTUAL_FILE' -->
Persistence type VIRTUAL_FILE '%' --> No restriction related to persistence type - ONLY_INTERNAL_COLUMNSActivates
/ deactivates restriction to internal columns 'X' --> Only internal columns (typically starting with '$') are considered ' ' --> All
columns are considered - EXCLUDE_PK_AND_UNIQUE Possibility to exclude columns related to primary keys and unique
indexes 'X' --> Exclude columns related to primary keysand unique indexes ' ' --> No restriction
...
Statement Impact
-
Indicator Value
-
HPP
-
TOTAL EXECUTION 57 28.679.976 28.545.621 28.814.331
PREPARATION 0 0 - -
-
15.5.3.2 Memory Consumption
-
The following table provides an overview of the memory consumption of the analyzed SQL statement as obtained from the
monitoring view M_SQL_PLAN_STATISTICS (or – if not yet available – M_SQL_PLAN_CACHE), that is, without taking a
specific time interval into account.
Activity Average Memory [MB] Minimal Memory [MB] Maximal Memory [MB]
EXECUTION_MEMORY_SIZE 6.090,0 6.083,8 6.093,3
-
15.5.3.2.1 High Memory Consumption
-
The memory consumption of this statement is relatively high when compared with the minimum "effective allocation limit" of
the index server(s) as obtained from M_SERVICE_MEMORY. See the following table for details. Note that the excessive
memory consumption of a single statement might impact the stability of the whole SAP HANA system. See SAP Note
1999997 for details and for an option to restrict the maximum memory allocated by a single statement.
(Minimal) Effective Allocation Limit [GB] 477,0
Maximal Statement Size / Effective Allocation Limit [%] 1,2
Average Statement Size / Effective Allocation Limit [%] 1,2
-
-
-
15.5.3.4 Tables
-

HPP
P_INDEXES_ SYS ROW Table not partitioned 117.215 srvprdpar1
P_GRANTEDPRIVS_ SYS ROW Table not partitioned 2.819 srvprdpar1
P_PROCEDURES_ SYS ROW Table not partitioned 1.211 srvprdpar1
CS_JOIN_CONSTRAINTS_ SYS ROW Table not partitioned 777 srvprdpar1
CS_JOIN_CONDITIONS_ SYS ROW Table not partitioned 468 srvprdpar1
P_PRINCIPALS_ SYS ROW Table not partitioned 108 srvprdpar1
... (further 15 tables)... ... ... ... - ...
-
-
Jobaname Component
SPP /BDL/TASK_PROCES CL_SQL_ST 22 24.03.2023 BC-DB-DBI Interface de
SOR ATEMENT== base de
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
========= datos
e de ésta
-
15.5.4 SQL Statement e30e22893638b08569f337d0fa088f7 1
-
SELECT
ZZHDBSSA1.*
FROM
(WITH BASIS_INF AS ( SELECT /* MODIFICATION SECTION */ 'X' HIST, /* IF 'X' HISTORICAL DATA OR IF ' ' LAST
MINUTE DATA */ (SELECT ADD_DAYS(AGG.TODAY, -(AGG.DAYS + 7)) "START_DATE"
FROM( select TO_DATE(current_timestamp) TODAY, (SELECT WEEKDAY (TO_DATE (current_timestamp))
FROMDUMMY) DAYS
FROM
DUMMY )AGG) AS INI_DATE, /* DATE AND TIME ANALYSIS START */ current_timestamp AS END_DATE, /* DATE
AND TIME ANALYSIS END */ 10 MAX_APPS, /* RETURNS TOP APPLICATIONS, REST WILL BE GROUPED IN
'_OTHERS_', EXCEL ALLOWS UP TO 255 COLUMNS */ 5 MAX_ROWS_APP, /* RETURNS TOP HASHES PER
APPLICATION, REST WILL BE GROUPED WITH A SIGN '+' */ '3600' TIME_INTERV, /* TIME INTERVAL IN SECONDS */
'X' SYS_STATS, /* IF 'X' EMBEDDED STATISTICS SERVER THREADS ARE GROUPED */ 'X' AUTO, /* IF 'X' THEN

HPP
MAX_APPS AND MAX_ROWS_APP WILL BE ADJUSTED ACORDING TOTHE SERVER NODES, NEXT SECTION OF
THE SCRIPT */ 10800 MAX_ROWS_TOT /* FINAL RESULT LIMITED TO ROWS, ONLY SERVERS WITH COMPLETE
RESULTSET WILL BE RETURN, IF IS -1 THEN NO LIMIT */
FROM
DUMMY ), BASIS_INFO AS ( SELECT HIST, INI_DATE, END_DATE, CASE WHEN AUTO= 'X' AND SR.HOST_AN = '1'
THEN MAX_APPS WHEN AUTO = 'X' AND SR.HOST_AN = '2' THEN 7 WHEN AUTO = 'X' AND SR.HOST_AN = '3'
THEN 6 WHEN AUTO = 'X' AND SR.HOST_AN = '4' THEN 5 WHEN AUTO = 'X' AND SR.HOST_AN = '5' THEN 5 WHEN
AUTO = 'X' AND SR.HOST_AN >= '6' THEN 3 END MAX_APPS, CASE WHEN AUTO = 'X' AND SR.HOST_AN = '1'
THEN MAX_ROWS_APP WHEN AUTO = 'X' AND SR.HOST_AN = '2' THEN 5 WHEN AUTO = 'X' AND SR.HOST_AN =
'3' THEN 4 WHEN AUTO = 'X' AND SR.HOST_AN = '4' THEN 3 WHEN AUTO = 'X' AND SR.HOST_AN = '5' THEN 3
WHEN AUTO = 'X' AND SR.HOST_AN >= '6' THEN 3 END MAX_ROWS_APP, TIME_INTERV, SYS_STATS, HOST_AN
FROM BASIS_INF, (SELECT COUNT(*) HOST_AN
FROM
M_LANDSCAPE_HOST_CONFIGURATION
WHERE
INDEXSERVER_ACTUAL_ROLE = 'MASTER' OR INDEXSERVER_ACTUAL_ROLE = 'COORDINATOR' OR
INDEXSERVER_ACTUAL_ROLE = 'SLAVE' OR INDEXSERVER_ACTUAL_ROLE = 'WORKER' ) SR ),
THREADES_BY_TIME_1 AS ( SELECT HOST, TIMESTAMP, APPLICATION_NAME, STATEMENT_HASH HASH,
STATEMENT_EXECUTION_ID, CASE WHEN APPLICATION_SOURCE = '?' and APPLICATION_NAME <> '?' THEN
APPLICATION_NAME ELSE SUBSTR_BEFORE(APPLICATION_SOURCE, ':') END APP_NAME
FROM
BASIS_INFO BI, _SYS_STATISTICS.HOST_SERVICE_THREAD_SAMPLES TS
WHERE
TS.THREAD_STATE = 'Running' AND TS.CONNECTION_ID >= 0 AND TS.THREAD_ID >= 0 AND TS.TIMESTAMP >=
BI.INI_DATE AND TS.TIMESTAMP <= BI.END_DATE AND BI.HIST = 'X' UNION ALL SELECT HOST, TIMESTAMP,
APPLICATION_NAME, STATEMENT_HASH HASH, STATEMENT_EXECUTION_ID, CASE WHEN
APPLICATION_SOURCE = '?' and APPLICATION_NAME <> '?' THEN APPLICATION_NAME ELSE
SUBSTR_BEFORE(APPLICATION_SOURCE, ':') END APP_NAME
FROM
BASIS_INFO BI, M_SERVICE_THREAD_SAMPLES TS
WHERE
BI.INI_DATE AND TS.TIMESTAMP <= BI.END_DATE AND BI.HIST <> 'X' ), THREADES_BY_TIME_1_GROUPED AS(
SELECT HOST, TIMESTAMP, CASE WHEN BI.SYS_STATS = 'X' AND APPLICATION_NAME = 'Embedded Statistics
Server' THEN 'HANA(Statistics Server)' ELSE HASH END HASH, CASE WHEN APP_NAME LIKE '/1LT/SAP%' THEN
'/1LT/SAP* (SLT)' WHEN APPLICATION_NAME = 'Embedded Statistics Server' THEN 'HANA(Statistics Server)' ELSE
APP_NAME END APP_NAME, COUNT(*) THREAD_COUNT, COUNT(DISTINCT(STATEMENT_EXECUTION_ID))
STMT_EXECUTION_ID
FROM
BASIS_INFO BI, THREADES_BY_TIME_1 TS1
GROUP BY
HOST, TIMESTAMP, CASE WHEN BI.SYS_STATS = 'X' AND APPLICATION_NAME = 'Embedded Statistics Server'
THEN 'HANA(Statistics Server)' ELSE HASH END, CASE WHEN APP_NAME LIKE '/1LT/SAP%' THEN '/1LT/SAP* (SLT)'
WHEN APPLICATION_NAME = 'Embedded Statistics Server' THEN 'HANA(Statistics Server)' ELSE APP_NAME END ),
TIME_SLICE AS ( SELECT HOST, ADD_SECONDS('2014-01-01 00:00:00', F
...
Statement Impact
-
Indicator Value
-
-
Table Field Operator
? APPLICATION_NAME <>
? APPLICATION_NAME =
? APPLICATION_SOURCE =
HPP
? APP_NAME LIKE
? CONNECTION_ID >=
? HIST <>
? HIST =
? INDEXSERVER_ACTUAL_ROLE =
? SYS_STATS =
? THREAD_ID >=
? THREAD_STATE =
? TIMESTAMP <=
? TIMESTAMP >=
-
15.5.4.2 Tables
-
HOST_SQL_PLA _SYS_STATISTICS COLUMN Table not partitioned 472.260 srvprdpar1
N_CACHE_BASE
HOST_RESOURC _SYS_STATISTICS COLUMN Table not partitioned 61.635 srvprdpar1
E_UTILIZATIO
N_STATISTICS_BASE
HOST_SERVICE _SYS_STATISTICS COLUMN Table not partitioned 50.965 srvprdpar1
_THREAD_SAMP
LES_BASE
DUMMY SYS ROW Table not partitioned 1 srvprdpar1
-
-
Jobaname Component
========= datos
e de ésta
-
15.5.5 SQL Statement 980cd097466e6f63e91bec129ae348f 6
-
SELECT
ZZHDBSSA1.*
FROM
(WITH BASIS_INF AS ( SELECT /* MODIFICATION SECTION */ 'X' HIST, /* IF 'X' HISTORICAL DATA OR IF ' ' LAST
MINUTE DATA */ (SELECT ADD_DAYS(AGG.TODAY, -(AGG.DAYS + 7)) "START_DATE"
FROM( select TO_DATE(current_timestamp) TODAY, (SELECT WEEKDAY (TO_DATE (current_timestamp))
FROMDUMMY) DAYS
FROM
DUMMY )AGG) AS INI_DATE, /* DATE AND TIME ANALYSIS START */ current_timestamp AS END_DATE, /* DATE
AND TIME ANALYSIS END */ 10 MAX_APPS, /* RETURNS TOP APPLICATIONS, REST WILL BE GROUPED IN
'_OTHERS_', EXCEL ALLOWS UP TO 255 COLUMNS */ 5 MAX_ROWS_APP, /* RETURNS TOP HASHES PER
APPLICATION, REST WILL BE GROUPED WITH A SIGN '+' */ '3600' TIME_INTERV, /* TIME INTERVAL IN SECONDS */
'X' SYS_STATS, /* IF 'X' EMBEDDED STATISTICS SERVER THREADS ARE GROUPED */ 'X' AUTO, /* IF 'X' THEN
MAX_APPS AND MAX_ROWS_APP WILL BE ADJUSTED ACORDING TOTHE SERVER NODES, NEXT SECTION OF
HPP
THE SCRIPT */ 10800 MAX_ROWS_TOT /* FINAL RESULT LIMITED TO ROWS, ONLY SERVERS WITH COMPLETE
RESULTSET WILL BE RETURN, IF IS -1 THEN NO LIMIT */
FROM
DUMMY ), BASIS_INFO AS ( SELECT HIST, INI_DATE, END_DATE, CASE WHEN AUTO= 'X' AND SR.HOST_AN = '1'
THEN MAX_APPS WHEN AUTO = 'X' AND SR.HOST_AN = '2' THEN 7 WHEN AUTO = 'X' AND SR.HOST_AN = '3'
THEN 6 WHEN AUTO = 'X' AND SR.HOST_AN = '4' THEN 5 WHEN AUTO = 'X' AND SR.HOST_AN = '5' THEN 5 WHEN
AUTO = 'X' AND SR.HOST_AN >= '6' THEN 3 END MAX_APPS, CASE WHEN AUTO = 'X' AND SR.HOST_AN = '1'
THEN MAX_ROWS_APP WHEN AUTO = 'X' AND SR.HOST_AN = '2' THEN 5 WHEN AUTO = 'X' AND SR.HOST_AN =
'3' THEN 4 WHEN AUTO = 'X' AND SR.HOST_AN = '4' THEN 3 WHEN AUTO = 'X' AND SR.HOST_AN = '5' THEN 3
WHEN AUTO = 'X' AND SR.HOST_AN >= '6' THEN 3 END MAX_ROWS_APP, TIME_INTERV, SYS_STATS, HOST_AN
FROM BASIS_INF, (SELECT COUNT(*) HOST_AN
FROM
M_LANDSCAPE_HOST_CONFIGURATION
WHERE
INDEXSERVER_ACTUAL_ROLE = 'MASTER' OR INDEXSERVER_ACTUAL_ROLE = 'COORDINATOR' OR
INDEXSERVER_ACTUAL_ROLE = 'SLAVE' OR INDEXSERVER_ACTUAL_ROLE = 'WORKER' ) SR ),
THREADES_BY_TIME_1 AS ( SELECT HOST, TIMESTAMP, APPLICATION_NAME, STATEMENT_HASH HASH,
STATEMENT_EXECUTION_ID, CASE WHEN APPLICATION_SOURCE = '?' and APPLICATION_NAME <> '?' THEN
APPLICATION_NAME ELSE SUBSTR_BEFORE(APPLICATION_SOURCE, ':') END APP_NAME
FROM
BASIS_INFO BI, _SYS_STATISTICS.HOST_SERVICE_THREAD_SAMPLES TS
WHERE
BI.INI_DATE AND TS.TIMESTAMP <= BI.END_DATE AND BI.HIST = 'X' UNION ALL SELECT HOST, TIMESTAMP,
APPLICATION_NAME, STATEMENT_HASH HASH, STATEMENT_EXECUTION_ID, CASE WHEN
APPLICATION_SOURCE = '?' and APPLICATION_NAME <> '?' THEN APPLICATION_NAME ELSE
SUBSTR_BEFORE(APPLICATION_SOURCE, ':') END APP_NAME
FROM
BASIS_INFO BI, M_SERVICE_THREAD_SAMPLES TS
WHERE
BI.INI_DATE AND TS.TIMESTAMP <= BI.END_DATE AND BI.HIST <> 'X' ), THREADES_BY_TIME_1_GROUPED AS(
SELECT HOST, TIMESTAMP, CASE WHEN BI.SYS_STATS = 'X' AND APPLICATION_NAME = 'Embedded Statistics
Server' THEN 'HANA(Statistics Server)' ELSE HASH END HASH, CASE WHEN APP_NAME LIKE '/1LT/SAP%' THEN
'/1LT/SAP* (SLT)' WHEN APPLICATION_NAME = 'Embedded Statistics Server' THEN 'HANA(Statistics Server)' ELSE
APP_NAME END APP_NAME, COUNT(*) THREAD_COUNT, COUNT(DISTINCT(STATEMENT_EXECUTION_ID))
STMT_EXECUTION_ID
FROM
BASIS_INFO BI, THREADES_BY_TIME_1 TS1
GROUP BY
HOST, TIMESTAMP, CASE WHEN BI.SYS_STATS = 'X' AND APPLICATION_NAME = 'Embedded Statistics Server'
THEN 'HANA(Statistics Server)' ELSE HASH END, CASE WHEN APP_NAME LIKE '/1LT/SAP%' THEN '/1LT/SAP* (SLT)'
WHEN APPLICATION_NAME = 'Embedded Statistics Server' THEN 'HANA(Statistics Server)' ELSE APP_NAME END ),
TIME_SLICE AS ( SELECT HOST, ADD_SECONDS('2014-01-01 00:00:00', F
...
Statement Impact
-
Indicator Value
-
-
? APPLICATION_NAME <>
? APPLICATION_NAME =
HPP
? APPLICATION_SOURCE =
? APP_NAME LIKE
? CONNECTION_ID >=
? HIST <>
? HIST =
? INDEXSERVER_ACTUAL_ROLE =
? SYS_STATS =
? THREAD_ID >=
? THREAD_STATE =
? TIMESTAMP <=
? TIMESTAMP >=
-
-
-
15.5.5.3 Tables
-
HOST_SQL_PLA _SYS_STATISTICS COLUMN Table not partitioned 472.260 srvprdpar1
N_CACHE_BASE
HOST_RESOURC _SYS_STATISTICS COLUMN Table not partitioned 61.635 srvprdpar1
E_UTILIZATIO
N_STATISTICS_BASE
HOST_SERVICE _SYS_STATISTICS COLUMN Table not partitioned 50.965 srvprdpar1
_THREAD_SAMP
LES_BASE
DUMMY SYS ROW Table not partitioned 1 srvprdpar1
-
-
HPP
SID APPLICATION_SOURCE Transaction / Jobaname

SPA CL_SQL_STATEMENT==============CP:500 /BDL/TASK_PROCESSOR
-
15.6 Top Statements (Thread Samples)
-
This section shows the top statements according to the number of observed "threads" ("Number of Samples") in the
SERVICE THREAD SAMPLES. A statement might occupy a high number of threads if (a) it has a long execution time, (b) it
is executed very often, or (c) it has a highly parallelized execution. In any case, it shows statements with a high resource
consumption on the SAP HANA database.
Database Start 25.03.2023 -- 15:06:46
Data Collection 09.10.2023 -- 15:13:13
Analysis Type Analysis of Thread Samples
Data Source HOST_SERVICE_THREAD_SAMPLES
Last Day 08.10.2023
Statement Hash Time / Execution [us] Records / Execution Time / Record [us] Number of Samples
9839265e2929b77258 622.794,1 306,3 2.033,3 190
cb495ace05b7d1
ba81a383d98a296d2e 2.137.958,7 0,0 0,0 92
44e04278ccb770
59a8aa9b59f3b5278a 205,4 1,0 205,5 79
05aa583b7d346b
33af180cf0874a5f432f 99,7 0,0 13.471,1 74
e90fc0e76480
430c496e0fe15c0353c 5.401.652,3 0,0 0,0 70
80de1c72caab1
-
15.6.1 SQL Statement 9839265e2929b77258cb495ace05b7d 1
-
/* procedure: "_SYS_STATISTICS"."COLLECTOR_HOST_SERVICE_THREAD_CALLSTACKS" line: 8 col: 2 (at pos 820)
*/ insert into _SYS_STATISTICS.HOST_SERVICE_THREAD_CALLSTACKS_BASE (snapshot_id, server_timestamp,
site_id,FRAME_LEVEL,FRAME_NAME,HOST,IS_ACTIVE,PORT,SERVICE_NAME,THREAD_ID)select
__typed_Longdate__($1) AS "SNAPSHOT_ID", current_timestamp,
STC.site_id,STC.frame_level,STC.frame_name,STC.host,STC.is_active,STC.port,STC.service_name,STC.thread_id
FROM
_SYS_STATISTICS.SOURCE_COLLECTOR_5057_SERVICE_THREAD_CALLSTACKS STC join
_SYS_STATISTICS.SOURCE_COLLECTOR_5057_SERVICE_T
HREADS ST on STC.host = ST.host and STC.port=ST.port and STC.site_id=ST.site_id and STC.thread_id = ST.thread_id
WHERE
ST.connection_id != current_connection and STC.is_active = 'TRUE'
ORDER BY
STC.thread_id, STC.frame_level, STC.site_id
Statement Impact
-
Indicator Value
-

HPP

-
Activity Average Time [us] Minimal Time [us] Maximal Time [us]
TOTAL EXECUTION 622.794 350.098 3.754.642
PREPARATION 0 - -
LOCK DURATION 0 - -
-
-
-
15.6.1.3 Root Statement
-
The following table shows details on the "ROOT STATEMENT", which is responsible for the observed SQL statement.
ROOT_STATEMENT_HASH ROOT_STATEMENT_TEXT Samples
d6fd6678833f9a2e25e7b53239c50e9a call _SYS_STATISTICS.STATISTICS_SC 400
HEDULABLEWRAPPER('Timer', ?, ?, ?, ?)
-
-
APPLICATION_NAME APPLICATION_SOURCE PASSPORT_ACTION
Embedded Statistics Server running ID (5057, deletion: no) for 03.10.2023 00:26:54 000 Tue -
Embedded Statistics Server running ID (5057, deletion: no) for 04.10.2023 00:16:54 000 Wed -
Embedded Statistics Server running ID (5057, deletion: no) for 06.10.2023 01:56:54 000 Fri -
Embedded Statistics Server running ID (5057, deletion: no) for 07.10.2023 00:26:54 000 Sat -
Embedded Statistics Server running ID (5057, deletion: no) for 07.10.2023 00:36:54 000 Sat -
-
HPP
15.6.1.5 Internal SQL Statement

-
This SQL statement was executed from an internal database connection.
-
15.6.2 SQL Statement ba81a383d98a296d2e44e04278ccb77 0
-
/* procedure: "_SYS_STATISTICS"."ALERT_MON_PART_TABLE_SIZE_HOST_MAIN_MEM" variable: TABLES line: 21
col: 106 (at pos 1799) */ select top 100 t0.host || '.' || t0.port || '.' || t1.schema_name || '.' || t1.table_name || '.' || t1.part_id
index_id, t0.host, t0.port, t1.schema_name, t1.table_name, t1.part_id, round(t1.memory_size_in_main /
t0.effective_allocation_limit * 100,0) main_mem_usage_perc, round(t1.memory_size_in_total / t0.effective_allocation_limit *
100,0) total_mem_usage_perc, t1.memory_size_in_main, t1.memory_size_in_total, t0.effective_allocation_limit
FROM
_SYS_STATISTICS.source_alert_45_service_memory t0, _SYS_STATISTICS.source_alert_45_cs_tables t1
WHERE
t0.host=t1.host and t0.port=t1.port
ORDER BY
main_mem_usage_perc desc
Statement Impact
-
Indicator Value
-
15.6.2.1 Known Issue
-
Information about this statement (as identified by its STATEMENT_HASH) can be found in the following SAP Note:
Recommendation: Check the mentioned SAP Note(s) for the recommendation concerning the statement and apply
the recommendation if applicable.
STATEMENT_HASH SAP Note Type Object

ba81a383d98a296d2e44e04 2000002 SELECT M_CS_ALL_COLUMNS, M_CS_COLUMNS, M_CS_TABLES
278ccb770
-
-
TOTAL EXECUTION 2.137.959 1.362.868 4.174.863
PREPARATION 0 - -
LOCK DURATION 0 - -
-
-

HPP
-
-
-
-
-
-
SELECT
*
FROM
"BSEG"
WHERE
Statement Impact
-
Indicator Value
-
HPP
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG BUZEI = 5.150.245.884 1
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
-
TOTAL EXECUTION 205 43 37.054
PREPARATION 0 - -
LOCK DURATION 0 - -
-
-
-
-
or CPU consumption.
statement
SQL Statement
-
15.6.3.5 Tables
-
HPP
-
-
-
15.6.4 SQL Statement 33af180cf0874a5f432fe90fc0e7648 0
-
SELECT
*
FROM
"NAST"
WHERE
"MANDT" = ? AND "OBJKY" = ? AND "KAPPL" = ? AND "KSCHL" = ? AND "NACHA" = N'1' AND "VSTAT" <= ? LIMIT 1
WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
-
-
NAST KAPPL = 96.239.553 3.082
NAST KSCHL = 87.861.629 2
NAST MANDT = 1.442 1
NAST NACHA = 0 0
NAST OBJKY = 126.736.979 1
NAST VSTAT <= 2.367.144 0
-
-
TOTAL EXECUTION 100 76 30.328
PREPARATION 0 - -
LOCK DURATION 0 - -
-
-
HPP
-
-
The distribution of thread samples with the status "Running" correlates with the overall CPU or memory consumption of the
system. Such a correlation indicates that this statement might be responsible for peaks in the memory or CPU
consumption.
CPU consumption index server(s) - Threads (running) from this SQL 0,30 weak correlation
statement
SQL Statement
-
15.6.4.5 Tables
-
NAST SAPABAP1 COLUMN Table not partitioned 639.574 srvprdpar1
-
-
Jobaname Component
SPP IDCP IDPRCNINV 2.095 24.03.2023 FI-LOC-SD-CN Ventas y
OICE distribución
para China
SPP IDPRCNINVOICE IDPRCNINV 2.095 24.03.2023 FI-LOC-SD-CN Ventas y
OICE distribución
para China
-
15.6.5 SQL Statement 430c496e0fe15c0353c80de1c72caab 1
HPP
-
/* procedure: "_SYS_STATISTICS"."ALERT_MON_PART_TABLE_SIZE_HOST_TOTAL_MEM" variable: TABLES line: 21
col: 106 (at pos 1800) */ select top 100 t0.host || '.' || t0.port || '.' || t1.schema_name || '.' || t1.table_name || '.' || t1.part_id
index_id, t0.host, t0.port, t1.schema_name, t1.table_name, t1.part_id, round(t1.memory_size_in_main /
t0.effective_allocation_limit * 100,0) main_mem_usage_perc, round(t1.memory_size_in_total / t0.effective_allocation_limit *
100,0) total_mem_usage_perc, t1.memory_size_in_main, t1.memory_size_in_total, t0.effective_allocation_limit
FROM
_SYS_STATISTICS.source_alert_40_service_memory t0, _SYS_STATISTICS.source_alert_40_cs_tables t1
WHERE
t0.host=t1.host and t0.port=t1.port
ORDER BY
total_mem_usage_perc desc
Statement Impact
-
Indicator Value
-
15.6.5.1 Known Issue
-
Information about this statement (as identified by its STATEMENT_HASH) can be found in the following SAP Note:
Recommendation: Check the mentioned SAP Note(s) for the recommendation concerning the statement and apply
the recommendation if applicable.
STATEMENT_HASH SAP Note Type Object

430c496e0fe15c0353c80de1 2000002 CALL ALERT_MON_PART_TABLE_SIZE_HOST_TOTAL_MEM
c72caab1
430c496e0fe15c0353c80de1 2000002 SELECT M_CS_ALL_COLUMNS, M_CS_COLUMNS, M_CS_TABLES
c72caab1
-
-
TOTAL EXECUTION 5.401.652 3.185.629 10.953.829
PREPARATION 0 - -
LOCK DURATION 0 - -
-
-

HPP
-
-
-
-
-
15.7 Top Statements (CPU Peak Hour)
-
This section shows the top statements according to the number of observed "threads" ("Number of Samples") in the
SERVICE THREAD SAMPLES. A statement might occupy a high number of threads if (a) it has a long execution time, (b) it
is executed very often, or (c) it has a highly parallelized execution. In any case, it shows statements with a high resource
consumption on the SAP HANA database.
For this section, the hour with the highest number of thread samples in thread state" "Running" is determined, that is, the
"CPU peak hour". The top statements observed in this hour are listed and analyzed.
Hour of Maximal CPU Consumptiion
-
From To
02.10.2023 -- 14:00:00 02.10.2023 -- 15:00:00
Database Start 25.03.2023 -- 15:06:46
Data Collection 09.10.2023 -- 15:13:13
Analysis Type Analysis of Thread Samples
Data Source HOST_SERVICE_THREAD_SAMPLES
Last Day 08.10.2023

HPP
Statement Hash Time / Execution [us] Records / Execution Time / Record [us] Number if Samples in
CPU Peak Hour
59a8aa9b59f3b5278a 205,4 1,0 205,5 8
05aa583b7d346b
35a2955f66943d149d 64,2 1,0 64,2 7
47184a82a8c4e1
093df47208b3914f89d 125,2 0,2 572,2 5
a8424df29a709
ce7a5b93a546507161 111,0 1,0 111,0 5
47164130ecd52c
539dc509df8c76870b0 85,5 0,0 6.897,3 5
39fffea80d66e
-
-
SELECT
*
FROM
"BSEG"
WHERE
Statement Impact
-
Indicator Value
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG BUZEI = 5.150.245.884 1
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-

HPP
-
-
-
or CPU consumption.
statement
SQL Statement
-
15.7.1.5 Tables
-
-
-
-
15.7.2 SQL Statement 35a2955f66943d149d47184a82a8c4e 1
-
SELECT
"MATNR"
FROM
HPP
"BSEG"
WHERE
"MANDT" = ? AND "BUKRS" = ? AND "BUZEI" = ? AND "BELNR" = ? AND "GJAHR" = ? LIMIT 1 WITH
Statement Impact
-
Indicator Value
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG BUZEI = 5.150.245.884 1
BSEG GJAHR = 5.222.615.176 34
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
-

HPP
-
-
or CPU consumption.
statement
SQL Statement
-
15.7.2.5 Tables
-
-
-
-
-
SELECT
"KUNNR"
FROM
"BSEG"
WHERE
HPP
Statement Impact
-
Indicator Value
-
-
BSEG BELNR = 624.134.307.746 51
BSEG BUKRS = 7.235.082.490 0
BSEG GJAHR = 5.222.615.176 34
BSEG KUNNR <> 6.271.420.408 0
BSEG MANDT = 471 0
-
-
PREPARATION 0 0 - -
-
-
-
HPP

-
or CPU consumption.
statement
SQL Statement
-
15.7.3.5 Tables
-
-
-
-
15.7.4 SQL Statement ce7a5b93a54650716147164130ecd52 c
-
SELECT
/* FDA READ */ "MANDT" , "SETCLASS" , "SUBCLASS" , "SETNAME" , "LINEID" , "VALSIGN" , "VALOPTION" ,
"VALFROM" , "VALTO", "SEQNR"
FROM
"SETLEAF"
WHERE
"MANDT" = ? AND "SETNAME" = ? WITH RANGE_RESTRICTION('CURRENT')
Statement Impact
-
Indicator Value
-
-
SETLEAF MANDT = 90.429 0
SETLEAF SETNAME = 110.081.740 622.959
-
HPP
-
PREPARATION 0 0 - -
-
-
-
-
or CPU consumption.
statement
SQL Statement
-
15.7.4.5 Tables
-
SETLEAF SAPABAP1 COLUMN Table not partitioned 724.090 srvprdpar1
-
-
HPP
-
15.7.5 SQL Statement 539dc509df8c76870b039fffea80d66 e
-
SELECT
"LIFNR"
FROM
"BSIK"
WHERE
"MANDT" = ? AND "BELNR" = ? AND "GJAHR" = ? AND "BUKRS" = ? LIMIT 1 WITH
Statement Impact
-
Indicator Value
-
-
BSIK BELNR = 645.982 947
BSIK BUKRS = 2.949.122 0
BSIK GJAHR = 1.164.138 25
BSIK MANDT = 4.518.845 22
-
-
PREPARATION 0 0 - -
-
-

HPP
-
-
or CPU consumption.
statement
SQL Statement
-
15.7.5.5 Tables
-
BSIK SAPABAP1 COLUMN Table not partitioned 3.558 srvprdpar1
-
-

HPP
16 SAP NetWeaver Gateway

-
The gateway configuration and administration of your SAP ERP ENHANCE PACKAGE
system SPP have been analyzed and areas that require your attention have been
highlighted. To ensure system stability, you should implement the recommendations
in the following section.
Rating Check
MetaData Cache Activation
Logging Configuration
Gateway Error Logs
Important Periodic Jobs
-
16.1 Gateway Configuration
-
16.1.1 MetaData Cache Activation
-
Cache Activated
Metadata Cache Yes
The metadata cache is activated in your system as recommended.
-
16.1.2 Logging Configuration
-
Logging Use Case Log Level Recommended Log Level
Regular processing Error, Security, Warning Error, Security, Warning
The gateway logging configuration is set correctly on your system.
-
16.2 Gateway Administration
-
16.2.1 Important Periodic Jobs
-
The jobs based on the reports listed in the table below are important for the smooth operation of your system.
Report Name Scheduled Scheduled Recommended Rating Further Information
Periodically? Frequency Frequency
/UI5/UPD_OD X 1 per hour 48 Hours* LINK
ATA_METADAT
A_CACHE
/UI5/APP_INDEX_ X 15 mins Daily* LINK
CALCULATE
/IWFND/R_SM_C X 1 per day Daily LINK
LEANUP
/IWBEP/R_CLEAN - - Daily LINK
_UP_QRL
/IWBEP/SUTIL_C - - Daily LINK
LEANUP
/UI2/PERS_EXPIR - - Weekly LINK
ED_DELETE
Confidential SAP NetWeaver Gateway 109/120

Report Name Scheduled Scheduled Recommended Rating Further Information
Periodically? Frequency Frequency
/IWFND/R_METE X 1 per day Daily LINK
RING_DELETE
/IWFND/R_MET X 1 per day Daily LINK
ERING_AGGREG
ATE
*Schedule these jobs as indicated, or more often in periods of frequent imports, depending on your use case. Take
observed job duration for your system into account when tuning the schedule.
Recommendation : See the recommended schedule for the important periodic jobs listed in the table above. One or
more periodic jobs important for the smooth operation of your system are not scheduled to run regularly as
recommended.
Confidential SAP NetWeaver Gateway 110/120

17 UI Technologies Checks
-
The UI technology configuration and administration of your SAP ERP ENHANCE
PACKAGE system SPP have been analyzed and areas that require your attention have
been highlighted. To ensure system stability, you should implement the
recommendations in the following section.
Rating Check
Fiori Checks for SPP
-
17.1 Fiori Checks for SPP
-
Rating Check
Maintenance and Update Strategy for SAP Fiori Front-End Server
SAPUI5 Version
SAP Fiori Cache Buster Activation
HTTP/2 Support
SAP Fiori Launchpad Performance - Home Page Mode
Activated but unused ICF services in UI5 apps
The SAP Fiori configuration and administration of your SAP ERP ENHANCE PACKAGE system SPP have been analyzed
and problems that require your attention have been found. To ensure system stability, you should take corrective action as
soon as possible.
-
17.1.1 Maintenance and Update Strategy for SAP Fiori Front-End Server
-
Software Product SAP_UI Release End of Maintenance Rating
SAP Fiori FES 6.0 754 31.12.2027
Your version of the SAP Fiori Front-End Server (SAP_UI) is still in maintenance by SAP. For further information on the SAP
Fiori Front-End Server maintenance and upgrade strategy, refer to SAP Note 2217489 .
-
17.1.2 SAPUI5 Version
-
Current SAPUI5 Version Installed
1.71.53
Your SAPUI5 Library version is up to date as recommended. The planned end of maintenance for your SAPUI5 Library
version is 31.12.2027.
SAP recommends to plan updates and upgrades with SAP Maintenance Planner .
It is strongly recommended that you test all of your SAPUI5 applications before upgrading the SAPUI5 version in the
productive system.
-
17.1.3 SAP Fiori Cache Buster Activation
-
You have activated the cache buster mechanism for system SPP because the ICF service /sap/bc/ui2/flp is activated in
SICF.
Please note that to use the cache buster mechanism, you need to call the SAP Fiori launchpad with one of the following
URLs:
https://<server>:<port>/sap/bc/ui2/flp/
https://<server>:<port>/sap/bc/ui2/flp/index.html
Confidential UI Technologies Checks 111/120

https://<server>:<port>/sap/bc/ui2/flp/FioriLaunchpad.html
You can also maintain a custom URL via an SICF external alias as described here: Customize the Launchpad URL
Background:
Web browsers store static resources like JavaScript files, stylesheets, and images in the browser cache. When these
resources are changed on the server in a software upgrade, you want the browser to load the new resources from the
server rather than from the cache, without having to manually clear the browser cache.
Cache buster techniques cause Web browsers to load content from the server rather than from the browser cache when
new resources are available on the server.
You can find the latest information about the cache buster for SAP Fiori components in 2043432 .
-
17.1.4 HTTP/2 Support
-
HTTP/2 support is currently active as recommended.
The HTTP protocol is one of the most frequently used protocols on the Internet. However, HTTP/1.0 and HTTP/1.1 have
some disadvantages for modern applications, in particular with respect to performance in wide-area networks. To improve
these problems, their successor RFC 7540 HTTP/2 has been implemented.
For more information on HTTP/2 Support, see here
Host Parameter Name Current Value Rating
srvprdpar1 icm/HTTP/support_http2 true
-
17.1.5 SAP Fiori Launchpad Performance - Home Page Mode
-
The performance of the SAP Fiori Launchpad could not be evaluated. Either no statistics about your OData service
requests could be collected or none of your users use the SAP Fiori Launchpad in the Home Page/Groups mode.
-
17.1.6 Activated but unused ICF services in UI5 apps
-
Rating Unused ICF Services
195
SAP detected 195 activated ICF services in your system that cannot be used since the corresponding SAPUI5 apps have
not been configured correctly. Active ICF services represent a security risk as they can be accessed directly from the
Internet via the HTTP protocol. Please deactivate ICF services for SAPUI5 apps that are not used. The identification of
such ICF services is described in SAP KBA 3261151 .
-
17.1.7 Important Notes for SAP Fiori
-
The following SAP Notes contain important fixes or performance improvements for the SAP_UI Add-on.
Recommendation: Read these SAP Notes carefully and implement them if relevant.
SAP Note number Description
2380743 SAP_UI 7.51: UI2 Cache Invalidation Bug Fixes
Confidential UI Technologies Checks 112/120

18 Cross Application Business Process

Analysis
-
This section provides insights into cross-application data in the areas of jobs, interfaces, and data consistency.
The data is collected in the cross-application business process analysis (BPA) and the data collection findings are
displayed in the EWA if it is configured to include BPA data. Further details can be found in the cross-application BPA.
With Business Process Monitoring in SAP Solution Manager, you can continuously analyze the key figures displayed below
in addition to approximately 800 out-of-the-box key figures.
Disclaimer
Bear in mind that all assumptions and ratings in this presentation are based on our general experience with other
customers and that the findings are not necessarily business-critical in your particular case.
Rating Area Key Figure Finding
Jobs Canceled background jobs 19 of jobs have been canceled on the
peak day of the analyzed week.
Interfaces IDoc throughput (Inbound) 0 of all inbound IDocs have been
successfully processed in the analyzed
week.
Interfaces Erroneous IDocs (Inbound) 0 erroneous inbound IDocs were
identified for the analyzed week.
Interfaces IDoc backlog (Inbound) 0 backlog inbound IDocs have been
identified in the analyzed week.
Interfaces IDoc throughput (Outbound) 0 of all outbound IDocs have been
successfully processed in the analyzed
week.
Interfaces Erroneous IDocs (Outbound) 0 erroneous outbound IDocs were
identified for the analyzed week.
Interfaces IDoc backlog (Outbound) 0 backlog outbound IDocs have been
Interfaces Erroneous qRFC (Inbound) 0 qRFC inbound errors occurred during
the analyzed week.
Interfaces Backlog qRFC (Inbound) 0 inbound qRFC were in backlog in the
analyzed week.
Interfaces Erroneous qRFC (Outbound) 0 qRFC outbound errors occurred
during the analyzed week.
Interfaces Backlog qRFC (Outbound) 0 outbound qRFC were in backlog in
the analyzed week.
Interfaces Erroneous bgRFC (Inbound) 0 bgRFC inbound errors occurred
Interfaces Backlog bgRFC (Inbound) 0 inbound bgRFC were in backlog in
the analyzed week.
Interfaces Erroneous bgRFC (Outbound) 0 bgRFC outbound errors occurred
Interfaces Backlog bgRFC (Outbound) 0 outbound bgRFC were in backlog in
the analyzed week.
Interfaces Workflows in error 0 errors in workflows have been
Interfaces Throughput batch input sessions 1015 throughput batch input sessions
have been identified in the analyzed
week.
Interfaces Batch input sessions with errors 211 erroneous batch input sessions
week.
Interfaces Batch input sessions in backlog 347 batch input sessions in backlog
week.
Confidential Cross Application Business 113/120

Process Analysis
Rating Area Key Figure Finding
Interfaces Erroneous PI messages 0 erroneous PI messages have been
Interfaces PI messages in backlog 0 PI messages in backlog have been
Interfaces Canceled PI messages messages 0 canceled PI messages have been
Data Consistency Errors in update task 2 errors in update tasks occurred
Data Consistency Consistency check scheduling verification Not all variants for all recommended
Data Consistency reports have been
executed
Data Consistency Posting of error records from auto. goods movements 0 failed goods movements were
identified that are more than seven day
old.
The displayed measurements relate to the findings in the cross-application business process analysis (BPA). For more
information, see the results of the BPA. For more information about the BPA, check the following link:
SAP CQC BPI.pdf
If you have an SAP Enterprise Support contract, SAP Active Global Support will provide you with the following offerings to
provide job monitoring, interface monitoring, and data consistency monitoring:
- Expert Guided Implementation Data Consistency Management
- CQC Interface Management
- CQC Data Consistency Management
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 to implement job, interface, and consistency monitoring.
Confidential Cross Application Business 114/120

Process Analysis
19 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 fewer than 20 sessions.
In this section, a "week" is from Monday to Sunday. The date displayed is the Sunday of the week.
-
19.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.
Confidential Trend Analysis 115/120

-
19.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.
No Transaction Code Load (%)

Transaction 1 FBL3N 25,2
Transaction 2 IDCP 8,0
Transaction 3 FBL5N 7,3
Transaction 4 ZF02 6,5
Transaction 5 SESSION_MANAGER 5,3


-
19.3 System Operation
-
The following diagram or table shows important KPIs for system operation.
-
19.4 Hardware Capacity
-
Report time frame: Service data was collected starting at 09.10.2023 15:00:21. This took 16 minutes.
You can see sample SAP EarlyWatch Alert reports on SAP Support Portal at SAP EarlyWatch Alert -> Sample Reports.
For general information about SAP EarlyWatch Alert, see SAP Note 1257308 .
About System And Solution Manager

-
System No. Of Target System 850737455
Solution Manager System MSA

Solution Manager Version SOLUTION MANAGER 7.2
Service Tool 720 SP25
Service Content Update On 23.06.2023

SPP - PAR ABAP - Very Critical (Red) - EWA

Uploaded by

Copyright:

Available Formats

SPP - PAR ABAP - Very Critical (Red) - EWA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SPP - PAR ABAP - Very Critical (Red) - EWA

Uploaded by

Copyright:

Available Formats

Service Report

SAP System ID SPP

Processed on SAP Solution Manager MSA

Service Tool 720 SP25

Analysis from 02.10.2023 Session No. 0010000000954

Alerts Decisive For Red Report

Confidential Service Summary 2/120

Confidential Service Summary 4/120

Confidential Landscape 5/120

3 Service Data Quality and Service Readiness

Rating Check Performed

Confidential Service Data Quality and Service 6/120

Confidential Service Data Quality and Service 7/120

4 Software Configuration for SPP

SAP NetWeaver Version End of Mainstream Maintenance Status

Confidential Software Configuration for SPP 8/120

Confidential Software Configuration for SPP 9/120

SAP Note Description

Confidential Software Configuration for SPP 11/120

Confidential Software Configuration for SPP 12/120

Confidential Hardware Capacity 13/120

6 Workload of System SPP

Response Time Components In Hours

Confidential Workload of System SPP 14/120

Confidential Workload of System SPP 16/120

7 Performance Overview SPP

Confidential Performance Overview SPP 17/120

Confidential Performance Overview SPP 19/120

8 RFC Load by Initiating Action

Top 20 RFC Calls From External Systems - Average Times [ms]

Top 20 RFC Calls From Local System - Average Times [ms]

Confidential RFC Load by Initiating Action 20/120

Confidential RFC Load by Initiating Action 21/120

9 SAP System Operating SPP

We did not detect any problems.

Confidential SAP System Operating SPP 23/120

Confidential SAP System Operating SPP 24/120

Rating Check System ID

Confidential Security 25/120

Deactivate the user account with the SQL statement:

Confidential Security 26/120

Confidential Security 28/120

11 Software Change and Transport

Confidential Software Change and Transport 29/120

Date Objects in Workbench and Relocation Objects in Customizing Objects in Transport of

Rating Item Value Explanation

Confidential Software Change and Transport 31/120

12 Financial Data Quality

12.2.2 Customers with Open Items older than 10 Years old

Confidential Financial Data Quality 34/120

Confidential Financial Data Quality 35/120

13 Data Volume Management (DVM)

Confidential Data Volume Management (DVM) 36/120

14 SAP HANA Database HPP

Hardware Settings - General Data

Hardware Settings - CPU and Memory Data

Operating System Details

HANA Update Information

Disk ID Device ID File system Host Path Usage