SAP GET_DT_RECODER_KEY Function Module for
GET_DT_RECODER_KEY is a standard get dt recoder key 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 get dt recoder key FM, simply by entering the name GET_DT_RECODER_KEY into the relevant SAP transaction such as SE37 or SE38.
Function Group: DTCO
Program Name: SAPLDTCO
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_DT_RECODER_KEY 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 'GET_DT_RECODER_KEY'".
EXPORTING
I_DATEFROM = "
I_DATETO = "
I_ARBID = "
TABLES
E_RCR01 = "
EXCEPTIONS
ROUTING_ERROR = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLDTCO_001 Downtime Sorting
IMPORTING Parameters details for GET_DT_RECODER_KEY
I_DATEFROM -
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_DATETO -
Data type: SY-DATUMOptional: No
Call by Reference: Yes
I_ARBID -
Data type: REDTEL-ARBIDOptional: No
Call by Reference: Yes
TABLES Parameters details for GET_DT_RECODER_KEY
E_RCR01 -
Data type: RCR01Optional: No
Call by Reference: Yes
EXCEPTIONS details
ROUTING_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GET_DT_RECODER_KEY 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: | ||||
| lt_e_rcr01 | TYPE STANDARD TABLE OF RCR01, " | |||
| lv_i_datefrom | TYPE SY-DATUM, " | |||
| lv_routing_error | TYPE SY, " | |||
| lv_i_dateto | TYPE SY-DATUM, " | |||
| lv_i_arbid | TYPE REDTEL-ARBID. " |
|   CALL FUNCTION 'GET_DT_RECODER_KEY' " |
| EXPORTING | ||
| I_DATEFROM | = lv_i_datefrom | |
| I_DATETO | = lv_i_dateto | |
| I_ARBID | = lv_i_arbid | |
| TABLES | ||
| E_RCR01 | = lt_e_rcr01 | |
| EXCEPTIONS | ||
| ROUTING_ERROR = 1 | ||
| . " GET_DT_RECODER_KEY | ||
ABAP code using 7.40 inline data declarations to call FM GET_DT_RECODER_KEY
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 DATUM FROM SY INTO @DATA(ld_i_datefrom). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_dateto). | ||||
| "SELECT single ARBID FROM REDTEL INTO @DATA(ld_i_arbid). | ||||
Search for further information about these or an SAP related objects