SAP G_VARIABLE_GET_NEXT_USED Function Module for Sequential Reading of the Value Variables in a Set
G_VARIABLE_GET_NEXT_USED is a standard g variable get next used SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sequential Reading of the Value Variables in a Set 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 g variable get next used FM, simply by entering the name G_VARIABLE_GET_NEXT_USED into the relevant SAP transaction such as SE37 or SE38.
Function Group: GSSM
Program Name: SAPLGSSM
Main Program:
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_VARIABLE_GET_NEXT_USED 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_VARIABLE_GET_NEXT_USED'"Sequential Reading of the Value Variables in a Set.
EXPORTING
* CLASS = ' ' "Set class
* SETNAME = ' ' "Name of set
* TABLE = ' ' "Set table
* RETURN_INTERNAL_VARIABLE = ' ' "'X': Internal Variable, ' ': External Variable
IMPORTING
ENTRY = "Data of the Entry
VALUE = "Variable Default Value
VARIABLE = "Variable name
EXCEPTIONS
END_OF_VARIABLES = 1
IMPORTING Parameters details for G_VARIABLE_GET_NEXT_USED
CLASS - Set class
Data type: RGSMH-CLASSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SETNAME - Name of set
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLE - Set table
Data type: RGSMH-TABLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
RETURN_INTERNAL_VARIABLE - 'X': Internal Variable, ' ': External Variable
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for G_VARIABLE_GET_NEXT_USED
ENTRY - Data of the Entry
Data type: RGSMVOptional: No
Call by Reference: No ( called with pass by value option)
VALUE - Variable Default Value
Data type: RGSGV-DEFVALUEOptional: No
Call by Reference: No ( called with pass by value option)
VARIABLE - Variable name
Data type: RGSGV-VARIABLEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
END_OF_VARIABLES - No Additional Value Variable found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_VARIABLE_GET_NEXT_USED 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_class | TYPE RGSMH-CLASS, " SPACE | |||
| lv_entry | TYPE RGSMV, " | |||
| lv_end_of_variables | TYPE RGSMV, " | |||
| lv_value | TYPE RGSGV-DEFVALUE, " | |||
| lv_setname | TYPE C, " SPACE | |||
| lv_table | TYPE RGSMH-TABLE, " SPACE | |||
| lv_variable | TYPE RGSGV-VARIABLE, " | |||
| lv_return_internal_variable | TYPE FLAG. " SPACE |
|   CALL FUNCTION 'G_VARIABLE_GET_NEXT_USED' "Sequential Reading of the Value Variables in a Set |
| EXPORTING | ||
| CLASS | = lv_class | |
| SETNAME | = lv_setname | |
| TABLE | = lv_table | |
| RETURN_INTERNAL_VARIABLE | = lv_return_internal_variable | |
| IMPORTING | ||
| ENTRY | = lv_entry | |
| VALUE | = lv_value | |
| VARIABLE | = lv_variable | |
| EXCEPTIONS | ||
| END_OF_VARIABLES = 1 | ||
| . " G_VARIABLE_GET_NEXT_USED | ||
ABAP code using 7.40 inline data declarations to call FM G_VARIABLE_GET_NEXT_USED
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.| "SELECT single CLASS FROM RGSMH INTO @DATA(ld_class). | ||||
| DATA(ld_class) | = ' '. | |||
| "SELECT single DEFVALUE FROM RGSGV INTO @DATA(ld_value). | ||||
| DATA(ld_setname) | = ' '. | |||
| "SELECT single TABLE FROM RGSMH INTO @DATA(ld_table). | ||||
| DATA(ld_table) | = ' '. | |||
| "SELECT single VARIABLE FROM RGSGV INTO @DATA(ld_variable). | ||||
| DATA(ld_return_internal_variable) | = ' '. | |||
Search for further information about these or an SAP related objects