SAP ME_ABAPSTACK_DISPLAY Function Module for









ME_ABAPSTACK_DISPLAY is a standard me abapstack 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 me abapstack display FM, simply by entering the name ME_ABAPSTACK_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

Function Group: ME_CENTRAL_TRACING
Program Name: SAPLME_CENTRAL_TRACING
Main Program: SAPLME_CENTRAL_TRACING
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ME_ABAPSTACK_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 'ME_ABAPSTACK_DISPLAY'"
EXPORTING
DIALOG_MODE = "

TABLES
MT_TOOL_INFO = "

EXCEPTIONS
INVALID_DIALOG_MODE = 1 MT_TOOL_INFO_MISSING = 2 TOOL_INTENTIONALLY_ABORTED = 3 DONT_START_TOOL_AGAIN = 4
.



IMPORTING Parameters details for ME_ABAPSTACK_DISPLAY

DIALOG_MODE -

Data type: ALTYPES-CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ME_ABAPSTACK_DISPLAY

MT_TOOL_INFO -

Data type: ALTLEXDESC
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_DIALOG_MODE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

MT_TOOL_INFO_MISSING -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOOL_INTENTIONALLY_ABORTED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DONT_START_TOOL_AGAIN -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ME_ABAPSTACK_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_dialog_mode  TYPE ALTYPES-CHAR1, "   
lt_mt_tool_info  TYPE STANDARD TABLE OF ALTLEXDESC, "   
lv_invalid_dialog_mode  TYPE ALTLEXDESC, "   
lv_mt_tool_info_missing  TYPE ALTLEXDESC, "   
lv_tool_intentionally_aborted  TYPE ALTLEXDESC, "   
lv_dont_start_tool_again  TYPE ALTLEXDESC. "   

  CALL FUNCTION 'ME_ABAPSTACK_DISPLAY'  "
    EXPORTING
         DIALOG_MODE = lv_dialog_mode
    TABLES
         MT_TOOL_INFO = lt_mt_tool_info
    EXCEPTIONS
        INVALID_DIALOG_MODE = 1
        MT_TOOL_INFO_MISSING = 2
        TOOL_INTENTIONALLY_ABORTED = 3
        DONT_START_TOOL_AGAIN = 4
. " ME_ABAPSTACK_DISPLAY




ABAP code using 7.40 inline data declarations to call FM ME_ABAPSTACK_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 CHAR1 FROM ALTYPES INTO @DATA(ld_dialog_mode).
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!