SAP MINIALV_TRACE_DISPLAY Function Module for
MINIALV_TRACE_DISPLAY is a standard minialv trace display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 minialv trace display FM, simply by entering the name MINIALV_TRACE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: SKBE
Program Name: SAPLSKBE
Main Program: SAPLSKBE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MINIALV_TRACE_DISPLAY 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 'MINIALV_TRACE_DISPLAY'".
EXPORTING
I_REPORT = "ABAP Program: Current Main Program
* I_VARIANT = "Variant Name
* I_USER = SY-UNAME "SAP System, User Logon Name
* I_DATUM = SY-DATUM "Date and Time, Current (Application Server) Date
* I_TYPE = "
* I_DELETE_OPTION = "Character Field Length 1
* I_TRACE_OBJ = "Character Field Length 1
* I_CURRENT = "Character Field Length 1
EXCEPTIONS
NOT_FOUND = 1 WRONG_RELID = 2 NO_REPORT = 3 NO_EXNAME = 4 NO_IMPORT_POSSIBLE = 5
IMPORTING Parameters details for MINIALV_TRACE_DISPLAY
I_REPORT - ABAP Program: Current Main Program
Data type: SYREPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_VARIANT - Variant Name
Data type: RSVAR-VARIANTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_USER - SAP System, User Logon Name
Data type: SYUNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATUM - Date and Time, Current (Application Server) Date
Data type: SYDATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TYPE -
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DELETE_OPTION - Character Field Length 1
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TRACE_OBJ - Character Field Length 1
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CURRENT - Character Field Length 1
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
WRONG_RELID -
Data type:Optional: No
Call by Reference: Yes
NO_REPORT -
Data type:Optional: No
Call by Reference: Yes
NO_EXNAME -
Data type:Optional: No
Call by Reference: Yes
NO_IMPORT_POSSIBLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MINIALV_TRACE_DISPLAY 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_report | TYPE SYREPID, " | |||
| lv_not_found | TYPE SYREPID, " | |||
| lv_i_variant | TYPE RSVAR-VARIANT, " | |||
| lv_wrong_relid | TYPE RSVAR, " | |||
| lv_i_user | TYPE SYUNAME, " SY-UNAME | |||
| lv_no_report | TYPE SYUNAME, " | |||
| lv_i_datum | TYPE SYDATUM, " SY-DATUM | |||
| lv_no_exname | TYPE SYDATUM, " | |||
| lv_i_type | TYPE CHAR01, " | |||
| lv_no_import_possible | TYPE CHAR01, " | |||
| lv_i_delete_option | TYPE CHAR01, " | |||
| lv_i_trace_obj | TYPE CHAR01, " | |||
| lv_i_current | TYPE CHAR01. " |
|   CALL FUNCTION 'MINIALV_TRACE_DISPLAY' " |
| EXPORTING | ||
| I_REPORT | = lv_i_report | |
| I_VARIANT | = lv_i_variant | |
| I_USER | = lv_i_user | |
| I_DATUM | = lv_i_datum | |
| I_TYPE | = lv_i_type | |
| I_DELETE_OPTION | = lv_i_delete_option | |
| I_TRACE_OBJ | = lv_i_trace_obj | |
| I_CURRENT | = lv_i_current | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| WRONG_RELID = 2 | ||
| NO_REPORT = 3 | ||
| NO_EXNAME = 4 | ||
| NO_IMPORT_POSSIBLE = 5 | ||
| . " MINIALV_TRACE_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM MINIALV_TRACE_DISPLAY
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 VARIANT FROM RSVAR INTO @DATA(ld_i_variant). | ||||
| DATA(ld_i_user) | = SY-UNAME. | |||
| DATA(ld_i_datum) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects