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

Search SAP Function Modules

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

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

Function BDL_FUPDEF_INTERFACE_SET 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_SET'"Saves interface data in BDLFUPDEF for R/3-Release 4.*
  EXPORTING
   LOGFUNC =  "
   CLUST_ID =  "
*  VERSIONNR =  "Sets version of given version number active.
   GLOBAL_FLAG =  "
   REMOTE_CALL =  "
   UPDATE_TASK =  "

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

EXCEPTIONS
   EXPORT_ERROR = 1    WRONG_VERSIONNR = 2 

.

IMPORTING Parameters details for BDL_FUPDEF_INTERFACE_SET

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)

VERSIONNR - Sets version of given version number active.

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

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_SET

EXCEPTION_LIST -

Data type: BDLRSEXC4
Optional: No
Call by Reference: Yes

EXPORT_PARAMETER -

Data type: BDLRSEXP4
Optional: No
Call by Reference: Yes

IMPORT_PARAMETER -

Data type: BDLRSIMP4
Optional: No
Call by Reference: Yes

CHANGING_PARAMETER -

Data type: BDLRSCHA4
Optional: No
Call by Reference: Yes

TABLES_PARAMETER -

Data type: BDLRSTBL4
Optional: No
Call by Reference: Yes

DFIELDS_TAB -

Data type: BDLDFIELDS
Optional: No
Call by Reference: Yes

TABLE_HEADERS -

Data type: BDLTABHEAD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

EXPORT_ERROR -

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

WRONG_VERSIONNR - Version number does not exist.

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

Copy and paste ABAP code example for BDL_FUPDEF_INTERFACE_SET 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.

ABAP code using 7.40 inline data declarations to call FM BDL_FUPDEF_INTERFACE_SET

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