G_TABLE_RECORD_TO_GLU1 SAP Function module

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

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

Pattern for FM G_TABLE_RECORD_TO_GLU1 - G TABLE RECORD TO GLU1

CALL FUNCTION 'G_TABLE_RECORD_TO_GLU1' "
  EXPORTING
    i_tabname =                 " t800a-tab
*   i_record =                  "
*   i_t_record =                " table
*   i_appending_table = GUSL_C_FALSE  " gusl_bool
*   i_db_commit = GUSL_C_FALSE  " gusl_bool
  CHANGING
    e_t_glu1 =                  " gusl_t_glu1
  EXCEPTIONS
    INVALID_TABLE = 1           "
    .  "  G_TABLE_RECORD_TO_GLU1

ABAP code example for Function Module G_TABLE_RECORD_TO_GLU1

The ABAP code below is a full code listing to execute function module G_TABLE_RECORD_TO_GLU1 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_e_t_glu1) = 'Check type of data required'.
 

SELECT single TAB 
  FROM T800A 
  INTO @DATA(ld_i_tabname).


DATA(ld_i_record) = 'some text here'.

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

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

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

CALL FUNCTION 'G_TABLE_RECORD_TO_GLU1'
  EXPORTING
    i_tabname =                  ld_i_tabname
*   i_record =                   ld_i_record
*   i_t_record =                 ld_i_t_record
*   i_appending_table =          ld_i_appending_table
*   i_db_commit =                ld_i_db_commit
  CHANGING
    e_t_glu1 =                   ld_e_t_glu1
  EXCEPTIONS
    INVALID_TABLE =              1
    .  "  G_TABLE_RECORD_TO_GLU1

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_e_t_glu1
 
 TYPE GUSL_T_GLU1 ,
ld_i_tabname
 
 TYPE T800A-TAB ,
ld_i_record
 
 TYPE STRING ,
ld_i_t_record
 
 TYPE TABLE ,
ld_i_appending_table
 
 TYPE GUSL_BOOL ,
ld_i_db_commit
 
 TYPE GUSL_BOOL .


ld_e_t_glu1 = 'Check type of data required'.

SELECT single TAB 
  FROM T800A 
  INTO ld_i_tabname.

ld_i_record = 'some text here'.
ld_i_t_record = 'Check type of data required'.
ld_i_appending_table = 'Check type of data required'.
ld_i_db_commit = 'Check type of data required'.