EWA - Expensive SQL Statements Review Methods

Overview


Expensive SQL Statements

Expensive SQL Statements displays detailed information about the most expensive SQL statements
For a complete explanation of the rating for SQL Server - Refer to SAP Note 2021756 - MSSQL Expensive SQL statements check. Rating strategy for EarlyWatch Alert.
For an explanation of the rating strategy for Oracle - Refer to SAP Note 551646 - Oracle SQL check rating strategy for EarlyWatch Alert.

Assistance with resolving Expensive SQL Statements:

  1. Create a SAP Technical Performance Optimization (TPO) service on Solution Manager  - This is a database tuning service that will look at the current state of your database and make recommendations in regards to performance optimizations, index.
    Refer to the wiki link https://wiki.scn.sap.com/wiki/x/p4fHGg for steps how to create a TPO Self Delivered Service.
  2. If you require further assistance, use the component SV-PERF. Upload the EWA report and the TPO report. 

Expensive SQL Statements incomplete or missing in the EWA report

  1. Ensure the latest add-on ST-PI is on the managed system by running ST13 - RTCCTOOL.
  2. Verify the latest add-on  ST-PI on Solution Manager by running ST13 - RTCCTOOL (it is very important Solution Manager is also using the latest ST-PI).
  3. On Solution Manager, ensure the latest Service Content is on the system using transaction AGS_UPDATE.
  4. Check SAP Note 2180792 - EWA: No Source Code in Expensive Statement section.
  5. Refer to SAP Note 2475365 - EWA report is missing sections "Database server load from expensive SQL statements" and "Database and ABAP Load Optimization"
  6. If the subsequent EWA is still not correct, use component SV-SMG-SER-EWA.

2665195 - How to check your DMIS support package? - SLT

Symptom

  • What is my SLT package?
  • What is my S/4 HANA level?
  • How to check your S/4 Core level?

Environment

SAP Landscape Transformation replication server

Resolution

  1. Select the 'System' button at the top of your SAP GUI screen
    2018-07-03_12-17-44.png
  2. Select 'Status' from the drop down
    2018-07-03_12-19-05.png
  3. Select the 'Details' button under the 'SAP System data' section
    2018-07-03_12-20-17.png 
  4. Under the Component colum you will see either DMIS or S/4 Core
    2018-07-03_12-21-30.png

Configuring Web Services in SOA Manager

Concept
You can use SOA Manager for the complete configuration of service providers and consumer proxies for a local system. The following task areas are described:
Prerequisites
  • You have Administrator authorization.
    More information: Checking Roles
  • In transaction SICF, you have activated the following nodes:
    • /sap/bc/srt (including sub nodes)
    • /sap/bc/webdynpro/sap/appl_soap_management
    You may have to activate the general Web Dynpro ICF services to ensure that the ABAP Web Dynpro runtime environment works. For more information, see Active Services in SICF.
  • The service and proxy definitions that you want to configure are available as development objects in the back-end system.
  • If you want to work with SOA Manager in a system landscape, you need to configure communication between ABAP systems.
    More information: Setting Up the SOA Manager
Procedure
To start SOA Manager:
  • Use the transaction code SOAMANAGER.
    Alternatively; you can start SOA Manager in an Internet browser using the following link:
    http://<host>:<port>/sap/bc/webdynpro/sap/appl_soap_management?sap-language=<logon language>
    The main screen is displayed, with tabs for the function groups. The main function groups are:
    Service Administration
    Functionality to set up configuration to support business processes with Web services.
    This functionality is intended for business administrators who manage business processes across systems in a system landscape.
    Technical Administration
    This functionality is intended for technical system administrators who set up connections between systems and who manage the security settings in a system landscape.
Note
SOA Manager is a WebDynpro ABAP application. For this reason, its ICF node ( /sap/bc/webdynpro/sap/appl_soap_management) needs to be active.
To check that the ICF node for SOA Manager is active, you can use transaction SICF.
More information: SAP Note 1124553 Information published on SAP site