Make sure snapshot monitoring is active (read this blog on activation)
Running the tool
To start the tool go to transaction SE38 and start program /SDF/RSLOADANALYSIS.
Selection screen:
Select the date range you want to analyze. The delta factor is normally 10 but bit too low. Increase it for more realistic result. This is factor to conclude if balancing is ok or not. Only 10% difference from average is too idealistic.
The second part is the work process analysis part.
Here you can see how load is distributed over the application servers using the snapshot monitoring statistics. The central instance can be excluded from the load balancing and hence show as ‘not balanced’.
The third part is host machine data.
Here you can see if the servers are having equal CPU power and memory. If no data for a sever: check in ST06 if it is configured properly.
It can be that CPU and memory are identical, but that older infrastructure was used. Then the CPU and mem look the same, but there can still be significant difference in CPU speed and memory speed. To rule this out, run the ABAPMETER tool.
Sometimes SAP users are far away from the server. There is much latency. For a global SAP system this is unavoidable. In some cases there might be a remote location you need to support which has a slow and/or low bandwidth connection.
In that case you best setup the SAP GUI to use
Default is as above. For low speed users, ask them to select the Low Speed Connection.
Before /SDF/SMON_DISPALY is working, you have to set a link to the plotly library. You can do this for all users, or for your personal user by setting a SU3 parameter:
Using /SDF/SMON_DISPLAY
Simply start transaction /SDF/SMON_DISPLAY:
Fill out the measurements you want to see. And the last n minutes. Automatically the results are shown in a separate window:
On table level: Check the table ICFSERVLOC. All active services are marked with an “X” flag.
Checking SICF security settings
Don’t use the old program RSICFCHK (see OSS note 3300857 – Report RSICFCHK shows incomplete result). Use the new SECSTORE transaction. At the start of transaction SECSTORE choose in the check entries section “ICF Service”:
Now hit execute and check the results:
Mass processing
SICF mass processing is done via program RS_ICF_SERV_MASS_PROCESSING.
Logging of SICF changes
To enable logging of SICF changes: switch on table logging for table ICFSERVLOC.
SAP Focused Run offers some nice API’s that you can use and re-use.
API’s available:
LMDB API
Work mode management API
Guided procedure API
Advanced analytics API
LMDB API
The LMDB now has a REST API available to read data in structured way. You can search for hosts, technical systems, software components, installed product versions and instances.
The full specification for this API can be found on this link.
Ad hoc work mode creation via function module
Via function module FM_START_ADHOC_WORKMODE you can create an ad-hoc work mode to stop monitoring for a system. You can start monitoring again by stopping the work mode by calling function module FM_STOP_ADHOC_WORKMODE.
Function module FM_EXTRN_GP_EXEC can be used to call a guided procedure. Unfortunately, you need to pass the GUID of the guided procedure to the function module.
In some cases you need to debug the session of another user. This can be needed for example when you need to solve an issue in ABAP for a FIORI app. The end user is doing his work until the break point is reached. Then you take over the session using the normal debugging tools. The basic principle is explained in OSS note 1919888 – Debugging the applications of another user, and in this SAP help file.
Follow the steps explained in this blog to set up a new custom check. We will use these steps to set up an extra SCI class to check if the AUTHORITY-CHECK statement is added in ABAP code or not.
New SCI check coding
Step 1: create the ZCL_CI_SCAN_AUTH class
In SE24 copy class CL_CI_TEST_FREE_SEARCH to ZCL_CI_SCAN_AUTH. In the attributes of the copied class set C_MY_NAME as variable to ‘ZCL_CI_SCAN_AUTH’. Also set the error code MCODE_0001 to ‘Z001’.
Step 2: redo the CONSTRUCTOR
Goto the constructor of the new class and overwrite the existing code with this code snippit:
In some cases you might be asked on the SAP menu. How it is build up, which transaction codes are in there, who is using SAP menu, and how is using the company created menu. And other questions.