SAP UR_EXEC_SELECT_DATA Function Module for
UR_EXEC_SELECT_DATA is a standard ur exec select data 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 ur exec select data FM, simply by entering the name UR_EXEC_SELECT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: UR_EXEC_TEST_GUI
Program Name: SAPLUR_EXEC_TEST_GUI
Main Program: SAPLUR_EXEC_TEST_GUI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UR_EXEC_SELECT_DATA 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 'UR_EXEC_SELECT_DATA'".
EXPORTING
I_ID = "
I_CHGRUN = "
I_NUMBER_OF_RECS = "
IO_REAL_ENGINE = "
EXCEPTIONS
CANCELLED = 1 FAILED = 2
IMPORTING Parameters details for UR_EXEC_SELECT_DATA
I_ID -
Data type: UR_IDOptional: No
Call by Reference: Yes
I_CHGRUN -
Data type: UR_CHGRUNOptional: No
Call by Reference: Yes
I_NUMBER_OF_RECS -
Data type: IOptional: No
Call by Reference: Yes
IO_REAL_ENGINE -
Data type: CL_UR_REALIGNMENT_ENGINEOptional: No
Call by Reference: Yes
EXCEPTIONS details
CANCELLED -
Data type:Optional: No
Call by Reference: Yes
FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UR_EXEC_SELECT_DATA 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_id | TYPE UR_ID, " | |||
| lv_cancelled | TYPE UR_ID, " | |||
| lv_failed | TYPE UR_ID, " | |||
| lv_i_chgrun | TYPE UR_CHGRUN, " | |||
| lv_i_number_of_recs | TYPE I, " | |||
| lv_io_real_engine | TYPE CL_UR_REALIGNMENT_ENGINE. " |
|   CALL FUNCTION 'UR_EXEC_SELECT_DATA' " |
| EXPORTING | ||
| I_ID | = lv_i_id | |
| I_CHGRUN | = lv_i_chgrun | |
| I_NUMBER_OF_RECS | = lv_i_number_of_recs | |
| IO_REAL_ENGINE | = lv_io_real_engine | |
| EXCEPTIONS | ||
| CANCELLED = 1 | ||
| FAILED = 2 | ||
| . " UR_EXEC_SELECT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM UR_EXEC_SELECT_DATA
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