SAP SQLM_API_GET_FEATURES Function Module for SQL Monitor API: Get Available Features
SQLM_API_GET_FEATURES is a standard sqlm api get features SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SQL Monitor API: Get Available Features processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for sqlm api get features FM, simply by entering the name SQLM_API_GET_FEATURES into the relevant SAP transaction such as SE37 or SE38.
Function Group: SQLM_API
Program Name: SAPLSQLM_API
Main Program: SAPLSQLM_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SQLM_API_GET_FEATURES pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'SQLM_API_GET_FEATURES'"SQL Monitor API: Get Available Features.
EXPORTING
* I_FEATURE_NAME = "
IMPORTING
E_AVAILABLE_FEATURES = "
IMPORTING Parameters details for SQLM_API_GET_FEATURES
I_FEATURE_NAME -
Data type: SQLM_API_FEATURE_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SQLM_API_GET_FEATURES
E_AVAILABLE_FEATURES -
Data type: SQLM_API_FEATURESOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SQLM_API_GET_FEATURES Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_feature_name | TYPE SQLM_API_FEATURE_NAME, " | |||
| lv_e_available_features | TYPE SQLM_API_FEATURES. " |
|   CALL FUNCTION 'SQLM_API_GET_FEATURES' "SQL Monitor API: Get Available Features |
| EXPORTING | ||
| I_FEATURE_NAME | = lv_i_feature_name | |
| IMPORTING | ||
| E_AVAILABLE_FEATURES | = lv_e_available_features | |
| . " SQLM_API_GET_FEATURES | ||
ABAP code using 7.40 inline data declarations to call FM SQLM_API_GET_FEATURES
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects