SAP G_SET_LIST_SELECT_RANGES Function Module for









G_SET_LIST_SELECT_RANGES is a standard g set list select ranges SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 g set list select ranges FM, simply by entering the name G_SET_LIST_SELECT_RANGES into the relevant SAP transaction such as SE37 or SE38.

Function Group: GSBD
Program Name: SAPLGSBD
Main Program: SAPLGSBD
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function G_SET_LIST_SELECT_RANGES 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 'G_SET_LIST_SELECT_RANGES'"
EXPORTING
* TYPELIST = 'BSDM' "
* LANGUAGE = "
* CLIENT = "
* NO_DYNAMIC_SETS = ' ' "

TABLES
* TABNAME_TAB = "
* TITLE_TAB = "
FOUND_SETS = "
* FIELDNAME_TAB = "
* CLASS_TAB = "
* SUBCLASS_TAB = "
* SETNAME_TAB = "
* CREUSER_TAB = "
* CREDATE_TAB = "
* UPDUSER_TAB = "
* UPDDATE_TAB = "
.



IMPORTING Parameters details for G_SET_LIST_SELECT_RANGES

TYPELIST -

Data type: C
Default: 'BSDM'
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE -

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

CLIENT -

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

NO_DYNAMIC_SETS -

Data type: SY-DATAR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for G_SET_LIST_SELECT_RANGES

TABNAME_TAB -

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

TITLE_TAB -

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

FOUND_SETS -

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

FIELDNAME_TAB -

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

CLASS_TAB -

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

SUBCLASS_TAB -

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

SETNAME_TAB -

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

CREUSER_TAB -

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

CREDATE_TAB -

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

UPDUSER_TAB -

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

UPDDATE_TAB -

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

Copy and paste ABAP code example for G_SET_LIST_SELECT_RANGES 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_typelist  TYPE C, "   'BSDM'
lt_tabname_tab  TYPE STANDARD TABLE OF GSR_TABLE, "   
lt_title_tab  TYPE STANDARD TABLE OF GSR_TITLE, "   
lt_found_sets  TYPE STANDARD TABLE OF SETHIER, "   
lv_language  TYPE SY-LANGU, "   
lt_fieldname_tab  TYPE STANDARD TABLE OF GSR_FIELD, "   
lv_client  TYPE SY-MANDT, "   
lt_class_tab  TYPE STANDARD TABLE OF GSR_CLASS, "   
lt_subclass_tab  TYPE STANDARD TABLE OF GSR_SUBCLS, "   
lv_no_dynamic_sets  TYPE SY-DATAR, "   SPACE
lt_setname_tab  TYPE STANDARD TABLE OF GSR_SETNAM, "   
lt_creuser_tab  TYPE STANDARD TABLE OF RSNAMRANGE, "   
lt_credate_tab  TYPE STANDARD TABLE OF RSDATRANGE, "   
lt_upduser_tab  TYPE STANDARD TABLE OF RSNAMRANGE, "   
lt_upddate_tab  TYPE STANDARD TABLE OF RSDATRANGE. "   

  CALL FUNCTION 'G_SET_LIST_SELECT_RANGES'  "
    EXPORTING
         TYPELIST = lv_typelist
         LANGUAGE = lv_language
         CLIENT = lv_client
         NO_DYNAMIC_SETS = lv_no_dynamic_sets
    TABLES
         TABNAME_TAB = lt_tabname_tab
         TITLE_TAB = lt_title_tab
         FOUND_SETS = lt_found_sets
         FIELDNAME_TAB = lt_fieldname_tab
         CLASS_TAB = lt_class_tab
         SUBCLASS_TAB = lt_subclass_tab
         SETNAME_TAB = lt_setname_tab
         CREUSER_TAB = lt_creuser_tab
         CREDATE_TAB = lt_credate_tab
         UPDUSER_TAB = lt_upduser_tab
         UPDDATE_TAB = lt_upddate_tab
. " G_SET_LIST_SELECT_RANGES




ABAP code using 7.40 inline data declarations to call FM G_SET_LIST_SELECT_RANGES

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.

DATA(ld_typelist) = 'BSDM'.
 
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
 
 
"SELECT single MANDT FROM SY INTO @DATA(ld_client).
 
 
 
"SELECT single DATAR FROM SY INTO @DATA(ld_no_dynamic_sets).
DATA(ld_no_dynamic_sets) = ' '.
 
 
 
 
 
 


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!