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

Function BDL_SEND_DATA 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_SEND_DATA'"send downloaded data to sapnet.
EXPORTING
DESTINATION = "
TO_SEND_SESSIONNR = "
TO_SEND_MANDANT = "
* MAPTO_SESSIONNR = ' ' "Character field length = 10
* MAPTO_MANDANT = ' ' "3-Byte field
* FORCE_SEND = ' ' "Internal
* NO_MSG_LOGGING = ' ' "Internal
IMPORTING
RCODE = "
EXCEPTIONS
NO_DATA_FOUND = 1 WRONG_PARAMETERS = 2
IMPORTING Parameters details for BDL_SEND_DATA
DESTINATION -
Data type: RFCDES-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
TO_SEND_SESSIONNR -
Data type: BDLDATCOL-SESSIONNROptional: No
Call by Reference: No ( called with pass by value option)
TO_SEND_MANDANT -
Data type: BDLDATCOL-MANDANTOptional: No
Call by Reference: No ( called with pass by value option)
MAPTO_SESSIONNR - Character field length = 10
Data type: BDLDATCOL-SESSIONNRDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
MAPTO_MANDANT - 3-Byte field
Data type: BDLDATCOL-MANDANTDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
FORCE_SEND - Internal
Data type: SY-DEBUGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_MSG_LOGGING - Internal
Data type: SY-DEBUGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BDL_SEND_DATA
RCODE -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DATA_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_PARAMETERS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BDL_SEND_DATA 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_rcode | TYPE SY-SUBRC, " | |||
| lv_destination | TYPE RFCDES-RFCDEST, " | |||
| lv_no_data_found | TYPE RFCDES, " | |||
| lv_wrong_parameters | TYPE RFCDES, " | |||
| lv_to_send_sessionnr | TYPE BDLDATCOL-SESSIONNR, " | |||
| lv_to_send_mandant | TYPE BDLDATCOL-MANDANT, " | |||
| lv_mapto_sessionnr | TYPE BDLDATCOL-SESSIONNR, " ' ' | |||
| lv_mapto_mandant | TYPE BDLDATCOL-MANDANT, " ' ' | |||
| lv_force_send | TYPE SY-DEBUG, " ' ' | |||
| lv_no_msg_logging | TYPE SY-DEBUG. " ' ' |
|   CALL FUNCTION 'BDL_SEND_DATA' "send downloaded data to sapnet |
| EXPORTING | ||
| DESTINATION | = lv_destination | |
| TO_SEND_SESSIONNR | = lv_to_send_sessionnr | |
| TO_SEND_MANDANT | = lv_to_send_mandant | |
| MAPTO_SESSIONNR | = lv_mapto_sessionnr | |
| MAPTO_MANDANT | = lv_mapto_mandant | |
| FORCE_SEND | = lv_force_send | |
| NO_MSG_LOGGING | = lv_no_msg_logging | |
| IMPORTING | ||
| RCODE | = lv_rcode | |
| EXCEPTIONS | ||
| NO_DATA_FOUND = 1 | ||
| WRONG_PARAMETERS = 2 | ||
| . " BDL_SEND_DATA | ||
ABAP code using 7.40 inline data declarations to call FM BDL_SEND_DATA
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_rcode). | ||||
| "SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_destination). | ||||
| "SELECT single SESSIONNR FROM BDLDATCOL INTO @DATA(ld_to_send_sessionnr). | ||||
| "SELECT single MANDANT FROM BDLDATCOL INTO @DATA(ld_to_send_mandant). | ||||
| "SELECT single SESSIONNR FROM BDLDATCOL INTO @DATA(ld_mapto_sessionnr). | ||||
| DATA(ld_mapto_sessionnr) | = ' '. | |||
| "SELECT single MANDANT FROM BDLDATCOL INTO @DATA(ld_mapto_mandant). | ||||
| DATA(ld_mapto_mandant) | = ' '. | |||
| "SELECT single DEBUG FROM SY INTO @DATA(ld_force_send). | ||||
| DATA(ld_force_send) | = ' '. | |||
| "SELECT single DEBUG FROM SY INTO @DATA(ld_no_msg_logging). | ||||
| DATA(ld_no_msg_logging) | = ' '. | |||
Search for further information about these or an SAP related objects