SCTC_GET_WHITELIST SAP Function module - Preparing DBACOCKPIT for DB6 database

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

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

Pattern for FM SCTC_GET_WHITELIST - SCTC GET WHITELIST

CALL FUNCTION 'SCTC_GET_WHITELIST' "Preparing DBACOCKPIT for DB6 database
  EXPORTING
    i_component_name =          " string
    i_action =                  " sctc_sc_dte_action  Required Action for SCTC_PROVIDE_TABLES_PER_CMP
    io_msg_handler =            " if_sctc_msg_handler  CTC Message Handler
*   iv_flg_check_auth = 'X'     " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
  IMPORTING
    e_whitelist =               " sctc_sc_t_tabname  List of Table Names for component-wise truncate
    .  "  SCTC_GET_WHITELIST

ABAP code example for Function Module SCTC_GET_WHITELIST

The ABAP code below is a full code listing to execute function module SCTC_GET_WHITELIST 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_whitelist  
 
 TYPE SCTC_SC_T_TABNAME
.


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

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

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

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

CALL FUNCTION 'SCTC_GET_WHITELIST'
  EXPORTING
    i_component_name =           ld_i_component_name
    i_action =                   ld_i_action
    io_msg_handler =             ld_io_msg_handler
*   iv_flg_check_auth =          ld_iv_flg_check_auth
  IMPORTING
    e_whitelist =                ld_e_whitelist
    .  "  SCTC_GET_WHITELIST

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_e_whitelist
 
 TYPE SCTC_SC_T_TABNAME ,
ld_i_component_name
 
 TYPE STRING ,
ld_i_action
 
 TYPE SCTC_SC_DTE_ACTION ,
ld_io_msg_handler
 
 TYPE IF_SCTC_MSG_HANDLER ,
ld_iv_flg_check_auth
 
 TYPE BOOLEAN .


ld_i_component_name = 'Check type of data required'.
ld_i_action = 'Check type of data required'.
ld_io_msg_handler = 'Check type of data required'.
ld_iv_flg_check_auth = 'Check type of data required'.