SAP Function Modules

SQLM_DATA_GET_NEXT_RECORDS SAP Function module - Get next n SQLM records starting at a given offset-record







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

Associated Function Group: SQLM_DATA
Released Date: Not Released
Processing type: Remote-Enabled + BasXML supported
remote enabled with basXML set


Pattern for FM SQLM_DATA_GET_NEXT_RECORDS - SQLM DATA GET NEXT RECORDS





CALL FUNCTION 'SQLM_DATA_GET_NEXT_RECORDS' "Get next n SQLM records starting at a given offset-record
  EXPORTING
    block_size =                " i
*   starting_record =           " sqlmrecord
*   filter =                    " sqlmdataselectfilter
*   devclasses =                " sqlmdevclassesrange
*   objnames =                  " sqlmobjnamesrange
*   objtypes =                  " sqlmobjtypesrange
*   top_stmt_keys =             " sqlmkeys
  IMPORTING
    records =                   " sqlmrecords
    number_of_records =         " i
    has_more_records =          " flag
  EXCEPTIONS
    FAILURE = 1                 "
    .  "  SQLM_DATA_GET_NEXT_RECORDS

ABAP code example for Function Module SQLM_DATA_GET_NEXT_RECORDS





The ABAP code below is a full code listing to execute function module SQLM_DATA_GET_NEXT_RECORDS 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_records  TYPE SQLMRECORDS ,
ld_number_of_records  TYPE I ,
ld_has_more_records  TYPE FLAG .

DATA(ld_block_size) = 'Check type of data required'.
DATA(ld_starting_record) = 'Check type of data required'.
DATA(ld_filter) = 'Check type of data required'.
DATA(ld_devclasses) = 'Check type of data required'.
DATA(ld_objnames) = 'Check type of data required'.
DATA(ld_objtypes) = 'Check type of data required'.
DATA(ld_top_stmt_keys) = 'Check type of data required'. . CALL FUNCTION 'SQLM_DATA_GET_NEXT_RECORDS' EXPORTING block_size = ld_block_size * starting_record = ld_starting_record * filter = ld_filter * devclasses = ld_devclasses * objnames = ld_objnames * objtypes = ld_objtypes * top_stmt_keys = ld_top_stmt_keys IMPORTING records = ld_records number_of_records = ld_number_of_records has_more_records = ld_has_more_records EXCEPTIONS FAILURE = 1 . " SQLM_DATA_GET_NEXT_RECORDS
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_records  TYPE SQLMRECORDS ,
ld_block_size  TYPE I ,
ld_number_of_records  TYPE I ,
ld_starting_record  TYPE SQLMRECORD ,
ld_has_more_records  TYPE FLAG ,
ld_filter  TYPE SQLMDATASELECTFILTER ,
ld_devclasses  TYPE SQLMDEVCLASSESRANGE ,
ld_objnames  TYPE SQLMOBJNAMESRANGE ,
ld_objtypes  TYPE SQLMOBJTYPESRANGE ,
ld_top_stmt_keys  TYPE SQLMKEYS .

ld_block_size = 'Check type of data required'.
ld_starting_record = 'Check type of data required'.
ld_filter = 'Check type of data required'.
ld_devclasses = 'Check type of data required'.
ld_objnames = 'Check type of data required'.
ld_objtypes = 'Check type of data required'.
ld_top_stmt_keys = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SQLM_DATA_GET_NEXT_RECORDS or its description.