SAP Function Modules

comments icon Comments

SHDB_EXISTS_INDEX SAP Function module - Check existence of table, view, index







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

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


Pattern for FM SHDB_EXISTS_INDEX - SHDB EXISTS INDEX 





CALL FUNCTION 'SHDB_EXISTS_INDEX' "Check existence of table, view, index
  EXPORTING
    i_index_name =              " shdbobjectname  Name of a HDB object
    i_table_name =              " shdbobjectname  Name of a HDB object
*   i_schema_name =             " shdbschema    Name of the current schema
*   i_db_name =                 " shdbname      Name of the current database
  IMPORTING
    e_index_exists =            " shdb_char01   Output name if existing
    e_constraint_name =         " shdbobjectname  Name of a HDB object
    e_unique =                  " shdb_char01
  EXCEPTIONS
    SQL_ERROR = 1               "
    INTERNAL_ERROR = 2          "
    .  "  SHDB_EXISTS_INDEX

ABAP code example for Function Module SHDB_EXISTS_INDEX





The ABAP code below is a full code listing to execute function module SHDB_EXISTS_INDEX 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_e_index_exists    TYPE SHDB_CHAR01
,
ld_e_constraint_name    TYPE SHDBOBJECTNAME
,
ld_e_unique    TYPE SHDB_CHAR01
.




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

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

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

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

CALL FUNCTION 'SHDB_EXISTS_INDEX'
  EXPORTING
    i_index_name =               ld_i_index_name
    i_table_name =               ld_i_table_name
*   i_schema_name =              ld_i_schema_name
*   i_db_name =                  ld_i_db_name
  IMPORTING
    e_index_exists =             ld_e_index_exists
    e_constraint_name =          ld_e_constraint_name
    e_unique =                   ld_e_unique
  EXCEPTIONS
    SQL_ERROR =                  1
    INTERNAL_ERROR =             2
    .  "  SHDB_EXISTS_INDEX

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_e_index_exists  TYPE SHDB_CHAR01 ,
ld_i_index_name  TYPE SHDBOBJECTNAME ,
ld_e_constraint_name  TYPE SHDBOBJECTNAME ,
ld_i_table_name  TYPE SHDBOBJECTNAME ,
ld_e_unique  TYPE SHDB_CHAR01 ,
ld_i_schema_name  TYPE SHDBSCHEMA ,
ld_i_db_name  TYPE SHDBNAME .




ld_i_index_name = 'Check type of data required'.
ld_i_table_name = 'Check type of data required'.
ld_i_schema_name = 'Check type of data required'.
ld_i_db_name = 'Check type of data required'.

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


   
 

SHDB_EXISTS_INDEX - Check existence of table, view, index
SHDB_EXISTS_DATA - Check existence of table, view, index
SHDB_DDIC_CONV_POSSIBLE - Checks whether a DDIC conversion is possible
SHDB_COUNT_INDEXSERVER - get number of indexserver
SHDB_CHECK_TABLE_CONVERSION - Prüft, ob eine DDIC Umsetzung möglich ist
SHARED_BUFFER_READ -