SAP DEST_LOGICAL_READ Function Module for
DEST_LOGICAL_READ is a standard dest logical read 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 dest logical read FM, simply by entering the name DEST_LOGICAL_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDEST_API
Program Name: SAPLSDEST_API
Main Program: SAPLSDEST_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DEST_LOGICAL_READ 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 'DEST_LOGICAL_READ'".
EXPORTING
NAME = "
IMPORTING
DESCRIPTION = "
SAME_USER = "
CONVERSION_MODE = "
CONVERSION_BYTES = "
UNICODE_BYTES = "
RFC_BITMAP = "
RFC_WAN = "
AUTHORIZATION_PARAMETER = "
QRFC_VERSION = "
KEEPALIVE_TIMEOUT = "
CATEGORY = "
REFERENCE = "
UI_LOCK = "
ENABLE_TRACE = "
EXPORT_TRACE = "
LOGON_LANGUAGE = "
LOGON_CLIENT = "
LOGON_USER = "
PASSWORD_STATUS = "
EXCEPTIONS
READ_FAILURE = 1
IMPORTING Parameters details for DEST_LOGICAL_READ
NAME -
Data type: RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DEST_LOGICAL_READ
DESCRIPTION -
Data type: RFCDOC_DOptional: No
Call by Reference: No ( called with pass by value option)
SAME_USER -
Data type: RFCSAMEUSROptional: No
Call by Reference: No ( called with pass by value option)
CONVERSION_MODE -
Data type: RFCCONVERTOptional: No
Call by Reference: No ( called with pass by value option)
CONVERSION_BYTES -
Data type: RFCCONVXOptional: No
Call by Reference: No ( called with pass by value option)
UNICODE_BYTES -
Data type: RFCUNICODEOptional: No
Call by Reference: No ( called with pass by value option)
RFC_BITMAP -
Data type: RFCBITMAPOptional: No
Call by Reference: No ( called with pass by value option)
RFC_WAN -
Data type: RFCWANOptional: No
Call by Reference: No ( called with pass by value option)
AUTHORIZATION_PARAMETER -
Data type: DESTAUTHOptional: No
Call by Reference: No ( called with pass by value option)
QRFC_VERSION -
Data type: QRFCVERSOptional: No
Call by Reference: No ( called with pass by value option)
KEEPALIVE_TIMEOUT -
Data type: SDEST_TIMEOUT_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
CATEGORY -
Data type: RFCCATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
REFERENCE -
Data type: RFCALIASOptional: No
Call by Reference: No ( called with pass by value option)
UI_LOCK -
Data type: RFCLOCKOptional: No
Call by Reference: No ( called with pass by value option)
ENABLE_TRACE -
Data type: RFCTRACEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORT_TRACE -
Data type: TRACEPROPAGATIONOptional: No
Call by Reference: No ( called with pass by value option)
LOGON_LANGUAGE -
Data type: RFCLANGOptional: No
Call by Reference: No ( called with pass by value option)
LOGON_CLIENT -
Data type: RFCCLIENTOptional: No
Call by Reference: No ( called with pass by value option)
LOGON_USER -
Data type: RFCUSEROptional: No
Call by Reference: No ( called with pass by value option)
PASSWORD_STATUS -
Data type: SDEST_PWD_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
READ_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DEST_LOGICAL_READ 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_name | TYPE RFCDEST, " | |||
| lv_description | TYPE RFCDOC_D, " | |||
| lv_read_failure | TYPE RFCDOC_D, " | |||
| lv_same_user | TYPE RFCSAMEUSR, " | |||
| lv_conversion_mode | TYPE RFCCONVERT, " | |||
| lv_conversion_bytes | TYPE RFCCONVX, " | |||
| lv_unicode_bytes | TYPE RFCUNICODE, " | |||
| lv_rfc_bitmap | TYPE RFCBITMAP, " | |||
| lv_rfc_wan | TYPE RFCWAN, " | |||
| lv_authorization_parameter | TYPE DESTAUTH, " | |||
| lv_qrfc_version | TYPE QRFCVERS, " | |||
| lv_keepalive_timeout | TYPE SDEST_TIMEOUT_VALUE, " | |||
| lv_category | TYPE RFCCATEGORY, " | |||
| lv_reference | TYPE RFCALIAS, " | |||
| lv_ui_lock | TYPE RFCLOCK, " | |||
| lv_enable_trace | TYPE RFCTRACE, " | |||
| lv_export_trace | TYPE TRACEPROPAGATION, " | |||
| lv_logon_language | TYPE RFCLANG, " | |||
| lv_logon_client | TYPE RFCCLIENT, " | |||
| lv_logon_user | TYPE RFCUSER, " | |||
| lv_password_status | TYPE SDEST_PWD_STATUS. " |
|   CALL FUNCTION 'DEST_LOGICAL_READ' " |
| EXPORTING | ||
| NAME | = lv_name | |
| IMPORTING | ||
| DESCRIPTION | = lv_description | |
| SAME_USER | = lv_same_user | |
| CONVERSION_MODE | = lv_conversion_mode | |
| CONVERSION_BYTES | = lv_conversion_bytes | |
| UNICODE_BYTES | = lv_unicode_bytes | |
| RFC_BITMAP | = lv_rfc_bitmap | |
| RFC_WAN | = lv_rfc_wan | |
| AUTHORIZATION_PARAMETER | = lv_authorization_parameter | |
| QRFC_VERSION | = lv_qrfc_version | |
| KEEPALIVE_TIMEOUT | = lv_keepalive_timeout | |
| CATEGORY | = lv_category | |
| REFERENCE | = lv_reference | |
| UI_LOCK | = lv_ui_lock | |
| ENABLE_TRACE | = lv_enable_trace | |
| EXPORT_TRACE | = lv_export_trace | |
| LOGON_LANGUAGE | = lv_logon_language | |
| LOGON_CLIENT | = lv_logon_client | |
| LOGON_USER | = lv_logon_user | |
| PASSWORD_STATUS | = lv_password_status | |
| EXCEPTIONS | ||
| READ_FAILURE = 1 | ||
| . " DEST_LOGICAL_READ | ||
ABAP code using 7.40 inline data declarations to call FM DEST_LOGICAL_READ
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