SAP BDL_FUPDEF_INTERFACE_GET Function Module for Gets interface data from BDLFUPDEF for R/3-Release 4.*









BDL_FUPDEF_INTERFACE_GET is a standard bdl fupdef interface get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets interface data from BDLFUPDEF for R/3-Release 4.* 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 fupdef interface get FM, simply by entering the name BDL_FUPDEF_INTERFACE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDL5
Program Name: SAPLBDL5
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BDL_FUPDEF_INTERFACE_GET 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_FUPDEF_INTERFACE_GET'"Gets interface data from BDLFUPDEF for R/3-Release 4.*
EXPORTING
LOGFUNC = "
CLUST_ID = "

IMPORTING
GLOBAL_FLAG = "
REMOTE_CALL = "
UPDATE_TASK = "

TABLES
* EXCEPTION_LIST = "
* EXPORT_PARAMETER = "
* IMPORT_PARAMETER = "
* CHANGING_PARAMETER = "
* TABLES_PARAMETER = "
* DFIELDS_TAB = "
* TABLE_HEADERS = "

EXCEPTIONS
NO_DATA_FOUND = 1
.



IMPORTING Parameters details for BDL_FUPDEF_INTERFACE_GET

LOGFUNC -

Data type: BDLFUVERS-LOGFUNC
Optional: No
Call by Reference: No ( called with pass by value option)

CLUST_ID -

Data type: BDLFUVERS-CLUST_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BDL_FUPDEF_INTERFACE_GET

GLOBAL_FLAG -

Data type: BDL_STRUCT-CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

REMOTE_CALL -

Data type: BDL_STRUCT-CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_TASK -

Data type: BDL_STRUCT-CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDL_FUPDEF_INTERFACE_GET

EXCEPTION_LIST -

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

EXPORT_PARAMETER -

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

IMPORT_PARAMETER -

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

CHANGING_PARAMETER -

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

TABLES_PARAMETER -

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

DFIELDS_TAB -

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

TABLE_HEADERS -

Data type: BDLTABHEAD
Optional: Yes
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)

Copy and paste ABAP code example for BDL_FUPDEF_INTERFACE_GET 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_logfunc  TYPE BDLFUVERS-LOGFUNC, "   
lv_global_flag  TYPE BDL_STRUCT-CHAR1, "   
lv_no_data_found  TYPE BDL_STRUCT, "   
lt_exception_list  TYPE STANDARD TABLE OF BDLRSEXC4, "   
lv_clust_id  TYPE BDLFUVERS-CLUST_ID, "   
lv_remote_call  TYPE BDL_STRUCT-CHAR1, "   
lt_export_parameter  TYPE STANDARD TABLE OF BDLRSEXP4, "   
lv_update_task  TYPE BDL_STRUCT-CHAR1, "   
lt_import_parameter  TYPE STANDARD TABLE OF BDLRSIMP4, "   
lt_changing_parameter  TYPE STANDARD TABLE OF BDLRSCHA4, "   
lt_tables_parameter  TYPE STANDARD TABLE OF BDLRSTBL4, "   
lt_dfields_tab  TYPE STANDARD TABLE OF BDLDFIELDS, "   
lt_table_headers  TYPE STANDARD TABLE OF BDLTABHEAD. "   

  CALL FUNCTION 'BDL_FUPDEF_INTERFACE_GET'  "Gets interface data from BDLFUPDEF for R/3-Release 4.*
    EXPORTING
         LOGFUNC = lv_logfunc
         CLUST_ID = lv_clust_id
    IMPORTING
         GLOBAL_FLAG = lv_global_flag
         REMOTE_CALL = lv_remote_call
         UPDATE_TASK = lv_update_task
    TABLES
         EXCEPTION_LIST = lt_exception_list
         EXPORT_PARAMETER = lt_export_parameter
         IMPORT_PARAMETER = lt_import_parameter
         CHANGING_PARAMETER = lt_changing_parameter
         TABLES_PARAMETER = lt_tables_parameter
         DFIELDS_TAB = lt_dfields_tab
         TABLE_HEADERS = lt_table_headers
    EXCEPTIONS
        NO_DATA_FOUND = 1
. " BDL_FUPDEF_INTERFACE_GET




ABAP code using 7.40 inline data declarations to call FM BDL_FUPDEF_INTERFACE_GET

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 LOGFUNC FROM BDLFUVERS INTO @DATA(ld_logfunc).
 
"SELECT single CHAR1 FROM BDL_STRUCT INTO @DATA(ld_global_flag).
 
 
 
"SELECT single CLUST_ID FROM BDLFUVERS INTO @DATA(ld_clust_id).
 
"SELECT single CHAR1 FROM BDL_STRUCT INTO @DATA(ld_remote_call).
 
 
"SELECT single CHAR1 FROM BDL_STRUCT INTO @DATA(ld_update_task).
 
 
 
 
 
 


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!