SAP /BDL/_SERVER_PING Function Module for Pings servers within the customer system
/BDL/_SERVER_PING is a standard /bdl/ server ping SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Pings servers within the customer system 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 /bdl/ server ping FM, simply by entering the name /BDL/_SERVER_PING into the relevant SAP transaction such as SE37 or SE38.
Function Group: /BDL/BDL3
Program Name: /BDL/SAPLBDL3
Main Program: /BDL/SAPLBDL3
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /BDL/_SERVER_PING 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 '/BDL/_SERVER_PING'"Pings servers within the customer system.
EXPORTING
DESTINATION_CHECKED = "Logical destination (specified in function call)
IMPORTING
DESTINATION_OK = "
IMPORTING Parameters details for /BDL/_SERVER_PING
DESTINATION_CHECKED - Logical destination (specified in function call)
Data type: RFCDES-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /BDL/_SERVER_PING
DESTINATION_OK -
Data type: SY-DEBUGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /BDL/_SERVER_PING 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_destination_ok | TYPE SY-DEBUG, " | |||
| lv_destination_checked | TYPE RFCDES-RFCDEST. " |
|   CALL FUNCTION '/BDL/_SERVER_PING' "Pings servers within the customer system |
| EXPORTING | ||
| DESTINATION_CHECKED | = lv_destination_checked | |
| IMPORTING | ||
| DESTINATION_OK | = lv_destination_ok | |
| . " /BDL/_SERVER_PING | ||
ABAP code using 7.40 inline data declarations to call FM /BDL/_SERVER_PING
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 DEBUG FROM SY INTO @DATA(ld_destination_ok). | ||||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_destination_checked). | ||||
Search for further information about these or an SAP related objects