SAP DISPATCH_SPML_REQUEST_BGRFC Function Module for
DISPATCH_SPML_REQUEST_BGRFC is a standard dispatch spml request bgrfc 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 dispatch spml request bgrfc FM, simply by entering the name DISPATCH_SPML_REQUEST_BGRFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: SPML_CLIENT
Program Name: SAPLSPML_CLIENT
Main Program: SAPLSPML_CLIENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DISPATCH_SPML_REQUEST_BGRFC 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 'DISPATCH_SPML_REQUEST_BGRFC'".
EXPORTING
IV_REQUEST = "
IV_DESTINATION = "
IMPORTING
EV_RESPONSE = "
EXCEPTIONS
HTTP_INVALID_TIMEOUT = 1 OTHERS = 10 COMMUNICATION_FAILURE = 2 INVALID_SOAP_RESPONSE = 3 DOM_NOT_INITIALIZED = 4 ATTRIBUTE_NOT_FOUND = 5 SERVICE_ERROR = 6 INVALID_STATUS = 7 INVALID_DESTINATION = 8 NO_AUTHORIZATION = 9
IMPORTING Parameters details for DISPATCH_SPML_REQUEST_BGRFC
IV_REQUEST -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
IV_DESTINATION -
Data type: RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DISPATCH_SPML_REQUEST_BGRFC
EV_RESPONSE -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
HTTP_INVALID_TIMEOUT -
Data type:Optional: No
Call by Reference: Yes
OTHERS -
Data type:Optional: No
Call by Reference: Yes
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: Yes
INVALID_SOAP_RESPONSE -
Data type:Optional: No
Call by Reference: Yes
DOM_NOT_INITIALIZED -
Data type:Optional: No
Call by Reference: Yes
ATTRIBUTE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
SERVICE_ERROR -
Data type:Optional: No
Call by Reference: Yes
INVALID_STATUS -
Data type:Optional: No
Call by Reference: Yes
INVALID_DESTINATION -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DISPATCH_SPML_REQUEST_BGRFC 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_iv_request | TYPE XSTRING, " | |||
| lv_ev_response | TYPE XSTRING, " | |||
| lv_http_invalid_timeout | TYPE XSTRING, " | |||
| lv_others | TYPE XSTRING, " | |||
| lv_iv_destination | TYPE RFCDEST, " | |||
| lv_communication_failure | TYPE RFCDEST, " | |||
| lv_invalid_soap_response | TYPE RFCDEST, " | |||
| lv_dom_not_initialized | TYPE RFCDEST, " | |||
| lv_attribute_not_found | TYPE RFCDEST, " | |||
| lv_service_error | TYPE RFCDEST, " | |||
| lv_invalid_status | TYPE RFCDEST, " | |||
| lv_invalid_destination | TYPE RFCDEST, " | |||
| lv_no_authorization | TYPE RFCDEST. " |
|   CALL FUNCTION 'DISPATCH_SPML_REQUEST_BGRFC' " |
| EXPORTING | ||
| IV_REQUEST | = lv_iv_request | |
| IV_DESTINATION | = lv_iv_destination | |
| IMPORTING | ||
| EV_RESPONSE | = lv_ev_response | |
| EXCEPTIONS | ||
| HTTP_INVALID_TIMEOUT = 1 | ||
| OTHERS = 10 | ||
| COMMUNICATION_FAILURE = 2 | ||
| INVALID_SOAP_RESPONSE = 3 | ||
| DOM_NOT_INITIALIZED = 4 | ||
| ATTRIBUTE_NOT_FOUND = 5 | ||
| SERVICE_ERROR = 6 | ||
| INVALID_STATUS = 7 | ||
| INVALID_DESTINATION = 8 | ||
| NO_AUTHORIZATION = 9 | ||
| . " DISPATCH_SPML_REQUEST_BGRFC | ||
ABAP code using 7.40 inline data declarations to call FM DISPATCH_SPML_REQUEST_BGRFC
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