SAP RDM_OPT_TASKNAME_RANGE_GET Function Module for Determine Number Range of Parallel Tasks
RDM_OPT_TASKNAME_RANGE_GET is a standard rdm opt taskname range get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Number Range of Parallel Tasks 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 rdm opt taskname range get FM, simply by entering the name RDM_OPT_TASKNAME_RANGE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: RDM_OPT_COMMON
Program Name: SAPLRDM_OPT_COMMON
Main Program: SAPLRDM_OPT_COMMON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RDM_OPT_TASKNAME_RANGE_GET 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 'RDM_OPT_TASKNAME_RANGE_GET'"Determine Number Range of Parallel Tasks.
EXPORTING
I_RANGE_ID = "Gruppierungs-ID für parallele tasknamen-Ranges =>siehe CL_RDM_OPT_CONST
IMPORTING
E_TASKNAME_LOW = "Name of a Parallel RFC Request
E_TASKNAME_HIGH = "Name of a Parallel RFC Request
EXCEPTIONS
ID_NOT_FOUND = 1
IMPORTING Parameters details for RDM_OPT_TASKNAME_RANGE_GET
I_RANGE_ID - Gruppierungs-ID für parallele tasknamen-Ranges =>siehe CL_RDM_OPT_CONST
Data type: RDM_PARALLEL_TASK_RANGE_IDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RDM_OPT_TASKNAME_RANGE_GET
E_TASKNAME_LOW - Name of a Parallel RFC Request
Data type: RDM_TASKNAMEOptional: No
Call by Reference: Yes
E_TASKNAME_HIGH - Name of a Parallel RFC Request
Data type: RDM_TASKNAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
ID_NOT_FOUND - Range-ID existiert nicht
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RDM_OPT_TASKNAME_RANGE_GET 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_i_range_id | TYPE RDM_PARALLEL_TASK_RANGE_ID, " | |||
| lv_id_not_found | TYPE RDM_PARALLEL_TASK_RANGE_ID, " | |||
| lv_e_taskname_low | TYPE RDM_TASKNAME, " | |||
| lv_e_taskname_high | TYPE RDM_TASKNAME. " |
|   CALL FUNCTION 'RDM_OPT_TASKNAME_RANGE_GET' "Determine Number Range of Parallel Tasks |
| EXPORTING | ||
| I_RANGE_ID | = lv_i_range_id | |
| IMPORTING | ||
| E_TASKNAME_LOW | = lv_e_taskname_low | |
| E_TASKNAME_HIGH | = lv_e_taskname_high | |
| EXCEPTIONS | ||
| ID_NOT_FOUND = 1 | ||
| . " RDM_OPT_TASKNAME_RANGE_GET | ||
ABAP code using 7.40 inline data declarations to call FM RDM_OPT_TASKNAME_RANGE_GET
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