SAP Function Modules

BDL_FUPDEF_INTERFACE_SET SAP Function module - Saves interface data in BDLFUPDEF for R/3-Release 4.*







BDL_FUPDEF_INTERFACE_SET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BDL_FUPDEF_INTERFACE_SET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BDL5
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM BDL_FUPDEF_INTERFACE_SET - BDL FUPDEF INTERFACE SET





CALL FUNCTION 'BDL_FUPDEF_INTERFACE_SET' "Saves interface data in BDLFUPDEF for R/3-Release 4.*
  EXPORTING
    logfunc =                   " bdlfuvers-logfunc
    clust_id =                  " bdlfuvers-clust_id
*   versionnr =                 " bdlfupdef-versionnr  Sets version of given version number active.
    global_flag =               " bdl_struct-char1
    remote_call =               " bdl_struct-char1
    update_task =               " bdl_struct-char1
  TABLES
    exception_list =            " bdlrsexc4
    export_parameter =          " bdlrsexp4
    import_parameter =          " bdlrsimp4
    changing_parameter =        " bdlrscha4
    tables_parameter =          " bdlrstbl4
    dfields_tab =               " bdldfields
    table_headers =             " bdltabhead
  EXCEPTIONS
    EXPORT_ERROR = 1            "
    WRONG_VERSIONNR = 2         "               Version number does not exist.
    .  "  BDL_FUPDEF_INTERFACE_SET

ABAP code example for Function Module BDL_FUPDEF_INTERFACE_SET





The ABAP code below is a full code listing to execute function module BDL_FUPDEF_INTERFACE_SET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_exception_list  TYPE STANDARD TABLE OF BDLRSEXC4,"TABLES PARAM
wa_exception_list  LIKE LINE OF it_exception_list ,
it_export_parameter  TYPE STANDARD TABLE OF BDLRSEXP4,"TABLES PARAM
wa_export_parameter  LIKE LINE OF it_export_parameter ,
it_import_parameter  TYPE STANDARD TABLE OF BDLRSIMP4,"TABLES PARAM
wa_import_parameter  LIKE LINE OF it_import_parameter ,
it_changing_parameter  TYPE STANDARD TABLE OF BDLRSCHA4,"TABLES PARAM
wa_changing_parameter  LIKE LINE OF it_changing_parameter ,
it_tables_parameter  TYPE STANDARD TABLE OF BDLRSTBL4,"TABLES PARAM
wa_tables_parameter  LIKE LINE OF it_tables_parameter ,
it_dfields_tab  TYPE STANDARD TABLE OF BDLDFIELDS,"TABLES PARAM
wa_dfields_tab  LIKE LINE OF it_dfields_tab ,
it_table_headers  TYPE STANDARD TABLE OF BDLTABHEAD,"TABLES PARAM
wa_table_headers  LIKE LINE OF it_table_headers .


SELECT single LOGFUNC
FROM BDLFUVERS
INTO @DATA(ld_logfunc).


SELECT single CLUST_ID
FROM BDLFUVERS
INTO @DATA(ld_clust_id).


SELECT single VERSIONNR
FROM BDLFUPDEF
INTO @DATA(ld_versionnr).


DATA(ld_global_flag) = some text here

DATA(ld_remote_call) = some text here

DATA(ld_update_task) = some text here

"populate fields of struture and append to itab
append wa_exception_list to it_exception_list.

"populate fields of struture and append to itab
append wa_export_parameter to it_export_parameter.

"populate fields of struture and append to itab
append wa_import_parameter to it_import_parameter.

"populate fields of struture and append to itab
append wa_changing_parameter to it_changing_parameter.

"populate fields of struture and append to itab
append wa_tables_parameter to it_tables_parameter.

"populate fields of struture and append to itab
append wa_dfields_tab to it_dfields_tab.

"populate fields of struture and append to itab
append wa_table_headers to it_table_headers. . CALL FUNCTION 'BDL_FUPDEF_INTERFACE_SET' EXPORTING logfunc = ld_logfunc clust_id = ld_clust_id * versionnr = ld_versionnr global_flag = ld_global_flag remote_call = ld_remote_call update_task = ld_update_task TABLES exception_list = it_exception_list export_parameter = it_export_parameter import_parameter = it_import_parameter changing_parameter = it_changing_parameter tables_parameter = it_tables_parameter dfields_tab = it_dfields_tab table_headers = it_table_headers EXCEPTIONS EXPORT_ERROR = 1 WRONG_VERSIONNR = 2 . " BDL_FUPDEF_INTERFACE_SET
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_logfunc  TYPE BDLFUVERS-LOGFUNC ,
it_exception_list  TYPE STANDARD TABLE OF BDLRSEXC4 ,
wa_exception_list  LIKE LINE OF it_exception_list,
ld_clust_id  TYPE BDLFUVERS-CLUST_ID ,
it_export_parameter  TYPE STANDARD TABLE OF BDLRSEXP4 ,
wa_export_parameter  LIKE LINE OF it_export_parameter,
ld_versionnr  TYPE BDLFUPDEF-VERSIONNR ,
it_import_parameter  TYPE STANDARD TABLE OF BDLRSIMP4 ,
wa_import_parameter  LIKE LINE OF it_import_parameter,
ld_global_flag  TYPE BDL_STRUCT-CHAR1 ,
it_changing_parameter  TYPE STANDARD TABLE OF BDLRSCHA4 ,
wa_changing_parameter  LIKE LINE OF it_changing_parameter,
ld_remote_call  TYPE BDL_STRUCT-CHAR1 ,
it_tables_parameter  TYPE STANDARD TABLE OF BDLRSTBL4 ,
wa_tables_parameter  LIKE LINE OF it_tables_parameter,
ld_update_task  TYPE BDL_STRUCT-CHAR1 ,
it_dfields_tab  TYPE STANDARD TABLE OF BDLDFIELDS ,
wa_dfields_tab  LIKE LINE OF it_dfields_tab,
it_table_headers  TYPE STANDARD TABLE OF BDLTABHEAD ,
wa_table_headers  LIKE LINE OF it_table_headers.


SELECT single LOGFUNC
FROM BDLFUVERS
INTO ld_logfunc.


"populate fields of struture and append to itab
append wa_exception_list to it_exception_list.

SELECT single CLUST_ID
FROM BDLFUVERS
INTO ld_clust_id.


"populate fields of struture and append to itab
append wa_export_parameter to it_export_parameter.

SELECT single VERSIONNR
FROM BDLFUPDEF
INTO ld_versionnr.


"populate fields of struture and append to itab
append wa_import_parameter to it_import_parameter.

ld_global_flag = some text here

"populate fields of struture and append to itab
append wa_changing_parameter to it_changing_parameter.

ld_remote_call = some text here

"populate fields of struture and append to itab
append wa_tables_parameter to it_tables_parameter.

ld_update_task = some text here

"populate fields of struture and append to itab
append wa_dfields_tab to it_dfields_tab.

"populate fields of struture and append to itab
append wa_table_headers to it_table_headers.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BDL_FUPDEF_INTERFACE_SET or its description.