SAP SUBST_GET_SYSTEM_STATUS Function Module for Module for Determining System Status for Upgrade, Add-on Update









SUBST_GET_SYSTEM_STATUS is a standard subst get system status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Module for Determining System Status for Upgrade, Add-on Update 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 subst get system status FM, simply by entering the name SUBST_GET_SYSTEM_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUGX
Program Name: SAPLSUGX
Main Program: SAPLSUGX
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SUBST_GET_SYSTEM_STATUS 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 'SUBST_GET_SYSTEM_STATUS'"Module for Determining System Status for Upgrade, Add-on Update
 IMPORTING
   EV_NORMAL_DEVELOPMENT =  "
   EV_STATUS =  "Status of upgrade (fixed values domain PUTSTATUS)
   EV_TYPE =  "Type of upgrade (fixed values domain PUTTYPE)
   EV_NEWRELEASE =  "Target release
   EV_STARTDATE =  "Start Date
   EV_STARTTIME =  "Start Time
   EV_ENDDATE =  "End Date
   EV_ENDTIME =  "End Time
   EV_OLDRELEASE =  "Source Release
.



EXPORTING Parameters details for SUBST_GET_SYSTEM_STATUS

EV_NORMAL_DEVELOPMENT -

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

EV_STATUS - Status of upgrade (fixed values domain PUTSTATUS)

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

EV_TYPE - Type of upgrade (fixed values domain PUTTYPE)

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

EV_NEWRELEASE - Target release

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

EV_STARTDATE - Start Date

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

EV_STARTTIME - Start Time

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

EV_ENDDATE - End Date

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

EV_ENDTIME - End Time

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

EV_OLDRELEASE - Source Release

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

Copy and paste ABAP code example for SUBST_GET_SYSTEM_STATUS 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_ev_normal_development  TYPE SUGX_FPARA-BOOLFLAG, "   
lv_ev_status  TYPE UVERS-PUTSTATUS, "   
lv_ev_type  TYPE UVERS-PUTTYPE, "   
lv_ev_newrelease  TYPE UVERS-NEWRELEASE, "   
lv_ev_startdate  TYPE UVERS-STARTDATE, "   
lv_ev_starttime  TYPE UVERS-STARTTIME, "   
lv_ev_enddate  TYPE UVERS-ENDDATE, "   
lv_ev_endtime  TYPE UVERS-ENDTIME, "   
lv_ev_oldrelease  TYPE UVERS-OLDRELEASE. "   

  CALL FUNCTION 'SUBST_GET_SYSTEM_STATUS'  "Module for Determining System Status for Upgrade, Add-on Update
    IMPORTING
         EV_NORMAL_DEVELOPMENT = lv_ev_normal_development
         EV_STATUS = lv_ev_status
         EV_TYPE = lv_ev_type
         EV_NEWRELEASE = lv_ev_newrelease
         EV_STARTDATE = lv_ev_startdate
         EV_STARTTIME = lv_ev_starttime
         EV_ENDDATE = lv_ev_enddate
         EV_ENDTIME = lv_ev_endtime
         EV_OLDRELEASE = lv_ev_oldrelease
. " SUBST_GET_SYSTEM_STATUS




ABAP code using 7.40 inline data declarations to call FM SUBST_GET_SYSTEM_STATUS

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 BOOLFLAG FROM SUGX_FPARA INTO @DATA(ld_ev_normal_development).
 
"SELECT single PUTSTATUS FROM UVERS INTO @DATA(ld_ev_status).
 
"SELECT single PUTTYPE FROM UVERS INTO @DATA(ld_ev_type).
 
"SELECT single NEWRELEASE FROM UVERS INTO @DATA(ld_ev_newrelease).
 
"SELECT single STARTDATE FROM UVERS INTO @DATA(ld_ev_startdate).
 
"SELECT single STARTTIME FROM UVERS INTO @DATA(ld_ev_starttime).
 
"SELECT single ENDDATE FROM UVERS INTO @DATA(ld_ev_enddate).
 
"SELECT single ENDTIME FROM UVERS INTO @DATA(ld_ev_endtime).
 
"SELECT single OLDRELEASE FROM UVERS INTO @DATA(ld_ev_oldrelease).
 


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!