SAP STATUS_ANZEIGEN Function Module for Display status information









STATUS_ANZEIGEN is a standard status anzeigen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display status information 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 status anzeigen FM, simply by entering the name STATUS_ANZEIGEN into the relevant SAP transaction such as SE37 or SE38.

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



Function STATUS_ANZEIGEN 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 'STATUS_ANZEIGEN'"Display status information
EXPORTING
DYNPPROG = "Current screen program
DYNPRO = "Current screen
KZ_SYDYN = "
PFKEY = "Current CUA status
PROGRAMM = "Current program as in CUA status
REPORT = "Current report in report processing
* SUBPROG = ' ' "
* SUBDYNP = ' ' "
.



IMPORTING Parameters details for STATUS_ANZEIGEN

DYNPPROG - Current screen program

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

DYNPRO - Current screen

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

KZ_SYDYN -

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

PFKEY - Current CUA status

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

PROGRAMM - Current program as in CUA status

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

REPORT - Current report in report processing

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

SUBPROG -

Data type: PHELP-DYNPPROG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUBDYNP -

Data type: PHELP-DYNPRO
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for STATUS_ANZEIGEN 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_dynpprog  TYPE PHELP-DYNPPROG, "   
lv_dynpro  TYPE PHELP-DYNPRO, "   
lv_kz_sydyn  TYPE PHELP-KZ_SYDYN, "   
lv_pfkey  TYPE PHELP, "   
lv_programm  TYPE PHELP-PROGRAMM, "   
lv_report  TYPE PHELP-REPORT, "   
lv_subprog  TYPE PHELP-DYNPPROG, "   SPACE
lv_subdynp  TYPE PHELP-DYNPRO. "   SPACE

  CALL FUNCTION 'STATUS_ANZEIGEN'  "Display status information
    EXPORTING
         DYNPPROG = lv_dynpprog
         DYNPRO = lv_dynpro
         KZ_SYDYN = lv_kz_sydyn
         PFKEY = lv_pfkey
         PROGRAMM = lv_programm
         REPORT = lv_report
         SUBPROG = lv_subprog
         SUBDYNP = lv_subdynp
. " STATUS_ANZEIGEN




ABAP code using 7.40 inline data declarations to call FM STATUS_ANZEIGEN

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 DYNPPROG FROM PHELP INTO @DATA(ld_dynpprog).
 
"SELECT single DYNPRO FROM PHELP INTO @DATA(ld_dynpro).
 
"SELECT single KZ_SYDYN FROM PHELP INTO @DATA(ld_kz_sydyn).
 
 
"SELECT single PROGRAMM FROM PHELP INTO @DATA(ld_programm).
 
"SELECT single REPORT FROM PHELP INTO @DATA(ld_report).
 
"SELECT single DYNPPROG FROM PHELP INTO @DATA(ld_subprog).
DATA(ld_subprog) = ' '.
 
"SELECT single DYNPRO FROM PHELP INTO @DATA(ld_subdynp).
DATA(ld_subdynp) = ' '.
 


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!