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









SQLM_DATA_GET_NEXT_RECORDS is a standard sqlm data get next records SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get next n SQLM records starting at a given offset-record processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for sqlm data get next records FM, simply by entering the name SQLM_DATA_GET_NEXT_RECORDS into the relevant SAP transaction such as SE37 or SE38.

Function Group: SQLM_DATA
Program Name: SAPLSQLM_DATA
Main Program: SAPLSQLM_DATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:



Function SQLM_DATA_GET_NEXT_RECORDS pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'SQLM_DATA_GET_NEXT_RECORDS'"Get next n SQLM records starting at a given offset-record
  EXPORTING
   BLOCK_SIZE =  "
*  STARTING_RECORD =  "
*  FILTER =  "
*  DEVCLASSES =  "
*  OBJNAMES =  "
*  OBJTYPES =  "
*  TOP_STMT_KEYS =  "

 IMPORTING
   RECORDS =  "
   NUMBER_OF_RECORDS =  "
   HAS_MORE_RECORDS =  "

EXCEPTIONS
   FAILURE = 1
.



IMPORTING Parameters details for SQLM_DATA_GET_NEXT_RECORDS

BLOCK_SIZE -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

STARTING_RECORD -

Data type: SQLMRECORD
Optional: Yes
Call by Reference: No ( called with pass by value option)

FILTER -

Data type: SQLMDATASELECTFILTER
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEVCLASSES -

Data type: SQLMDEVCLASSESRANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJNAMES -

Data type: SQLMOBJNAMESRANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJTYPES -

Data type: SQLMOBJTYPESRANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TOP_STMT_KEYS -

Data type: SQLMKEYS
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SQLM_DATA_GET_NEXT_RECORDS

RECORDS -

Data type: SQLMRECORDS
Optional: No
Call by Reference: No ( called with pass by value option)

NUMBER_OF_RECORDS -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

HAS_MORE_RECORDS -

Data type: FLAG
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FAILURE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SQLM_DATA_GET_NEXT_RECORDS Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_failure  TYPE STRING, "   
lv_records  TYPE SQLMRECORDS, "   
lv_block_size  TYPE I, "   
lv_starting_record  TYPE SQLMRECORD, "   
lv_number_of_records  TYPE I, "   
lv_filter  TYPE SQLMDATASELECTFILTER, "   
lv_has_more_records  TYPE FLAG, "   
lv_devclasses  TYPE SQLMDEVCLASSESRANGE, "   
lv_objnames  TYPE SQLMOBJNAMESRANGE, "   
lv_objtypes  TYPE SQLMOBJTYPESRANGE, "   
lv_top_stmt_keys  TYPE SQLMKEYS. "   

  CALL FUNCTION 'SQLM_DATA_GET_NEXT_RECORDS'  "Get next n SQLM records starting at a given offset-record
    EXPORTING
         BLOCK_SIZE = lv_block_size
         STARTING_RECORD = lv_starting_record
         FILTER = lv_filter
         DEVCLASSES = lv_devclasses
         OBJNAMES = lv_objnames
         OBJTYPES = lv_objtypes
         TOP_STMT_KEYS = lv_top_stmt_keys
    IMPORTING
         RECORDS = lv_records
         NUMBER_OF_RECORDS = lv_number_of_records
         HAS_MORE_RECORDS = lv_has_more_records
    EXCEPTIONS
        FAILURE = 1
. " SQLM_DATA_GET_NEXT_RECORDS




ABAP code using 7.40 inline data declarations to call FM SQLM_DATA_GET_NEXT_RECORDS

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!