BBP_CTR_MASS_APP_CLUSTER_READ SAP Function module - Reading the cluster table

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

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

Pattern for FM BBP_CTR_MASS_APP_CLUSTER_READ - BBP CTR MASS APP CLUSTER READ

CALL FUNCTION 'BBP_CTR_MASS_APP_CLUSTER_READ' "Reading the cluster table
* EXPORTING
*   it_relid =                  " crmt_bsp_range_tab  Range Structure for Search
*   it_status =                 " crmt_bsp_range_tab  Range Structure for Search
*   it_description =            " crmt_bsp_range_tab  Table Type for CRMT_BSP_RANGE
*   it_created_at =             " crmt_bsp_range_tab  Range Structure for Search
*   it_created_by =             " crmt_bsp_range_tab  Range Structure for Search
  IMPORTING
    et_cluster =                " bbpt_ctr_mass_ch  CTR: Mass Change - Data Interface for Background Run
    .  "  BBP_CTR_MASS_APP_CLUSTER_READ

ABAP code example for Function Module BBP_CTR_MASS_APP_CLUSTER_READ

The ABAP code below is a full code listing to execute function module BBP_CTR_MASS_APP_CLUSTER_READ 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_et_cluster  
 
 TYPE BBPT_CTR_MASS_CH
.


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

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

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

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

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

CALL FUNCTION 'BBP_CTR_MASS_APP_CLUSTER_READ'
* EXPORTING
*   it_relid =                   ld_it_relid
*   it_status =                  ld_it_status
*   it_description =             ld_it_description
*   it_created_at =              ld_it_created_at
*   it_created_by =              ld_it_created_by
  IMPORTING
    et_cluster =                 ld_et_cluster
    .  "  BBP_CTR_MASS_APP_CLUSTER_READ

IF SY-SUBRC EQ 0.
  "All OK
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_et_cluster
 
 TYPE BBPT_CTR_MASS_CH ,
ld_it_relid
 
 TYPE CRMT_BSP_RANGE_TAB ,
ld_it_status
 
 TYPE CRMT_BSP_RANGE_TAB ,
ld_it_description
 
 TYPE CRMT_BSP_RANGE_TAB ,
ld_it_created_at
 
 TYPE CRMT_BSP_RANGE_TAB ,
ld_it_created_by
 
 TYPE CRMT_BSP_RANGE_TAB .


ld_it_relid = 'Check type of data required'.
ld_it_status = 'Check type of data required'.
ld_it_description = 'Check type of data required'.
ld_it_created_at = 'Check type of data required'.
ld_it_created_by = 'Check type of data required'.