SAP GUI_STATUS_DISPLAY Function Module for









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

Function Group: GUI_STATUS
Program Name: SAPLGUI_STATUS
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GUI_STATUS_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 'GUI_STATUS_DISPLAY'"
  EXPORTING
   IM_GUID =  "
   IM_EXTSTATUS =  "
   IM_MSGID =  "
   IM_MSGNO =  "
   IM_MSGV1 =  "
   IM_MSGV2 =  "
   IM_MSGV3 =  "
   IM_MSGV4 =  "
   IM_APPLOG =  "
   IM_CURRENT =  "
   IM_MSGTXT =  "
   IM_APPLICATION_CATEGORY =  "
   IM_APPLFIELDSHORT1 =  "
   IM_APPLFIELDSHORT2 =  "
   IM_APPLFIELDLONG1 =  "
   IM_CREATED_BY =  "
   IM_APPLSEARCH =  "
   IM_OBJTYP =  "
   IM_OBJID =  "
   IM_COUNTER =  "
   IM_STATUS =  "
   IM_STATUSTEXT =  "
   IM_LOGDATE =  "
   IM_LOGTIME =  "
.



IMPORTING Parameters details for GUI_STATUS_DISPLAY

IM_GUID -

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

IM_EXTSTATUS -

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

IM_MSGID -

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

IM_MSGNO -

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

IM_MSGV1 -

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

IM_MSGV2 -

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

IM_MSGV3 -

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

IM_MSGV4 -

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

IM_APPLOG -

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

IM_CURRENT -

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

IM_MSGTXT -

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

IM_APPLICATION_CATEGORY -

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

IM_APPLFIELDSHORT1 -

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

IM_APPLFIELDSHORT2 -

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

IM_APPLFIELDLONG1 -

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

IM_CREATED_BY -

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

IM_APPLSEARCH -

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

IM_OBJTYP -

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

IM_OBJID -

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

IM_COUNTER -

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

IM_STATUS -

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

IM_STATUSTEXT -

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

IM_LOGDATE -

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

IM_LOGTIME -

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

Copy and paste ABAP code example for GUI_STATUS_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_im_guid  TYPE SYSUUID_C, "   
lv_im_extstatus  TYPE STATUSEXT, "   
lv_im_msgid  TYPE SYMSGID, "   
lv_im_msgno  TYPE SYMSGNO, "   
lv_im_msgv1  TYPE SYMSGV, "   
lv_im_msgv2  TYPE SYMSGV, "   
lv_im_msgv3  TYPE SYMSGV, "   
lv_im_msgv4  TYPE SYMSGV, "   
lv_im_applog  TYPE APPLOG, "   
lv_im_current  TYPE FIEBCURRENT, "   
lv_im_msgtxt  TYPE NATXT, "   
lv_im_application_category  TYPE FIEB_APPLICATION_CATEGORY, "   
lv_im_applfieldshort1  TYPE FIEB_APPLFIELDSHORT, "   
lv_im_applfieldshort2  TYPE FIEB_APPLFIELDSHORT, "   
lv_im_applfieldlong1  TYPE FIEB_APPLFIELDLONG, "   
lv_im_created_by  TYPE UNAME, "   
lv_im_applsearch  TYPE FIEB_APPLSEARCH, "   
lv_im_objtyp  TYPE REFOBJTYP, "   
lv_im_objid  TYPE REFOBJUID, "   
lv_im_counter  TYPE STACOUNT, "   
lv_im_status  TYPE FIEBSTATUS, "   
lv_im_statustext  TYPE FIEBSTATUSTEXT, "   
lv_im_logdate  TYPE LOGDATE, "   
lv_im_logtime  TYPE LOGTIME. "   

  CALL FUNCTION 'GUI_STATUS_DISPLAY'  "
    EXPORTING
         IM_GUID = lv_im_guid
         IM_EXTSTATUS = lv_im_extstatus
         IM_MSGID = lv_im_msgid
         IM_MSGNO = lv_im_msgno
         IM_MSGV1 = lv_im_msgv1
         IM_MSGV2 = lv_im_msgv2
         IM_MSGV3 = lv_im_msgv3
         IM_MSGV4 = lv_im_msgv4
         IM_APPLOG = lv_im_applog
         IM_CURRENT = lv_im_current
         IM_MSGTXT = lv_im_msgtxt
         IM_APPLICATION_CATEGORY = lv_im_application_category
         IM_APPLFIELDSHORT1 = lv_im_applfieldshort1
         IM_APPLFIELDSHORT2 = lv_im_applfieldshort2
         IM_APPLFIELDLONG1 = lv_im_applfieldlong1
         IM_CREATED_BY = lv_im_created_by
         IM_APPLSEARCH = lv_im_applsearch
         IM_OBJTYP = lv_im_objtyp
         IM_OBJID = lv_im_objid
         IM_COUNTER = lv_im_counter
         IM_STATUS = lv_im_status
         IM_STATUSTEXT = lv_im_statustext
         IM_LOGDATE = lv_im_logdate
         IM_LOGTIME = lv_im_logtime
. " GUI_STATUS_DISPLAY




ABAP code using 7.40 inline data declarations to call FM GUI_STATUS_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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!