SAP SQLM_API_EW_EXTRACTOR Function Module for Extractor for Early Watch
SQLM_API_EW_EXTRACTOR is a standard sqlm api ew extractor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extractor for Early Watch 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 ew extractor FM, simply by entering the name SQLM_API_EW_EXTRACTOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: SQLM_API_EW
Program Name: SAPLSQLM_API_EW
Main Program: SAPLSQLM_API_EW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SQLM_API_EW_EXTRACTOR 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_EW_EXTRACTOR'"Extractor for Early Watch.
EXPORTING
* I_TOPTIMECNT = 100 "
* I_TOPEXECNT = 100 "
* I_MAXAGE = 864000 "
IMPORTING
E_EXCEPTION_TEXT = "
E_SQLM_ACTIVE = "
E_TIMESERIES_ACTIVE = "
TABLES
E_SQLM_RECORDS = "SQL Monitor: Data Record
E_ACTIVITIES = "
IMPORTING Parameters details for SQLM_API_EW_EXTRACTOR
I_TOPTIMECNT -
Data type: IDefault: 100
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TOPEXECNT -
Data type: IDefault: 100
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MAXAGE -
Data type: IDefault: 864000
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SQLM_API_EW_EXTRACTOR
E_EXCEPTION_TEXT -
Data type: SQLM_API_EW_INPUT-EXCEPTION_TEXTOptional: No
Call by Reference: No ( called with pass by value option)
E_SQLM_ACTIVE -
Data type: SQLM_API_EW_INPUT-SQLM_ACTIVEOptional: No
Call by Reference: No ( called with pass by value option)
E_TIMESERIES_ACTIVE -
Data type: SQLM_API_EW_INPUT-TIMESERIES_ACTIVEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SQLM_API_EW_EXTRACTOR
E_SQLM_RECORDS - SQL Monitor: Data Record
Data type: SQLM_API_EW_RECORDOptional: No
Call by Reference: Yes
E_ACTIVITIES -
Data type: SQLM_API_EW_LOG_ENTRYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SQLM_API_EW_EXTRACTOR 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_toptimecnt | TYPE I, " 100 | |||
| lt_e_sqlm_records | TYPE STANDARD TABLE OF SQLM_API_EW_RECORD, " | |||
| lv_e_exception_text | TYPE SQLM_API_EW_INPUT-EXCEPTION_TEXT, " | |||
| lv_i_topexecnt | TYPE I, " 100 | |||
| lt_e_activities | TYPE STANDARD TABLE OF SQLM_API_EW_LOG_ENTRY, " | |||
| lv_e_sqlm_active | TYPE SQLM_API_EW_INPUT-SQLM_ACTIVE, " | |||
| lv_i_maxage | TYPE I, " 864000 | |||
| lv_e_timeseries_active | TYPE SQLM_API_EW_INPUT-TIMESERIES_ACTIVE. " |
|   CALL FUNCTION 'SQLM_API_EW_EXTRACTOR' "Extractor for Early Watch |
| EXPORTING | ||
| I_TOPTIMECNT | = lv_i_toptimecnt | |
| I_TOPEXECNT | = lv_i_topexecnt | |
| I_MAXAGE | = lv_i_maxage | |
| IMPORTING | ||
| E_EXCEPTION_TEXT | = lv_e_exception_text | |
| E_SQLM_ACTIVE | = lv_e_sqlm_active | |
| E_TIMESERIES_ACTIVE | = lv_e_timeseries_active | |
| TABLES | ||
| E_SQLM_RECORDS | = lt_e_sqlm_records | |
| E_ACTIVITIES | = lt_e_activities | |
| . " SQLM_API_EW_EXTRACTOR | ||
ABAP code using 7.40 inline data declarations to call FM SQLM_API_EW_EXTRACTOR
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.| DATA(ld_i_toptimecnt) | = 100. | |||
| "SELECT single EXCEPTION_TEXT FROM SQLM_API_EW_INPUT INTO @DATA(ld_e_exception_text). | ||||
| DATA(ld_i_topexecnt) | = 100. | |||
| "SELECT single SQLM_ACTIVE FROM SQLM_API_EW_INPUT INTO @DATA(ld_e_sqlm_active). | ||||
| DATA(ld_i_maxage) | = 864000. | |||
| "SELECT single TIMESERIES_ACTIVE FROM SQLM_API_EW_INPUT INTO @DATA(ld_e_timeseries_active). | ||||
Search for further information about these or an SAP related objects