SAP Function Modules

DBM_EXECUTE_SDB SAP Function module







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

Associated Function Group: SADC
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM DBM_EXECUTE_SDB - DBM EXECUTE SDB





CALL FUNCTION 'DBM_EXECUTE_SDB' "
  EXPORTING
    iv_con_name =               " dbcon-con_name  Logical Name for a Database Connection
*   iv_call_mode =              " sdb_cmode     SAP DB: DBMRFC Call Mode
*   iv_nohold =                 " flag
*   iv_force_mode =             " flag
    iv_command =                " sdb_dbmcmd    SAP DB: DBMServer command
*   iv_comm_text =              " sy-ucomm      Text in status line
  IMPORTING
    ev_sysrc =                  " sdb_sysrc     SAP DB: SysRC from DBM call
    ev_dbmrc =                  " sdb_dbmrc     SAP DB: Error code from DBMServer command
    ev_errtxt =                 " sdb_errtxt    SAP DB: Error text from DBM command
* TABLES
*   et_result =                 " sdb_answ      SAP DB: Response Line from DBM Command
  EXCEPTIONS
    NO_PERMISSION = 1           "
    CONNECT_INFO_ERROR = 2      "
    COMMUNICATION_FAILURE = 3   "
    SYSTEM_FAILURE = 4          "
    DBM_SYSTEM_ERROR = 5        "
    DBM_EXECUTE_ERROR = 6       "
    SAPDB_DBM_EXECUTE_ERROR = 7  "
    .  "  DBM_EXECUTE_SDB

ABAP code example for Function Module DBM_EXECUTE_SDB





The ABAP code below is a full code listing to execute function module DBM_EXECUTE_SDB 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_sysrc  TYPE SDB_SYSRC ,
ld_ev_dbmrc  TYPE SDB_DBMRC ,
ld_ev_errtxt  TYPE SDB_ERRTXT ,
it_et_result  TYPE STANDARD TABLE OF SDB_ANSW,"TABLES PARAM
wa_et_result  LIKE LINE OF it_et_result .


SELECT single CON_NAME
FROM DBCON
INTO @DATA(ld_iv_con_name).

DATA(ld_iv_call_mode) = 'Check type of data required'.
DATA(ld_iv_nohold) = 'Check type of data required'.
DATA(ld_iv_force_mode) = 'Check type of data required'.
DATA(ld_iv_command) = 'Check type of data required'.
DATA(ld_iv_comm_text) = 'some text here'.

"populate fields of struture and append to itab
append wa_et_result to it_et_result. . CALL FUNCTION 'DBM_EXECUTE_SDB' EXPORTING iv_con_name = ld_iv_con_name * iv_call_mode = ld_iv_call_mode * iv_nohold = ld_iv_nohold * iv_force_mode = ld_iv_force_mode iv_command = ld_iv_command * iv_comm_text = ld_iv_comm_text IMPORTING ev_sysrc = ld_ev_sysrc ev_dbmrc = ld_ev_dbmrc ev_errtxt = ld_ev_errtxt * TABLES * et_result = it_et_result EXCEPTIONS NO_PERMISSION = 1 CONNECT_INFO_ERROR = 2 COMMUNICATION_FAILURE = 3 SYSTEM_FAILURE = 4 DBM_SYSTEM_ERROR = 5 DBM_EXECUTE_ERROR = 6 SAPDB_DBM_EXECUTE_ERROR = 7 . " DBM_EXECUTE_SDB
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 ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "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_sysrc  TYPE SDB_SYSRC ,
ld_iv_con_name  TYPE DBCON-CON_NAME ,
it_et_result  TYPE STANDARD TABLE OF SDB_ANSW ,
wa_et_result  LIKE LINE OF it_et_result,
ld_ev_dbmrc  TYPE SDB_DBMRC ,
ld_iv_call_mode  TYPE SDB_CMODE ,
ld_ev_errtxt  TYPE SDB_ERRTXT ,
ld_iv_nohold  TYPE FLAG ,
ld_iv_force_mode  TYPE FLAG ,
ld_iv_command  TYPE SDB_DBMCMD ,
ld_iv_comm_text  TYPE SY-UCOMM .


SELECT single CON_NAME
FROM DBCON
INTO ld_iv_con_name.


"populate fields of struture and append to itab
append wa_et_result to it_et_result.
ld_iv_call_mode = 'some text here'.
ld_iv_nohold = 'some text here'.
ld_iv_force_mode = 'some text here'.
ld_iv_command = 'some text here'.
ld_iv_comm_text = 'some text here'.

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 DBM_EXECUTE_SDB or its description.