HDB_SETT_MAINTAIN SAP Function module - Maintain ERP Accelerator Settings

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

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

Pattern for FM HDB_SETT_MAINTAIN - HDB SETT MAINTAIN

CALL FUNCTION 'HDB_SETT_MAINTAIN' "Maintain ERP Accelerator Settings
  EXPORTING
    it_ra_application =         " hdb_t_range   Applications
    it_ra_subapplication =      " hdb_t_range   Sub-Applications
*   id_cross_application = ABAP_TRUE  " boole_d  'X' = Include Cross-Application Settings
*   id_start_application =      " hdb_application  Start Display with Specific Application
*   id_start_subapplication =   " hdb_subapplication  Start Display with Specific Sub-Application
*   id_tree_show = ABAP_TRUE    " boole_d       'X' = Show Navigation Tree
*   it_exclude_ucomm =          " salv_dynpro_t_fcode  Exclude User Commands in GUI Status
    .  "  HDB_SETT_MAINTAIN

ABAP code example for Function Module HDB_SETT_MAINTAIN

The ABAP code below is a full code listing to execute function module HDB_SETT_MAINTAIN 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_it_ra_application) = 'Check type of data required'.

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

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

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

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

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

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

CALL FUNCTION 'HDB_SETT_MAINTAIN'
  EXPORTING
    it_ra_application =          ld_it_ra_application
    it_ra_subapplication =       ld_it_ra_subapplication
*   id_cross_application =       ld_id_cross_application
*   id_start_application =       ld_id_start_application
*   id_start_subapplication =    ld_id_start_subapplication
*   id_tree_show =               ld_id_tree_show
*   it_exclude_ucomm =           ld_it_exclude_ucomm
    .  "  HDB_SETT_MAINTAIN

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_it_ra_application
 
 TYPE HDB_T_RANGE ,
ld_it_ra_subapplication
 
 TYPE HDB_T_RANGE ,
ld_id_cross_application
 
 TYPE BOOLE_D ,
ld_id_start_application
 
 TYPE HDB_APPLICATION ,
ld_id_start_subapplication
 
 TYPE HDB_SUBAPPLICATION ,
ld_id_tree_show
 
 TYPE BOOLE_D ,
ld_it_exclude_ucomm
 
 TYPE SALV_DYNPRO_T_FCODE .


ld_it_ra_application = 'Check type of data required'.
ld_it_ra_subapplication = 'Check type of data required'.
ld_id_cross_application = 'Check type of data required'.
ld_id_start_application = 'Check type of data required'.
ld_id_start_subapplication = 'Check type of data required'.
ld_id_tree_show = 'Check type of data required'.
ld_it_exclude_ucomm = 'Check type of data required'.