SAP ADMINISTRATION_WINDOW Function Module for Window with management information









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

Function Group: IADM
Program Name: SAPLIADM
Main Program:
Appliation area: I
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ADMINISTRATION_WINDOW 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 'ADMINISTRATION_WINDOW'"Window with management information
  EXPORTING
*  CUA_TITLE = ' ' "CUA_Titel, default: 'Management in
*  TZONE =  "
*  TZONE_ACTIVE =  "
   ERDAT =  "Date at which the object was creat
*  ERUHR = '000000' "
*  ERUHR_ACTIVE = ' ' "
   ERNAM =  "Name of the user who created the o
   AEDAT =  "Date at which the object was last
*  AEUHR = '000000' "
*  AEUHR_ACTIVE = ' ' "
   AENAM =  "Name of the user who last changed
.



IMPORTING Parameters details for ADMINISTRATION_WINDOW

CUA_TITLE - CUA_Titel, default: 'Management in

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

TZONE -

Data type: RIADM-TZONE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TZONE_ACTIVE -

Data type: IREF-IIND
Optional: Yes
Call by Reference: No ( called with pass by value option)

ERDAT - Date at which the object was creat

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

ERUHR -

Data type: RIADM-ERUHR
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ERUHR_ACTIVE -

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

ERNAM - Name of the user who created the o

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

AEDAT - Date at which the object was last

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

AEUHR -

Data type: RIADM-AEUHR
Default: '000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

AEUHR_ACTIVE -

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

AENAM - Name of the user who last changed

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

Copy and paste ABAP code example for ADMINISTRATION_WINDOW 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_cua_title  TYPE STRING, "   SPACE
lv_tzone  TYPE RIADM-TZONE, "   
lv_tzone_active  TYPE IREF-IIND, "   
lv_erdat  TYPE RIADM-ERDAT, "   
lv_eruhr  TYPE RIADM-ERUHR, "   '000000'
lv_eruhr_active  TYPE IREF-IIND, "   SPACE
lv_ernam  TYPE RIADM-ERNAM, "   
lv_aedat  TYPE RIADM-AEDAT, "   
lv_aeuhr  TYPE RIADM-AEUHR, "   '000000'
lv_aeuhr_active  TYPE IREF-IIND, "   SPACE
lv_aenam  TYPE RIADM-AENAM. "   

  CALL FUNCTION 'ADMINISTRATION_WINDOW'  "Window with management information
    EXPORTING
         CUA_TITLE = lv_cua_title
         TZONE = lv_tzone
         TZONE_ACTIVE = lv_tzone_active
         ERDAT = lv_erdat
         ERUHR = lv_eruhr
         ERUHR_ACTIVE = lv_eruhr_active
         ERNAM = lv_ernam
         AEDAT = lv_aedat
         AEUHR = lv_aeuhr
         AEUHR_ACTIVE = lv_aeuhr_active
         AENAM = lv_aenam
. " ADMINISTRATION_WINDOW




ABAP code using 7.40 inline data declarations to call FM ADMINISTRATION_WINDOW

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.

DATA(ld_cua_title) = ' '.
 
"SELECT single TZONE FROM RIADM INTO @DATA(ld_tzone).
 
"SELECT single IIND FROM IREF INTO @DATA(ld_tzone_active).
 
"SELECT single ERDAT FROM RIADM INTO @DATA(ld_erdat).
 
"SELECT single ERUHR FROM RIADM INTO @DATA(ld_eruhr).
DATA(ld_eruhr) = '000000'.
 
"SELECT single IIND FROM IREF INTO @DATA(ld_eruhr_active).
DATA(ld_eruhr_active) = ' '.
 
"SELECT single ERNAM FROM RIADM INTO @DATA(ld_ernam).
 
"SELECT single AEDAT FROM RIADM INTO @DATA(ld_aedat).
 
"SELECT single AEUHR FROM RIADM INTO @DATA(ld_aeuhr).
DATA(ld_aeuhr) = '000000'.
 
"SELECT single IIND FROM IREF INTO @DATA(ld_aeuhr_active).
DATA(ld_aeuhr_active) = ' '.
 
"SELECT single AENAM FROM RIADM INTO @DATA(ld_aenam).
 


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!