SAP SQLM_API_MERGE_SQLM_REQ_DATA Function Module for SQL Monitor API: Merge Request Data and Standard SQLM Data
SQLM_API_MERGE_SQLM_REQ_DATA is a standard sqlm api merge sqlm req data 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: Merge Request Data and Standard SQLM Data 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 merge sqlm req data FM, simply by entering the name SQLM_API_MERGE_SQLM_REQ_DATA 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 Warning: Undefined array key "UPDATE" in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 212
Update:
Function SQLM_API_MERGE_SQLM_REQ_DATA 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. Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 267 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 296 Warning: Undefined variable $pimport in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 304 Warning: Undefined variable $pidet in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 305 Warning: Undefined variable $ai in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 307 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 267 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 296 Warning: Undefined variable $pe in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 312 Warning: Undefined variable $pedet in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 313 Warning: Undefined variable $ae in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 314 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 267 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 296 Warning: Undefined variable $px in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 337 Warning: Undefined variable $pxdet in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 338 Warning: Undefined variable $ax in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 339 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 267 Warning: Trying to access array offset on value of type null in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 296 Warning: Undefined variable $pattern in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 347 Warning: Undefined variable $abapcall in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 349CALL FUNCTION 'SQLM_API_MERGE_SQLM_REQ_DATA'"SQL Monitor API: Merge Request Data and Standard SQLM Data.
EXPORTING
I_SQLM_RECORDS = "
I_SQLM_REQ_RECORDS = "
IMPORTING
E_MERGED_RECORDS = "
EXCEPTIONS
SQLM_API_FAILURE = 1
Warning: Undefined variable $idoc in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 395 Warning: Undefined variable $exitfms in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 397 Warning: Undefined variable $custfunc in /customers/3/8/f/se80.co.uk/httpd.www/builder/sap-function-modules/index.php on line 399 Warning: file(/customers/3/8/f/se80.co.uk/httpd.www/sap/fms/sqlm_api_merge_sqlm_req_data/sqlm_api_merge_sqlm_req_data.txt): Failed to open stream: No such file or directory in /customers/3/8/f/se80.co.uk/httpd.www/page/php/functions-noconn.php on line 575 Warning: foreach() argument must be of type array|object, bool given in /customers/3/8/f/se80.co.uk/httpd.www/page/php/functions-noconn.php on line 595 Warning: Undefined variable $endtag in /customers/3/8/f/se80.co.uk/httpd.www/page/php/functions-noconn.php on line 859
IMPORTING Parameters details for SQLM_API_MERGE_SQLM_REQ_DATA
I_SQLM_RECORDS -
Data type: SQLM_API_RECORDSOptional: No
Call by Reference: No ( called with pass by value option)
I_SQLM_REQ_RECORDS -
Data type: SQLM_API_REQ_RECORDSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SQLM_API_MERGE_SQLM_REQ_DATA
E_MERGED_RECORDS -
Data type: SQLM_API_MERGED_RECORDSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SQLM_API_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SQLM_API_MERGE_SQLM_REQ_DATA 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_sqlm_records | TYPE SQLM_API_RECORDS, " | |||
| lv_e_merged_records | TYPE SQLM_API_MERGED_RECORDS, " | |||
| lv_sqlm_api_failure | TYPE SQLM_API_MERGED_RECORDS, " | |||
| lv_i_sqlm_req_records | TYPE SQLM_API_REQ_RECORDS. " |
| CALL FUNCTION 'SQLM_API_MERGE_SQLM_REQ_DATA' "SQL Monitor API: Merge Request Data and Standard SQLM Data |
| EXPORTING | ||
| I_SQLM_RECORDS | = lv_i_sqlm_records | |
| I_SQLM_REQ_RECORDS | = lv_i_sqlm_req_records | |
| IMPORTING | ||
| E_MERGED_RECORDS | = lv_e_merged_records | |
| EXCEPTIONS | ||
| SQLM_API_FAILURE = 1 | ||
| . " SQLM_API_MERGE_SQLM_REQ_DATA | ||
ABAP code using 7.40 inline data declarations to call FM SQLM_API_MERGE_SQLM_REQ_DATA
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