RSD_CUBE_MULTI_GET_ONLY_DB SAP Function module - Info about multiple InfoCubes (only DB fields -> fast access)

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

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

Pattern for FM RSD_CUBE_MULTI_GET_ONLY_DB - RSD CUBE MULTI GET ONLY DB

CALL FUNCTION 'RSD_CUBE_MULTI_GET_ONLY_DB' "Info about multiple InfoCubes (only DB fields -> fast access)
* EXPORTING
*   i_read_all = RS_C_FALSE     " rs_bool       Read All? (Indicator)
*   i_t_infocube =              " rsd_t_c30     Table with InfoCubes
*   i_objvers = RS_C_OBJVERS-ACTIVE  " rs_objvers  Version
*   i_incl_append = RS_C_TRUE   " rs_bool       With Appends
*   i_cubetype = 'B'            " rsd_s_cube-cubetype  Type of InfoCube (base / aggregate)
*   i_t_cubetype =              " rsd_t_cubetype  List of Cube types
*   i_with_atr_nav = RS_C_FALSE  " rs_bool      Flag: with nav. attributes
  IMPORTING
    e_t_cube =                  " rsd_t_cube    InfoCubes
    e_t_cube_iobj =             " rsd_t_cube_iobj  InfoCubes - InfoObjects
    e_t_dime_iobj =             " rsd_t_dime_iobj  Dimensions - InfoObjects
    e_t_ic_val_iobj =           " rsd_t_ic_val_iobj  InfoObjects in the validity table of the Cube
    e_t_cube_part =             " rsd_t_cube_part  Used InfoCubes in a Multicube
  EXCEPTIONS
    ILLEGAL_INPUT = 1           "               Invalid Entry
    .  "  RSD_CUBE_MULTI_GET_ONLY_DB

ABAP code example for Function Module RSD_CUBE_MULTI_GET_ONLY_DB

The ABAP code below is a full code listing to execute function module RSD_CUBE_MULTI_GET_ONLY_DB 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_cube  
 
 TYPE RSD_T_CUBE
,
ld_e_t_cube_iobj  
 
 TYPE RSD_T_CUBE_IOBJ
,
ld_e_t_dime_iobj  
 
 TYPE RSD_T_DIME_IOBJ
,
ld_e_t_ic_val_iobj  
 
 TYPE RSD_T_IC_VAL_IOBJ
,
ld_e_t_cube_part  
 
 TYPE RSD_T_CUBE_PART
.


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

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

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

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


DATA(ld_i_cubetype) = some text here

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

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

CALL FUNCTION 'RSD_CUBE_MULTI_GET_ONLY_DB'
* EXPORTING
*   i_read_all =                 ld_i_read_all
*   i_t_infocube =               ld_i_t_infocube
*   i_objvers =                  ld_i_objvers
*   i_incl_append =              ld_i_incl_append
*   i_cubetype =                 ld_i_cubetype
*   i_t_cubetype =               ld_i_t_cubetype
*   i_with_atr_nav =             ld_i_with_atr_nav
  IMPORTING
    e_t_cube =                   ld_e_t_cube
    e_t_cube_iobj =              ld_e_t_cube_iobj
    e_t_dime_iobj =              ld_e_t_dime_iobj
    e_t_ic_val_iobj =            ld_e_t_ic_val_iobj
    e_t_cube_part =              ld_e_t_cube_part
  EXCEPTIONS
    ILLEGAL_INPUT =              1
    .  "  RSD_CUBE_MULTI_GET_ONLY_DB

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_cube
 
 TYPE RSD_T_CUBE ,
ld_i_read_all
 
 TYPE RS_BOOL ,
ld_e_t_cube_iobj
 
 TYPE RSD_T_CUBE_IOBJ ,
ld_i_t_infocube
 
 TYPE RSD_T_C30 ,
ld_e_t_dime_iobj
 
 TYPE RSD_T_DIME_IOBJ ,
ld_i_objvers
 
 TYPE RS_OBJVERS ,
ld_e_t_ic_val_iobj
 
 TYPE RSD_T_IC_VAL_IOBJ ,
ld_i_incl_append
 
 TYPE RS_BOOL ,
ld_e_t_cube_part
 
 TYPE RSD_T_CUBE_PART ,
ld_i_cubetype
 
 TYPE RSD_S_CUBE-CUBETYPE ,
ld_i_t_cubetype
 
 TYPE RSD_T_CUBETYPE ,
ld_i_with_atr_nav
 
 TYPE RS_BOOL .


ld_i_read_all = 'Check type of data required'.
ld_i_t_infocube = 'Check type of data required'.
ld_i_objvers = 'Check type of data required'.
ld_i_incl_append = 'Check type of data required'.

ld_i_cubetype = some text here
ld_i_t_cubetype = 'Check type of data required'.
ld_i_with_atr_nav = 'Check type of data required'.