EXISTS_INDEX_SDB SAP Function module

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

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

Pattern for FM EXISTS_INDEX_SDB - EXISTS INDEX SDB

CALL FUNCTION 'EXISTS_INDEX_SDB' "
  EXPORTING
*   iv_con_name =               " dbcon_name
*   iv_owner =                  " char32
    iv_tablename =              " sadatab
    iv_indexname =              " sadatab
*   iv_sysdba =                 " flag
*   iv_user =                   " flag
* CHANGING
*   cv_kernelversion =          " char15
  EXCEPTIONS
    INDEX_DOESNT_EXIST = 1      "
    NO_CONNECTION = 2           "
    .  "  EXISTS_INDEX_SDB

ABAP code example for Function Module EXISTS_INDEX_SDB

The ABAP code below is a full code listing to execute function module EXISTS_INDEX_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_cv_kernelversion) = 'Check type of data required'.

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

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

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

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

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

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

CALL FUNCTION 'EXISTS_INDEX_SDB'
  EXPORTING
*   iv_con_name =                ld_iv_con_name
*   iv_owner =                   ld_iv_owner
    iv_tablename =               ld_iv_tablename
    iv_indexname =               ld_iv_indexname
*   iv_sysdba =                  ld_iv_sysdba
*   iv_user =                    ld_iv_user
* CHANGING
*   cv_kernelversion =           ld_cv_kernelversion
  EXCEPTIONS
    INDEX_DOESNT_EXIST =         1
    NO_CONNECTION =              2
    .  "  EXISTS_INDEX_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
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_cv_kernelversion
 
 TYPE CHAR15 ,
ld_iv_con_name
 
 TYPE DBCON_NAME ,
ld_iv_owner
 
 TYPE CHAR32 ,
ld_iv_tablename
 
 TYPE SADATAB ,
ld_iv_indexname
 
 TYPE SADATAB ,
ld_iv_sysdba
 
 TYPE FLAG ,
ld_iv_user
 
 TYPE FLAG .


ld_cv_kernelversion = 'Check type of data required'.
ld_iv_con_name = 'Check type of data required'.
ld_iv_owner = 'Check type of data required'.
ld_iv_tablename = 'Check type of data required'.
ld_iv_indexname = 'Check type of data required'.
ld_iv_sysdba = 'Check type of data required'.
ld_iv_user = 'Check type of data required'.