SAP BDT_DATA_CHECK Function Module for









BDT_DATA_CHECK is a standard bdt data check 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 bdt data check FM, simply by entering the name BDT_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: BUSS
Program Name: SAPLBUSS
Main Program: SAPLBUSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BDT_DATA_CHECK 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 'BDT_DATA_CHECK'"
  EXPORTING
   IV_HANDLE =  "ID of a BDT Instance
*  IV_NO_DATA =  "BDT: No data character

TABLES
*  IT_DATA =  "Data
*  ET_MESSAGE =  "Messages

EXCEPTIONS
   HANDLE_NOT_FOUND = 1
.



IMPORTING Parameters details for BDT_DATA_CHECK

IV_HANDLE - ID of a BDT Instance

Data type: BDT_INSTANCE_ID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_NO_DATA - BDT: No data character

Data type: BDT_NO_DATA
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDT_DATA_CHECK

IT_DATA - Data

Data type: BUSFRGN2
Optional: Yes
Call by Reference: Yes

ET_MESSAGE - Messages

Data type: BUS0MSG1
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

HANDLE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BDT_DATA_CHECK 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:
lt_it_data  TYPE STANDARD TABLE OF BUSFRGN2, "   
lv_iv_handle  TYPE BDT_INSTANCE_ID, "   
lv_handle_not_found  TYPE BDT_INSTANCE_ID, "   
lt_et_message  TYPE STANDARD TABLE OF BUS0MSG1, "   
lv_iv_no_data  TYPE BDT_NO_DATA. "   

  CALL FUNCTION 'BDT_DATA_CHECK'  "
    EXPORTING
         IV_HANDLE = lv_iv_handle
         IV_NO_DATA = lv_iv_no_data
    TABLES
         IT_DATA = lt_it_data
         ET_MESSAGE = lt_et_message
    EXCEPTIONS
        HANDLE_NOT_FOUND = 1
. " BDT_DATA_CHECK




ABAP code using 7.40 inline data declarations to call FM BDT_DATA_CHECK

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!