SAP SUBST_GET_RELMAP_FOR_BASREL Function Module for
SUBST_GET_RELMAP_FOR_BASREL is a standard subst get relmap for basrel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 relmap for basrel FM, simply by entering the name SUBST_GET_RELMAP_FOR_BASREL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUGE
Program Name: SAPLSUGE
Main Program: SAPLSUGE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SUBST_GET_RELMAP_FOR_BASREL 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_RELMAP_FOR_BASREL'".
EXPORTING
IV_BASRELEASE = "
IMPORTING
EV_SAPREL1 = "
EV_SAPREL2 = "
IMPORTING Parameters details for SUBST_GET_RELMAP_FOR_BASREL
IV_BASRELEASE -
Data type: RELEASEMAP-MAPNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUBST_GET_RELMAP_FOR_BASREL
EV_SAPREL1 -
Data type: RELEASEMAP-SAPRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
EV_SAPREL2 -
Data type: RELEASEMAP-SAPRELEASEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUBST_GET_RELMAP_FOR_BASREL 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_saprel1 | TYPE RELEASEMAP-SAPRELEASE, " | |||
| lv_iv_basrelease | TYPE RELEASEMAP-MAPNAME, " | |||
| lv_ev_saprel2 | TYPE RELEASEMAP-SAPRELEASE. " |
|   CALL FUNCTION 'SUBST_GET_RELMAP_FOR_BASREL' " |
| EXPORTING | ||
| IV_BASRELEASE | = lv_iv_basrelease | |
| IMPORTING | ||
| EV_SAPREL1 | = lv_ev_saprel1 | |
| EV_SAPREL2 | = lv_ev_saprel2 | |
| . " SUBST_GET_RELMAP_FOR_BASREL | ||
ABAP code using 7.40 inline data declarations to call FM SUBST_GET_RELMAP_FOR_BASREL
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 SAPRELEASE FROM RELEASEMAP INTO @DATA(ld_ev_saprel1). | ||||
| "SELECT single MAPNAME FROM RELEASEMAP INTO @DATA(ld_iv_basrelease). | ||||
| "SELECT single SAPRELEASE FROM RELEASEMAP INTO @DATA(ld_ev_saprel2). | ||||
Search for further information about these or an SAP related objects