G_VARIABLE_GET_NEXT_USED SAP Function module - Sequential Reading of the Value Variables in a Set

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

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

Pattern for FM G_VARIABLE_GET_NEXT_USED - G VARIABLE GET NEXT USED

CALL FUNCTION 'G_VARIABLE_GET_NEXT_USED' "Sequential Reading of the Value Variables in a Set
* EXPORTING
*   class = SPACE               " rgsmh-class   Set class
*   setname = SPACE             " c             Name of set
*   table = SPACE               " rgsmh-table   Set table
*   return_internal_variable = SPACE  " flag    'X': Internal Variable, ' ': External Variable
  IMPORTING
    entry =                     " rgsmv         Data of the Entry
    value =                     " rgsgv-defvalue  Variable Default Value
    variable =                  " rgsgv-variable  Variable name
  EXCEPTIONS
    END_OF_VARIABLES = 1        "               No Additional Value Variable found
    .  "  G_VARIABLE_GET_NEXT_USED

ABAP code example for Function Module G_VARIABLE_GET_NEXT_USED

The ABAP code below is a full code listing to execute function module G_VARIABLE_GET_NEXT_USED 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_entry  
 
 TYPE RGSMV
,
ld_value  
 
 TYPE RGSGV-DEFVALUE
,
ld_variable  
 
 TYPE RGSGV-VARIABLE
.



DATA(ld_class) = some text here

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


DATA(ld_table) = some text here

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

CALL FUNCTION 'G_VARIABLE_GET_NEXT_USED'
* EXPORTING
*   class =                      ld_class
*   setname =                    ld_setname
*   table =                      ld_table
*   return_internal_variable =    ld_return_internal_variable
  IMPORTING
    entry =                      ld_entry
    value =                      ld_value
    variable =                   ld_variable
  EXCEPTIONS
    END_OF_VARIABLES =           1
    .  "  G_VARIABLE_GET_NEXT_USED

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_entry
 
 TYPE RGSMV ,
ld_class
 
 TYPE RGSMH-CLASS ,
ld_value
 
 TYPE RGSGV-DEFVALUE ,
ld_setname
 
 TYPE C ,
ld_variable
 
 TYPE RGSGV-VARIABLE ,
ld_table
 
 TYPE RGSMH-TABLE ,
ld_return_internal_variable
 
 TYPE FLAG .



ld_class = some text here
ld_setname = 'Check type of data required'.

ld_table = some text here
ld_return_internal_variable = 'Check type of data required'.