SAP DD_SE_PING Function Module for
DD_SE_PING is a standard dd se ping 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 dd se ping FM, simply by entering the name DD_SE_PING into the relevant SAP transaction such as SE37 or SE38.
Function Group: SF4E
Program Name: SAPLSF4E
Main Program: SAPLSF4E
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_SE_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 'DD_SE_PING'".
EXPORTING
ACTION = "Search server relation task (search or index)
SRSVRID = "Search Server Relation ID
IMPORTING
RC = "Return Code
EXCEPTIONS
ID_NOT_EXISTS = 1
IMPORTING Parameters details for DD_SE_PING
ACTION - Search server relation task (search or index)
Data type: SRET_SSRACOptional: No
Call by Reference: No ( called with pass by value option)
SRSVRID - Search Server Relation ID
Data type: SRET_SSRIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_SE_PING
RC - Return Code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ID_NOT_EXISTS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DD_SE_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_rc | TYPE SY-SUBRC, " | |||
| lv_action | TYPE SRET_SSRAC, " | |||
| lv_id_not_exists | TYPE SRET_SSRAC, " | |||
| lv_srsvrid | TYPE SRET_SSRID. " |
|   CALL FUNCTION 'DD_SE_PING' " |
| EXPORTING | ||
| ACTION | = lv_action | |
| SRSVRID | = lv_srsvrid | |
| IMPORTING | ||
| RC | = lv_rc | |
| EXCEPTIONS | ||
| ID_NOT_EXISTS = 1 | ||
| . " DD_SE_PING | ||
ABAP code using 7.40 inline data declarations to call FM DD_SE_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 SUBRC FROM SY INTO @DATA(ld_rc). | ||||
Search for further information about these or an SAP related objects