SAP ESH_QL_AGGREGATE_LOG Function Module for Query Log Aggregation: Execute (in NEW TASK)
ESH_QL_AGGREGATE_LOG is a standard esh ql aggregate log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Query Log Aggregation: Execute (in NEW TASK) 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 esh ql aggregate log FM, simply by entering the name ESH_QL_AGGREGATE_LOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: ESH_QL_AGGREGATION
Program Name: SAPLESH_QL_AGGREGATION
Main Program: SAPLESH_QL_AGGREGATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ESH_QL_AGGREGATE_LOG 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 'ESH_QL_AGGREGATE_LOG'"Query Log Aggregation: Execute (in NEW TASK).
EXPORTING
IV_JOBSTART_STATUS = "Query Log Aggregation Last Execution Status
* IV_USERBASED = ABAP_TRUE "Personalized Query Log Aggregation
* IV_AGGREGATION_USER = "Personalization User
IMPORTING Parameters details for ESH_QL_AGGREGATE_LOG
IV_JOBSTART_STATUS - Query Log Aggregation Last Execution Status
Data type: ESH_E_QL_AGGREG_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
IV_USERBASED - Personalized Query Log Aggregation
Data type: ESH_E_QL_CUST_QL_AGGREG_USRBSDDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_AGGREGATION_USER - Personalization User
Data type: ESH_E_CM_PERS_USEROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ESH_QL_AGGREGATE_LOG 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_iv_jobstart_status | TYPE ESH_E_QL_AGGREG_STATUS, " | |||
| lv_iv_userbased | TYPE ESH_E_QL_CUST_QL_AGGREG_USRBSD, " ABAP_TRUE | |||
| lv_iv_aggregation_user | TYPE ESH_E_CM_PERS_USER. " |
|   CALL FUNCTION 'ESH_QL_AGGREGATE_LOG' "Query Log Aggregation: Execute (in NEW TASK) |
| EXPORTING | ||
| IV_JOBSTART_STATUS | = lv_iv_jobstart_status | |
| IV_USERBASED | = lv_iv_userbased | |
| IV_AGGREGATION_USER | = lv_iv_aggregation_user | |
| . " ESH_QL_AGGREGATE_LOG | ||
ABAP code using 7.40 inline data declarations to call FM ESH_QL_AGGREGATE_LOG
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_iv_userbased) | = ABAP_TRUE. | |||
Search for further information about these or an SAP related objects