RSDU_DATA_EXISTS_INFOCUBE_ORA SAP Function module - Is there any data in the basic infocube?

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

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

Pattern for FM RSDU_DATA_EXISTS_INFOCUBE_ORA - RSDU DATA EXISTS INFOCUBE ORA

CALL FUNCTION 'RSDU_DATA_EXISTS_INFOCUBE_ORA' "Is there any data in the basic infocube?
  EXPORTING
    i_basiccube =               " rsd_infocube  Name of basic Infocube
  IMPORTING
    e_data_exists =             " rs_bool       Data in I_BASICCUBE yes/no?
    e_f_data_exists =           " rs_bool       Data in F-fact table yes/no?
    e_e_data_exists =           " rs_bool       Data in E-fact table yes/no?
  CHANGING
    c_processed = RS_C_FALSE    " rs_bool       Boolean
  EXCEPTIONS
    INFOCUBE_ERROR = 1          "               I_BASICCUBE is no basic-Infocube or aggregate
    INHERITED_ERROR = 2         "
    .  "  RSDU_DATA_EXISTS_INFOCUBE_ORA

ABAP code example for Function Module RSDU_DATA_EXISTS_INFOCUBE_ORA

The ABAP code below is a full code listing to execute function module RSDU_DATA_EXISTS_INFOCUBE_ORA 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_data_exists  
 
 TYPE RS_BOOL
,
ld_e_f_data_exists  
 
 TYPE RS_BOOL
,
ld_e_e_data_exists  
 
 TYPE RS_BOOL
.


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

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

CALL FUNCTION 'RSDU_DATA_EXISTS_INFOCUBE_ORA'
  EXPORTING
    i_basiccube =                ld_i_basiccube
  IMPORTING
    e_data_exists =              ld_e_data_exists
    e_f_data_exists =            ld_e_f_data_exists
    e_e_data_exists =            ld_e_e_data_exists
  CHANGING
    c_processed =                ld_c_processed
  EXCEPTIONS
    INFOCUBE_ERROR =             1
    INHERITED_ERROR =            2
    .  "  RSDU_DATA_EXISTS_INFOCUBE_ORA

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_c_processed
 
 TYPE RS_BOOL ,
ld_e_data_exists
 
 TYPE RS_BOOL ,
ld_i_basiccube
 
 TYPE RSD_INFOCUBE ,
ld_e_f_data_exists
 
 TYPE RS_BOOL ,
ld_e_e_data_exists
 
 TYPE RS_BOOL .


ld_c_processed = 'Check type of data required'.
ld_i_basiccube = 'Check type of data required'.