BDT_DATA_SAVE SAP Function module

BDT_DATA_SAVE 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 BDT_DATA_SAVE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BUSS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BDT_DATA_SAVE - BDT DATA SAVE

CALL FUNCTION 'BDT_DATA_SAVE' "
  EXPORTING
    iv_handle =                 " bdt_instance_id  Handle
*   iv_xupdtask = '~'           " bdt_boole_t
*   iv_xcommit =                " boole_d
*   iv_xdsavc = 'X'             " boole_d
*   iv_xdsave = 'X'             " boole_d
  IMPORTING
    ev_message_severity =       " sysubrc
    ev_xdsave_performed =       " bdt_boole_d
* TABLES
*   et_key_assignment =         " busskey
*   et_message =                " bus0msg1      Messages
  EXCEPTIONS
    HANDLE_NOT_FOUND = 1        "
    SECONDARY_INSTANCE = 2      "
    .  "  BDT_DATA_SAVE

ABAP code example for Function Module BDT_DATA_SAVE

The ABAP code below is a full code listing to execute function module BDT_DATA_SAVE 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:
ld_ev_message_severity  
 
 TYPE SYSUBRC
,
ld_ev_xdsave_performed  
 
 TYPE BDT_BOOLE_D
,
it_et_key_assignment  
 
 TYPE STANDARD TABLE OF BUSSKEY,"TABLES PARAM
wa_et_key_assignment
 
 LIKE LINE OF it_et_key_assignment
,
it_et_message  
 
 TYPE STANDARD TABLE OF BUS0MSG1,"TABLES PARAM
wa_et_message
 
 LIKE LINE OF it_et_message
.


DATA(ld_iv_handle) = 'Check type of data required'.

DATA(ld_iv_xupdtask) = 'Check type of data required'.

DATA(ld_iv_xcommit) = 'Check type of data required'.

DATA(ld_iv_xdsavc) = 'Check type of data required'.

DATA(ld_iv_xdsave) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_et_key_assignment to it_et_key_assignment.
 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
.

CALL FUNCTION 'BDT_DATA_SAVE'
  EXPORTING
    iv_handle =                  ld_iv_handle
*   iv_xupdtask =                ld_iv_xupdtask
*   iv_xcommit =                 ld_iv_xcommit
*   iv_xdsavc =                  ld_iv_xdsavc
*   iv_xdsave =                  ld_iv_xdsave
  IMPORTING
    ev_message_severity =        ld_ev_message_severity
    ev_xdsave_performed =        ld_ev_xdsave_performed
* TABLES
*   et_key_assignment =          it_et_key_assignment
*   et_message =                 it_et_message
  EXCEPTIONS
    HANDLE_NOT_FOUND =           1
    SECONDARY_INSTANCE =         2
    .  "  BDT_DATA_SAVE

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_ev_message_severity
 
 TYPE SYSUBRC ,
ld_iv_handle
 
 TYPE BDT_INSTANCE_ID ,
it_et_key_assignment
 
 TYPE STANDARD TABLE OF BUSSKEY ,
wa_et_key_assignment
 
 LIKE LINE OF it_et_key_assignment,
ld_ev_xdsave_performed
 
 TYPE BDT_BOOLE_D ,
ld_iv_xupdtask
 
 TYPE BDT_BOOLE_T ,
it_et_message
 
 TYPE STANDARD TABLE OF BUS0MSG1 ,
wa_et_message
 
 LIKE LINE OF it_et_message,
ld_iv_xcommit
 
 TYPE BOOLE_D ,
ld_iv_xdsavc
 
 TYPE BOOLE_D ,
ld_iv_xdsave
 
 TYPE BOOLE_D .


ld_iv_handle = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_key_assignment to it_et_key_assignment.
ld_iv_xupdtask = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_et_message to it_et_message.
ld_iv_xcommit = 'Check type of data required'.
ld_iv_xdsavc = 'Check type of data required'.
ld_iv_xdsave = 'Check type of data required'.