CCMSBI_CUBE_DELETE_D SAP Function module - Deletes data from the InfoCube, that must be "overwritten"

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

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

Pattern for FM CCMSBI_CUBE_DELETE_D - CCMSBI CUBE DELETE D

CALL FUNCTION 'CCMSBI_CUBE_DELETE_D' "Deletes data from the InfoCube, that must be "overwritten"
  EXPORTING
    cube_name =                 " rsddatatarget  Data target for transaction data (InfoCube, ODS object, ...)
*   non_aggr = ' '              " char1         Single-Character Indicator
*   granu = 1                   " int4          Granularity
*   pseudo_enqueue = 'X'        " char1         Pseudo-Enqueue on/off
  TABLES
    data_pack =                 "
  CHANGING
    errors =                    " rs_t_msg      BW: Table with Messages (Application Log)
  EXCEPTIONS
    DELETE_ERROR = 1            "               Deletion Error
    WRONG_TABLE_STRUCTURE = 2   "               Table DATA_PACK has wrong structure
    .  "  CCMSBI_CUBE_DELETE_D

ABAP code example for Function Module CCMSBI_CUBE_DELETE_D

The ABAP code below is a full code listing to execute function module CCMSBI_CUBE_DELETE_D 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:
it_data_pack  
 
 TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_data_pack
 
 LIKE LINE OF it_data_pack
.


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

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

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

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

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

"populate fields of struture and append to itab
append wa_data_pack to it_data_pack.
.

CALL FUNCTION 'CCMSBI_CUBE_DELETE_D'
  EXPORTING
    cube_name =                  ld_cube_name
*   non_aggr =                   ld_non_aggr
*   granu =                      ld_granu
*   pseudo_enqueue =             ld_pseudo_enqueue
  TABLES
    data_pack =                  it_data_pack
  CHANGING
    errors =                     ld_errors
  EXCEPTIONS
    DELETE_ERROR =               1
    WRONG_TABLE_STRUCTURE =      2
    .  "  CCMSBI_CUBE_DELETE_D

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_errors
 
 TYPE RS_T_MSG ,
ld_cube_name
 
 TYPE RSDDATATARGET ,
it_data_pack
 
 TYPE STANDARD TABLE OF STRING ,
wa_data_pack
 
 LIKE LINE OF it_data_pack,
ld_non_aggr
 
 TYPE CHAR1 ,
ld_granu
 
 TYPE INT4 ,
ld_pseudo_enqueue
 
 TYPE CHAR1 .


ld_errors = 'Check type of data required'.
ld_cube_name = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_data_pack to it_data_pack.
ld_non_aggr = 'Check type of data required'.
ld_granu = 'Check type of data required'.
ld_pseudo_enqueue = 'Check type of data required'.