RSSDBIDX is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). Below is the basic information available for this SAP report including which OBJECTS it interacts with such as TABLES, FUNCTION MODULES, INCLUDES ETC. Also check out the submitted Comments related to this SAP report or see any standard documentation available.
If you would like to execute this report or see the full code listing simply enter RSSDBIDX into the relevant SAP transactions such as SE38 or SE80
This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.
Selection Text: PDISABLE = Deny Index Access
Selection Text: PENABLE = Allow Index Access
Selection Text: PIDXNAME = Index Name
Selection Text: POWNER = Table Owner/Schema
Selection Text: PRECREA = Restore Index
Selection Text: PRESET = Reset Usage Counter
Selection Text: PTABNAME = Table Name
Selection Text: P_CON = Name of Database Connection
Title: SAP DB: Enable/Disable Indexing of Table
Text Symbol: 001 = Table does not exist
Text Symbol: 002 = To:
Text Symbol: 003 = Index does not exist
Text Symbol: 004 = Error during the subroutine generation
Text Symbol: 005 = Restore Index
Text Symbol: 006 = Error when restoring:
Text Symbol: 007 = Index restored:
Text Symbol: 008 = to
Text Symbol: 010 = Cannot reset in this DB version.
Text Symbol: 011 = Index is not bad:
Text Symbol: 012 = Reset usage counter, index:
INCLUDE SDB_CLIENT_SEPARATION.
INCLUDE: ISDBCON1. "#EC NEEDED
APPEND 'INCLUDE SDB_CLIENT_SEPARATION.' TO G_CODE.
No SAP DATABASE tables are accessed within this REPORT code!
EXISTS_OBJECT_SDB CALL FUNCTION 'EXISTS_OBJECT_SDB' EXPORTING iv_con_name = p_con iv_owner = dbuser iv_tablename = tabname CHANGING cv_kernelversion = long_version EXCEPTIONS object_doesnt_exist = 1 no_connection = 2 OTHERS = 3.
EXISTS_INDEX_SDB CALL FUNCTION 'EXISTS_INDEX_SDB' EXPORTING iv_con_name = p_con iv_owner = dbuser iv_tablename = tabname iv_indexname = idxname CHANGING cv_kernelversion = long_version EXCEPTIONS index_doesnt_exist = 1 no_connection = 2 OTHERS = 3.
DBM_EXECUTE_SDB CALL FUNCTION 'DBM_EXECUTE_SDB' EXPORTING iv_con_name = l_con_name iv_call_mode = 'C' iv_command = l_command iv_comm_text = l_comm_text iv_force_mode = 'X' TABLES et_result = lt_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 OTHERS = 8.
SEL_EXTENDED_VERSION_SDB CALL FUNCTION 'SEL_EXTENDED_VERSION_SDB' EXPORTING con_name = l_con_name IMPORTING long_version = l_long_version.
DBM_EXECUTE_SDB CALL FUNCTION 'DBM_EXECUTE_SDB' EXPORTING iv_con_name = l_con_name iv_command = l_command iv_comm_text = l_comm_text 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 OTHERS = 8.
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.