SAP SRFC_DIALOG Function Module for Dialog to request RFC Service data
SRFC_DIALOG is a standard srfc dialog SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Dialog to request RFC Service data 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 srfc dialog FM, simply by entering the name SRFC_DIALOG into the relevant SAP transaction such as SE37 or SE38.
Function Group: UCON_WB_LM_DIALOGS
Program Name: SAPLUCON_WB_LM_DIALOGS
Main Program: SAPLUCON_WB_LM_DIALOGS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SRFC_DIALOG 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 'SRFC_DIALOG'"Dialog to request RFC Service data.
EXPORTING
RFC_SERVICE_NAME = "RFC Service ID
CHANGING
ATTRIBUTES = "Attributes passed via function builder to RFC-Service
EXCEPTIONS
CANCELED = 1
IMPORTING Parameters details for SRFC_DIALOG
RFC_SERVICE_NAME - RFC Service ID
Data type: UCONRFCSERVIDOptional: No
Call by Reference: Yes
CHANGING Parameters details for SRFC_DIALOG
ATTRIBUTES - Attributes passed via function builder to RFC-Service
Data type: UCON_RFC_SERVICE_ATTRIBUTESOptional: No
Call by Reference: Yes
EXCEPTIONS details
CANCELED - Canceled
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SRFC_DIALOG 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_canceled | TYPE STRING, " | |||
| lv_attributes | TYPE UCON_RFC_SERVICE_ATTRIBUTES, " | |||
| lv_rfc_service_name | TYPE UCONRFCSERVID. " |
|   CALL FUNCTION 'SRFC_DIALOG' "Dialog to request RFC Service data |
| EXPORTING | ||
| RFC_SERVICE_NAME | = lv_rfc_service_name | |
| CHANGING | ||
| ATTRIBUTES | = lv_attributes | |
| EXCEPTIONS | ||
| CANCELED = 1 | ||
| . " SRFC_DIALOG | ||
ABAP code using 7.40 inline data declarations to call FM SRFC_DIALOG
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