SAP STU3_GET_MEPL Function Module for Get output of 'DIAGNOSE DISPLAY MEPL' (installed PTF's)
STU3_GET_MEPL is a standard stu3 get mepl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get output of 'DIAGNOSE DISPLAY MEPL' (installed PTF's) 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 stu3 get mepl FM, simply by entering the name STU3_GET_MEPL into the relevant SAP transaction such as SE37 or SE38.
Function Group: STU3_CONFIG
Program Name: SAPLSTU3_CONFIG
Main Program: SAPLSTU3_CONFIG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function STU3_GET_MEPL 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 'STU3_GET_MEPL'"Get output of 'DIAGNOSE DISPLAY MEPL' (installed PTF's).
EXPORTING
* REMOTE_DBCON = "Logical name for a database connection
IMPORTING
SYSPRINT_T = "Table type for DB2/390 table SYSIBM.SYSPRINT
EXCEPTIONS
DSNUTILS_ERROR = 1 ADBC_SQL_ERROR = 2
IMPORTING Parameters details for STU3_GET_MEPL
REMOTE_DBCON - Logical name for a database connection
Data type: DBCON-CON_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for STU3_GET_MEPL
SYSPRINT_T - Table type for DB2/390 table SYSIBM.SYSPRINT
Data type: DB2SYSPRNT_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
DSNUTILS_ERROR -
Data type:Optional: No
Call by Reference: Yes
ADBC_SQL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for STU3_GET_MEPL 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_sysprint_t | TYPE DB2SYSPRNT_TAB, " | |||
| lv_remote_dbcon | TYPE DBCON-CON_NAME, " | |||
| lv_dsnutils_error | TYPE DBCON, " | |||
| lv_adbc_sql_error | TYPE DBCON. " |
|   CALL FUNCTION 'STU3_GET_MEPL' "Get output of 'DIAGNOSE DISPLAY MEPL' (installed PTF's) |
| EXPORTING | ||
| REMOTE_DBCON | = lv_remote_dbcon | |
| IMPORTING | ||
| SYSPRINT_T | = lv_sysprint_t | |
| EXCEPTIONS | ||
| DSNUTILS_ERROR = 1 | ||
| ADBC_SQL_ERROR = 2 | ||
| . " STU3_GET_MEPL | ||
ABAP code using 7.40 inline data declarations to call FM STU3_GET_MEPL
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.| "SELECT single CON_NAME FROM DBCON INTO @DATA(ld_remote_dbcon). | ||||
Search for further information about these or an SAP related objects