SAP CONTROL_RECORD_GET_DESTINATION Function Module for Get an RFC Destination from the Control Record
CONTROL_RECORD_GET_DESTINATION is a standard control record get destination SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get an RFC Destination from the Control Record 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 control record get destination FM, simply by entering the name CONTROL_RECORD_GET_DESTINATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BD_DISPATCHER
Program Name: SAPLBBP_BD_DISPATCHER
Main Program: SAPLBBP_BD_DISPATCHER
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CONTROL_RECORD_GET_DESTINATION 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 'CONTROL_RECORD_GET_DESTINATION'"Get an RFC Destination from the Control Record.
IMPORTING
RFC_DESTINATION = "RFCDES_RFCDEST
TABLES
CONTROL_RECORD = "BBP_CONTROL_RECORD
EXCEPTIONS
NOT_FOUND = 1
EXPORTING Parameters details for CONTROL_RECORD_GET_DESTINATION
RFC_DESTINATION - RFCDES_RFCDEST
Data type: RFCDISPLAY-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CONTROL_RECORD_GET_DESTINATION
CONTROL_RECORD - BBP_CONTROL_RECORD
Data type: BBP_CONTROL_RECORDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CONTROL_RECORD_GET_DESTINATION 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_not_found | TYPE STRING, " | |||
| lt_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD, " | |||
| lv_rfc_destination | TYPE RFCDISPLAY-RFCDEST. " |
|   CALL FUNCTION 'CONTROL_RECORD_GET_DESTINATION' "Get an RFC Destination from the Control Record |
| IMPORTING | ||
| RFC_DESTINATION | = lv_rfc_destination | |
| TABLES | ||
| CONTROL_RECORD | = lt_control_record | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " CONTROL_RECORD_GET_DESTINATION | ||
ABAP code using 7.40 inline data declarations to call FM CONTROL_RECORD_GET_DESTINATION
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 RFCDEST FROM RFCDISPLAY INTO @DATA(ld_rfc_destination). | ||||
Search for further information about these or an SAP related objects