SAP SUBST_RELMAP_GET_IDPOSITION Function Module for Finds the physical column of a release in a release map

Search SAP Function Modules

SUBST_RELMAP_GET_IDPOSITION is a standard subst relmap get idposition SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Finds the physical column of a release in a release map 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 relmap get idposition FM, simply by entering the name SUBST_RELMAP_GET_IDPOSITION into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUGB
Program Name: SAPLSUGB
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SUBST_RELMAP_GET_IDPOSITION 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_RELMAP_GET_IDPOSITION'"Finds the physical column of a release in a release map
  EXPORTING
*  IV_RELMAPNAME = ' ' "Convention: Use target release as name!
*  IV_SAPRELEASE = ' ' "Customer release before substitution
*  IV_SAPRELEASE_LONG = ' ' "Customer release before substitution
*  IV_BYPASSING_BUFFER = ' ' "Single-Character Flag

 IMPORTING
   EV_IDPOSITION =  "Physical position in rel. map
   EV_GENERIC =  "

EXCEPTIONS
   MAPPING_NOT_FOUND = 1    RELMAP_NOT_FOUND = 2 

.

IMPORTING Parameters details for SUBST_RELMAP_GET_IDPOSITION

IV_RELMAPNAME - Convention: Use target release as name!

Data type: RELEASEMAP-MAPNAME
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SAPRELEASE - Customer release before substitution

Data type: SY-SAPRL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SAPRELEASE_LONG - Customer release before substitution

Data type: RELEASEMAP-SAPRELEASE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_BYPASSING_BUFFER - Single-Character Flag

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

EXPORTING Parameters details for SUBST_RELMAP_GET_IDPOSITION

EV_IDPOSITION - Physical position in rel. map

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

EV_GENERIC -

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

EXCEPTIONS details

MAPPING_NOT_FOUND - IV_STARTRELEASE not found in IV_RELMAPNAME

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

RELMAP_NOT_FOUND - IV_RELMAPNAME not found in RELEASEMAP

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

Copy and paste ABAP code example for SUBST_RELMAP_GET_IDPOSITION 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.

ABAP code using 7.40 inline data declarations to call FM SUBST_RELMAP_GET_IDPOSITION

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.

Search for further information about these or an SAP related objects