SAP SUBST_GET_SAPRELEASE Function Module for Ermittle das Aktuelle SAP-Release (svers-version(3))
SUBST_GET_SAPRELEASE is a standard subst get saprelease SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ermittle das Aktuelle SAP-Release (svers-version(3)) 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 saprelease FM, simply by entering the name SUBST_GET_SAPRELEASE 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_SAPRELEASE 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_SAPRELEASE'"Ermittle das Aktuelle SAP-Release (svers-version(3)).
IMPORTING
EV_SAPRELEASE = "Current SAP Release
EXCEPTIONS
NO_SVERS_ENTRY = 1
EXPORTING Parameters details for SUBST_GET_SAPRELEASE
EV_SAPRELEASE - Current SAP Release
Data type: SY-SAPRLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SVERS_ENTRY - SVERS contains no entries
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUBST_GET_SAPRELEASE 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_saprelease | TYPE SY-SAPRL, " | |||
lv_no_svers_entry | TYPE SY. " |
  CALL FUNCTION 'SUBST_GET_SAPRELEASE' "Ermittle das Aktuelle SAP-Release (svers-version(3)) |
IMPORTING | ||
EV_SAPRELEASE | = lv_ev_saprelease | |
EXCEPTIONS | ||
NO_SVERS_ENTRY = 1 | ||
. " SUBST_GET_SAPRELEASE |
ABAP code using 7.40 inline data declarations to call FM SUBST_GET_SAPRELEASE
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 SAPRL FROM SY INTO @DATA(ld_ev_saprelease). | ||||
Search for further information about these or an SAP related objects