RSDU_INFOCUBE_INDEXES_GET SAP Function module - Gets DB Names of Secondary Indexes on the Fact Table

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

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

Pattern for FM RSDU_INFOCUBE_INDEXES_GET - RSDU INFOCUBE INDEXES GET

CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_GET' "Gets DB Names of Secondary Indexes on the Fact Table
  EXPORTING
    i_infocube =                " rsd_infocube
*   i_facttab =                 " rsd_tablnm
*   i_double_facttab = RS_C_TRUE  " rs_bool
  IMPORTING
    e_t_idxname =               " rsdu_t_index
  EXCEPTIONS
    INFOCUBE_ERROR = 1          "
    DDIC_ERROR = 2              "
    INHERITED_ERROR = 3         "               Internal Error
    .  "  RSDU_INFOCUBE_INDEXES_GET

ABAP code example for Function Module RSDU_INFOCUBE_INDEXES_GET

The ABAP code below is a full code listing to execute function module RSDU_INFOCUBE_INDEXES_GET 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_t_idxname  
 
 TYPE RSDU_T_INDEX
.


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

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

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

CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_GET'
  EXPORTING
    i_infocube =                 ld_i_infocube
*   i_facttab =                  ld_i_facttab
*   i_double_facttab =           ld_i_double_facttab
  IMPORTING
    e_t_idxname =                ld_e_t_idxname
  EXCEPTIONS
    INFOCUBE_ERROR =             1
    DDIC_ERROR =                 2
    INHERITED_ERROR =            3
    .  "  RSDU_INFOCUBE_INDEXES_GET

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
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_t_idxname
 
 TYPE RSDU_T_INDEX ,
ld_i_infocube
 
 TYPE RSD_INFOCUBE ,
ld_i_facttab
 
 TYPE RSD_TABLNM ,
ld_i_double_facttab
 
 TYPE RS_BOOL .


ld_i_infocube = 'Check type of data required'.
ld_i_facttab = 'Check type of data required'.
ld_i_double_facttab = 'Check type of data required'.