HDB_RANGE_SAVE SAP Function module - Save applicationspecific Ranges on DB

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

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

Pattern for FM HDB_RANGE_SAVE - HDB RANGE SAVE

CALL FUNCTION 'HDB_RANGE_SAVE' "Save applicationspecific Ranges on DB
  EXPORTING
    i_application =             " hdb_application  Application
*   i_subapplication = SPACE    " hdb_subapplication  Sub-Application
*   i_range_type = SPACE        " hdb_range_type  Range Type
*   i_key_value = SPACE         " hdb_key_value  Key Value
*   i_take_all_values =         " flag          Take all values, independent from range-table
*   it_range =                  " hdb_t_range   Range of Values
    .  "  HDB_RANGE_SAVE

ABAP code example for Function Module HDB_RANGE_SAVE

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

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

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

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

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

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

CALL FUNCTION 'HDB_RANGE_SAVE'
  EXPORTING
    i_application =              ld_i_application
*   i_subapplication =           ld_i_subapplication
*   i_range_type =               ld_i_range_type
*   i_key_value =                ld_i_key_value
*   i_take_all_values =          ld_i_take_all_values
*   it_range =                   ld_it_range
    .  "  HDB_RANGE_SAVE

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_i_application
 
 TYPE HDB_APPLICATION ,
ld_i_subapplication
 
 TYPE HDB_SUBAPPLICATION ,
ld_i_range_type
 
 TYPE HDB_RANGE_TYPE ,
ld_i_key_value
 
 TYPE HDB_KEY_VALUE ,
ld_i_take_all_values
 
 TYPE FLAG ,
ld_it_range
 
 TYPE HDB_T_RANGE .


ld_i_application = 'Check type of data required'.
ld_i_subapplication = 'Check type of data required'.
ld_i_range_type = 'Check type of data required'.
ld_i_key_value = 'Check type of data required'.
ld_i_take_all_values = 'Check type of data required'.
ld_it_range = 'Check type of data required'.

SAP Documentation for FM HDB_RANGE_SAVE