SAP CHECK_FOR_UPDATE_BDL2TRANS Function Module for get information which tables are to update from sapnet
CHECK_FOR_UPDATE_BDL2TRANS is a standard check for update bdl2trans SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for get information which tables are to update from 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 check for update bdl2trans FM, simply by entering the name CHECK_FOR_UPDATE_BDL2TRANS 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): Remote-Enabled
Update:

Function CHECK_FOR_UPDATE_BDL2TRANS 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 'CHECK_FOR_UPDATE_BDL2TRANS'"get information which tables are to update from sapnet.
EXPORTING
* DEST_TYPE = 'SAP' "Character field length = 10
TABLES
BDL_TO_UPDATE = "
ERROR_LOG = "
EXCEPTIONS
LOCK_ERROR = 1
IMPORTING Parameters details for CHECK_FOR_UPDATE_BDL2TRANS
DEST_TYPE - Character field length = 10
Data type: BDL2TRANS-SAPNETBDLDefault: 'SAP'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CHECK_FOR_UPDATE_BDL2TRANS
BDL_TO_UPDATE -
Data type: BDL2TRANSOptional: No
Call by Reference: No ( called with pass by value option)
ERROR_LOG -
Data type: LISTEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOCK_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CHECK_FOR_UPDATE_BDL2TRANS 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_dest_type | TYPE BDL2TRANS-SAPNETBDL, " 'SAP' | |||
| lv_lock_error | TYPE BDL2TRANS, " | |||
| lt_bdl_to_update | TYPE STANDARD TABLE OF BDL2TRANS, " | |||
| lt_error_log | TYPE STANDARD TABLE OF LISTE. " |
|   CALL FUNCTION 'CHECK_FOR_UPDATE_BDL2TRANS' "get information which tables are to update from sapnet |
| EXPORTING | ||
| DEST_TYPE | = lv_dest_type | |
| TABLES | ||
| BDL_TO_UPDATE | = lt_bdl_to_update | |
| ERROR_LOG | = lt_error_log | |
| EXCEPTIONS | ||
| LOCK_ERROR = 1 | ||
| . " CHECK_FOR_UPDATE_BDL2TRANS | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_FOR_UPDATE_BDL2TRANS
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 SAPNETBDL FROM BDL2TRANS INTO @DATA(ld_dest_type). | ||||
| DATA(ld_dest_type) | = 'SAP'. | |||
Search for further information about these or an SAP related objects