SAP SUBST_GET_UPGRADE_INFO Function Module for Statusinformationen über das zuletzt bzw. gerade laufende Upgrade
SUBST_GET_UPGRADE_INFO is a standard subst get upgrade info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Statusinformationen über das zuletzt bzw. gerade laufende Upgrade 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 upgrade info FM, simply by entering the name SUBST_GET_UPGRADE_INFO 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_UPGRADE_INFO 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_UPGRADE_INFO'"Statusinformationen über das zuletzt bzw. gerade laufende Upgrade.
EXPORTING
* IV_BUFFERED = ' ' "
IMPORTING
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
EXCEPTIONS
UNDEFINED_RELEASE = 1
IMPORTING Parameters details for SUBST_GET_UPGRADE_INFO
IV_BUFFERED -
Data type: SUGS_FPARA-BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUBST_GET_UPGRADE_INFO
EV_STATUS - Status of upgrade (fixed values domain PUTSTATUS)
Data type: UVERS-PUTSTATUSOptional: No
Call by Reference: No ( called with pass by value option)
EV_TYPE - Type of upgrade (fixed values domain PUTTYPE)
Data type: UVERS-PUTTYPEOptional: No
Call by Reference: No ( called with pass by value option)
EV_NEWRELEASE - Target Release
Data type: UVERS-NEWRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
EV_STARTDATE - Start Date
Data type: UVERS-STARTDATEOptional: No
Call by Reference: No ( called with pass by value option)
EV_STARTTIME - Start Time
Data type: UVERS-STARTTIMEOptional: No
Call by Reference: No ( called with pass by value option)
EV_ENDDATE - End Date
Data type: UVERS-ENDDATEOptional: No
Call by Reference: No ( called with pass by value option)
EV_ENDTIME - End Time
Data type: UVERS-ENDTIMEOptional: No
Call by Reference: No ( called with pass by value option)
EV_OLDRELEASE - Source Release
Data type: UVERS-OLDRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNDEFINED_RELEASE - Table SVERS does not contain any entries
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUBST_GET_UPGRADE_INFO 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_status | TYPE UVERS-PUTSTATUS, " | |||
| lv_iv_buffered | TYPE SUGS_FPARA-BOOL, " SPACE | |||
| lv_undefined_release | TYPE SUGS_FPARA, " | |||
| 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_UPGRADE_INFO' "Statusinformationen über das zuletzt bzw. gerade laufende Upgrade |
| EXPORTING | ||
| IV_BUFFERED | = lv_iv_buffered | |
| IMPORTING | ||
| 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 | |
| EXCEPTIONS | ||
| UNDEFINED_RELEASE = 1 | ||
| . " SUBST_GET_UPGRADE_INFO | ||
ABAP code using 7.40 inline data declarations to call FM SUBST_GET_UPGRADE_INFO
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 PUTSTATUS FROM UVERS INTO @DATA(ld_ev_status). | ||||
| "SELECT single BOOL FROM SUGS_FPARA INTO @DATA(ld_iv_buffered). | ||||
| DATA(ld_iv_buffered) | = ' '. | |||
| "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