HDB_TABLE_DROP 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 HDB_TABLE_DROP into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
HDB_SERVICE
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'HDB_TABLE_DROP' "Drop a table on HDB
EXPORTING
i_tabname = " tabname Table Name
* i_drop_with_data = SPACE " flag General Flag
* i_schema_sys_bic = SPACE " flag General Flag
* i_application = " hdb_application Application (Default: Cross application)
* i_subapplication = SPACE " hdb_subapplication Subapplication
* i_key_value = SPACE " hdb_key_value Key Value
* i_hdbc_check = SPACE " flag Check main switches in HDBC
EXCEPTIONS
DBCON_NOT_EXIST = 1 " HDB Connection Does Not Exist
DBCON_NO_USE = 2 " HDB Connection should not be used in this context (see HDBC)
DBCON_ERROR = 3 " HDB Connection Cannot be Reached
TABLE_CONTAINS_DATA = 4 " Table contains data
HDB_ERROR = 5 " HDB SQL Error
. " HDB_TABLE_DROP
The ABAP code below is a full code listing to execute function module HDB_TABLE_DROP 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_i_tabname) = 'Check type of data required'.
DATA(ld_i_drop_with_data) = 'Check type of data required'.
DATA(ld_i_schema_sys_bic) = 'Check type of data required'.
DATA(ld_i_application) = 'Check type of data required'.
DATA(ld_i_subapplication) = 'Check type of data required'.
DATA(ld_i_key_value) = 'Check type of data required'.
DATA(ld_i_hdbc_check) = 'Check type of data required'. . CALL FUNCTION 'HDB_TABLE_DROP' EXPORTING i_tabname = ld_i_tabname * i_drop_with_data = ld_i_drop_with_data * i_schema_sys_bic = ld_i_schema_sys_bic * i_application = ld_i_application * i_subapplication = ld_i_subapplication * i_key_value = ld_i_key_value * i_hdbc_check = ld_i_hdbc_check EXCEPTIONS DBCON_NOT_EXIST = 1 DBCON_NO_USE = 2 DBCON_ERROR = 3 TABLE_CONTAINS_DATA = 4 HDB_ERROR = 5 . " HDB_TABLE_DROP
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 ENDIF.
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_i_tabname | TYPE TABNAME , |
| ld_i_drop_with_data | TYPE FLAG , |
| ld_i_schema_sys_bic | TYPE FLAG , |
| ld_i_application | TYPE HDB_APPLICATION , |
| ld_i_subapplication | TYPE HDB_SUBAPPLICATION , |
| ld_i_key_value | TYPE HDB_KEY_VALUE , |
| ld_i_hdbc_check | TYPE FLAG . |
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 HDB_TABLE_DROP or its description.